2009-10-11, 06:14 PM
Well one reason your analogy breaks down, is the event file records are basically just headers. The most interesting piece of data in the headers is an offset further into the file starting after the last event record, which is basically fully dynamic. What is in the event records, is really just one of these offsets for every "leaf" in the event. These offsets are not necessarily allocated in order also... I think they're allocated in the order you first added an instruction to a leaf. All the leafs in an event otherwise seem to stay side by side one another (that is I have yet to see leaf data for different events interleaved)
But all of that is beside the point. I would think SOM would just completely overwrite one file at a time, but I suppose it's possible it does not. In my opinion whenever you have a button or something that says "save" it should be a complete overwrite. But maybe SOM doesn't care about my opinions
Still if it wasn't a complete overwrite I don't think SOM would always take so long to save. The build definitely seems to rebuild the entire shebang. So my guess is still it does do a full save. Which if so would mean maybe your problems arose from SOM not being able to save all the files to be in accordance with one another... but that I think would've required you to have hit the save button at nearly the same time for both instances of SOM... or at least while one SOM was still working on a file. It's also possible SOM decided you didn't make any changes that would warrant saving all the files, so you ended up with one file pertaining to one instance and another pertaining to another.
The evt files don't care about what's in the map. Really the only prob you'll run into is if the object/npc/monster your event is associated with does not exist (it's number that is) ...then SOM might crash when opening the map or something.
But all of that is beside the point. I would think SOM would just completely overwrite one file at a time, but I suppose it's possible it does not. In my opinion whenever you have a button or something that says "save" it should be a complete overwrite. But maybe SOM doesn't care about my opinions
Still if it wasn't a complete overwrite I don't think SOM would always take so long to save. The build definitely seems to rebuild the entire shebang. So my guess is still it does do a full save. Which if so would mean maybe your problems arose from SOM not being able to save all the files to be in accordance with one another... but that I think would've required you to have hit the save button at nearly the same time for both instances of SOM... or at least while one SOM was still working on a file. It's also possible SOM decided you didn't make any changes that would warrant saving all the files, so you ended up with one file pertaining to one instance and another pertaining to another.
The evt files don't care about what's in the map. Really the only prob you'll run into is if the object/npc/monster your event is associated with does not exist (it's number that is) ...then SOM might crash when opening the map or something.