Changes between Version 2 and Version 3 of PvalHandling


Ignore:
Timestamp:
04/25/11 18:15:41 (8 years ago)
Author:
magnate
Comment:

Formatting

Legend:

Unmodified
Added
Removed
Modified
  • PvalHandling

    v2 v3  
    1717   - if not, work out what its new value should be and add/move it to the closest pval[[BR]] 
    1818 
    19 -- this is now object_add_pval in pval.c, and is called from ego_apply_magic. It will also be called from randart.c. It isn't necessary for standarts, because artifact pval details are copied wholesale, as artifact definitions are assumed to overwrite anything on the base item. N.B. #120 was completed first. 
     19-- this is now object_add_pval in pval.c, and is called from ego_apply_magic. It will also be called from randart.c. It isn't necessary for standarts, because artifact pval details are copied wholesale, as artifact definitions are assumed to overwrite anything on the base item. N.B. #120 was completed first.[[BR]] 
    2020     
    2121This is currently impossible due to the way object_flags and object_pval_flags work, and can only be done once o_ptr->flags is canonical. But that's on the radar (see http://angband-dev.blogspot.com/2011/03/so-i-finally-managed-to-refactor.html), so this is possible. There are two other possibilities though (and maybe more):