Changes between Version 7 and Version 8 of NewEgos


Ignore:
Timestamp:
10/13/11 09:52:53 (7 years ago)
Author:
magnate
Comment:

Some tidying of "other issues"

Legend:

Unmodified
Added
Removed
Modified
  • NewEgos

    v7 v8  
    125125 
    126126=== Other issues === 
    127 A bunch of things occurred to me while doing all this stuff (I'll make tickets) 
     127A bunch of things occurred to me while doing all this stuff (I'll make tickets post-merge) 
    128128* the slay cache can now go, as we're not constrained to a small number of slay combinations which are worth caching 
    129129* we could have a low-level code module for generating lookup tables like flag names (currently duplicated in obj-flag.c and init2.c) and tvals (which we could now do from object_base.txt, removing the need for hard-coding - we could also seek to remove tvalsval.h ...) 
    130 * affixes could change the display colour of an object (Ey has this, and fizzix thought of it too) 
    131 * affixes could be used to generate ego jewelry, which allows re-thinking of what non-ego jewelry ought to be ... 
     130* affixes could change the display colour of an object (Ey has this, and fizzix thought of it too - #837) 
     131* affixes could be used to generate ego jewelry, which allows re-thinking of what non-ego jewelry ought to be ... (it would be easy to regenerate the existing rings/amulets using affixes and themes, while enjoying the extra randomness) 
     132* we should now seek to remove the INSTA_ART objects from object.txt. In fact I wonder if we can already just remove the flag, and leave the base items. Is there any need to remove the base items too? I guess this is related to the issue of ego jewelry above: currently a ring/amulet sval determines its properties (including artifact-ness), but that isn't necessary. 
    132133* allocation of kinds could use the alloc_entry struct (presumably it was written before that struct?) 
    133 * items with alloc_prob 0 should not appear in knowledge menus (the old Bronze DSM problem, now occurring with stuff like Adamantite Plate and Maces of Disruption) 
     134* items with alloc_prob 0 should not appear in knowledge menus (the old Bronze DSM problem, now occurring with stuff like Adamantite Plate and Maces of Disruption) - not sure if this is related to fizzix's bug report 
    134135* speaking of Maces of Disruption, we can't currently generate Deathwreaker. It would be interesting to require artifacts to be generated from certain affixes, as well as from certain base items. i.e. You need a mace, with the Of Disruption affix, before you can generate Deathwreaker. 
    135 * we should now seek to remove the INSTA_ART objects from object.txt 
    136 * should maxima really be sparse? z_info->e_max is set not as the number of e_info entries but the index of the highest.  
     136* should maxima really be sparse? z_info->e_max is set not as the number of e_info entries but the index of the highest. Is this necessary? 
    137137 
    138138== Tickets affected ==