Talk:RSAV
The Mad Cacti: Woot!
Re: NPCs, stats, and caterpillar slots: By "0 to 299 - for each npc" I guess you probably meant container nodes named 0 to 299, but that seems like the wrong way to do things: inefficient, possibly annoying, and extremely counter-intuitive when viewed from an xml mindset. I suggest instead using npc as the name of each npc node, and its value can be an integer (of course, in xml you would use an "id" attribute or child, but...). Remember that all RELOAD nodes can have children, not just container nodes.
Also, my suggestion for the "npcs" node: instead of making it a child of the root rsav, how about a more forward-thinking hierarchy like:
- rsav
- maps - stores map states
- map int - value is a map ID (initially, only one map node; the current map)
- npcs
- npc int - value is an npc reference
- ...
- npc int - value is an npc reference
- npcs
- map int - value is a map ID (initially, only one map node; the current map)
- maps - stores map states
Bob the Hamster: Hmmm. Okay. I do like the idea for storing maps like that. As for the NPCs, I understand what you are saying, and I see no problem with changing to name the nodes npc and give them values of the ID number, but I don't understand why that would be any more efficient. I wasn't really approaching this format from an XML mindset (even if the XML output happens to be a convenient way to visualize it)
