Robin Redeker wrote: > We are very open to improvements. And maybe someone could discuss the > problem with the order of map objects. The problem is, that if we load a > map in GCE and save it again, we get many changes in the order of the > objects.
The only requirement is that the order the objects appear in is there stacking. Thus, if aboves (on the same space) show up as 'a, b, c', then a is at the bottom, c is at the top. When things are saved out, that order needs to be preserved - if you save as 'c, b, a', then objects c & b are going to disappear beneath the floor Now for fields within the object itself, there really isn't any required order. You can save 'sp xx, hp xx' or 'hp xx, sp xx', and it won't care. One thing it may care about is that the max_... values be before the values they refer. This is simply because there is some code that checks the sanity (OTOH, IIRC, that code isn't run until the object is fully loaded, so that order doesn't make a difference). So in this case, the only real importance in ordering the fields is trying to keep it the same to minimize the number of changes (so that only stuff that really changed shows up). The other standard behaviour is only fields that differ from the archetype are written out. So there is no reason to write out the hp values for all the monsters unless they are the same, for example. _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
