Changes between Version 4 and Version 5 of NewEgos


Ignore:
Timestamp:
10/13/11 07:19:56 (8 years ago)
Author:
magnate
Comment:

Added ref to list-flag-types.h and list of tickets affected

Legend:

Unmodified
Added
Removed
Modified
  • NewEgos

    v4 v5  
    2222* The C: line now takes seven parameters rather than three. As well as to_h/to_d/to_a, you can now modify base AC, weight, dice and sides. The first two of these are percentage mods (and are signed so can be negative), the last two are just extra dice and sides (but can also be negative). Full credit to Eytan Zweig for inspiring these. 
    2323* The M: line is assumed to be NO_MINIMUM:NO_MINIMUM:NO_MINIMUM if it's absent. So no worries about accidentally removing armour penalties. 
    24 * The X: line is gone. Rarity is no longer used, and random flags are now done by R: or R2: lines. R: lines specify flag types (sustains, high resists, etc.), while R2: lines allow specification of an exact flag mask. So if you want, you can have an affix that adds one of SUST_STR or SUST_CON but nothing else. You cannot add pval flags this way though - I wrote a spec for a Z: line to do this, but it is difficult to box around MAX_PVALS so I have left this for another day. 
     24* The X: line is gone. Rarity is no longer used, and random flags are now done by R: or R2: lines. R: lines specify OFT_ flag types (sustains, high resists, etc. - now in src/object/list-flag-types.h), while R2: lines allow specification of an exact flag mask. So if you want, you can have an affix that adds one of SUST_STR or SUST_CON but nothing else. You cannot add pval flags this way though - I wrote a spec for a Z: line to do this, but it is difficult to box around MAX_PVALS so I have left this for another day. 
    2525* The T: line now deals with rarity as well as kind legality. For each tval/min-sval/max-sval group, you can specify an alloc_prob and a min and max depth. EGO_TVALS_MAX has been increased accordingly (and could go further). So you can have the same affix appear with different likelihood and at different depths for different items. Acid-resistant shields can be much rarer (or less rare) than acid-resistant cloaks, for example. 
    2626* The T: line also includes a "level" field, which specifies how good the affix is considered for this object group at these depths. So far I've defined four levels: "good", "great", "uber" and "artifact", but we could have more. The last is in case we want to have affixes only found on randarts (e.g. immunities). More on levels in a minute, but one point to note is that you can redefine the ''same'' object group here. So: 
     
    123123* we should now seek to remove the INSTA_ART objects from object.txt 
    124124* 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.  
     125 
     126== Tickets affected == 
     127 
     128[[TicketQuery(Keywords~=affixes,format=table)]]