Re: [crossfire] Materials
Rick pretty well summarized my feelings on the matter... nice concept in theory if unintended side rffects on stacking etc. were dealt with, but that seems a big challenge considering current game mechanics and what not. Rick Tanner wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > > >> I wonder whether to enable that (extended material) support by default and >> fix >> issues, or totally remove it. >> >> What do you think? > >What I found to be irritating about the material code was it made >inventory management much more annoying. > >Specific example was Boots of speed. Instead of have (let's say..) a >stack of 6 boots, you would see all individual boots because they were >all made of different material (leather, snakeskin, etc.) > >So, only way to see that items were made of different materials is to >have them show up individually in your inventory or item stack. > >On a side note.. > >As I recall, the intent of the original author was to deploy a questing >system where a NPC would ask for something like a gold dagger and then >the player would provide that to get a new item request (i.e., granite >stone axe.) > >I personally liked such a concept, but not enough to really want to >endure the issues it causes and mentioned above. > >So, unless some new ways to deploys this can come together, I would vote >for removing this feature. > > > > > >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.4.7 (Darwin) >Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > >iD8DBQFOB4avhHyvgBp+vH4RArETAKCN1W9+ZiR6VWXgm4Bt3cmmeIPb+QCeImjl >Af5fojNj+3v76pqBiveExnA= >=V+4Z >-END PGP SIGNATURE- >___ >crossfire mailing list >crossfire@metalforge.org >http://mailman.metalforge.org/mailman/listinfo/crossfire ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Materials
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I wonder whether to enable that (extended material) support by default and > fix > issues, or totally remove it. > > What do you think? What I found to be irritating about the material code was it made inventory management much more annoying. Specific example was Boots of speed. Instead of have (let's say..) a stack of 6 boots, you would see all individual boots because they were all made of different material (leather, snakeskin, etc.) So, only way to see that items were made of different materials is to have them show up individually in your inventory or item stack. On a side note.. As I recall, the intent of the original author was to deploy a questing system where a NPC would ask for something like a gold dagger and then the player would provide that to get a new item request (i.e., granite stone axe.) I personally liked such a concept, but not enough to really want to endure the issues it causes and mentioned above. So, unless some new ways to deploys this can come together, I would vote for removing this feature. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFOB4avhHyvgBp+vH4RArETAKCN1W9+ZiR6VWXgm4Bt3cmmeIPb+QCeImjl Af5fojNj+3v76pqBiveExnA= =V+4Z -END PGP SIGNATURE- ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
[crossfire] Materials
Hello. In the code is support for "NEW_MATERIAL_CODE". Enabling it randomizes the material for many items, leading to proliferation of items with different materials and properties (more damage to weapons, different resistances, and such). Material support is half-written for multiple combinations (iron + paper for instance), but not totally everywhere. I wonder whether to enable that (extended material) support by default and fix issues, or totally remove it. What do you think? Regards Nicolas -- Mon p'tit coin du web - http://nicolas.weeger.org signature.asc Description: This is a digitally signed message part. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
