NPCData, ComboData, SpriteData

[Tamamo]

You do realize some shit is suppose to be read only for a reason right @ZoriaRPG ?
I don't even know if you know what your doing anymore... O_O

[Dimentio]

You do realize some shit is suppose to be read only for a reason right @ZoriaRPG ?
I don't even know if you know what your doing anymore... O_O

How is making useful variables write-able bad, if you make them work as you'd expect? Are you just against the adding of any new feature?

[ZoriaRPG]

You do realize some shit is suppose to be read only for a reason right @ZoriaRPG ?
I don't even know if you know what your doing anymore... O_O

Of course I know what I'm doing. Writing occurs to the buffers, not the physical tables; just as with itemdata, and it is not retained/written out. There is absolutely no difference in writing to guysbuf[id].member. than writing to itemsbuf[id].member; and similarly, writing to ComboData[id].member is lready partially implemented, albeit poorly, with SetCombo* functions. This also has appropriate approval, and blessings and is tied into other improvements.

This stuff was not read-only in the past. it was flat-out, never implemented; and FWIW, some stuff is read-only because no-one ever finished it in the past, or they were unable to work out issues that arose at the time. If any of the setters prove to be unstable, or buggy, I can disable them until we find a suitable work-around, but I do not anticipate much havoc, save from users who fail to read the documentation.

In conclusion, you are again seemingly complaining, purely to complain. Nothing new there, but thank you for stopping by.