Todd Mitchell wrote: > On Fri, 2003-12-19 at 00:54, Mark Wedel wrote: > Yes, exactly - excellent. This is what I mean by modular as well - body > parts do not have to be wrapped up in a parent treasure list any > longer. This makes it easier to have a dragon cleric without making a > dragon_cleric treasurelist - just add dragon_bodyparts and > cleric_treasure... Note that in a large sense, that could be done right now - it would just require more treasurelists. At some level, the archetype treasurelists should probably still get collected into the treasures.bld. The ability to customize treasurelists on an object level is most useful for map design. OTOH, it wasn't until recently that collections of .trs files was added - really, there shouldn't be any treasures file at all - it should be 100% generated - that would also make it easier to deal with the treasures (most likely), in that the dragon treasure would be right with the dragon creature - you wouldn't have to go searching through the treasures file to find the dragon treasurelist. That in its own regard may make the treasurelists better - having a 50 line treasure file for a creature probably isn't that unreasonable, and you may better customize the treasures. Where as with a common treasures file, there may be more perceived need to recycle treasures. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel