Kyatric: I'm not sure what it is called exactly but node index seemed logical. Example:
/bookstore/book Selects the first book element that is the child of the bookstore element.
For some of the examples I have seen it won't be different at all than using IDs but it can save a lot of work in some cases. A lot of times I have used xml has been for dialogue and intro/story where it is subject to a lot of change but I never have to change any id numbers or anything.
The reason why I am asking is that not too long ago I knew nothing about xml. So I want to keep learning and figure out if there are better ways. Also, haven't done one before but was thinking about writing a tutorial on it.
If you want to see some capx: (sorry, they aren't examples, just things I have worked on before, so lots of other stuff in them)
Chooses random node (between 1 and node count):
First time using XML, simply changes text every couple of seconds to the next line. Once at end (variable > nodeCount) starts over. I bookmarked the event:
https://www.dropbox.com/s/fvytszs9v3bup ... .capx?dl=0
Something I'm working on now, bookmarked a couple of events. Can talk to people and just got it working where npc can ask you a question and have a response for each answer:
https://www.dropbox.com/s/eschjyoosogyc ... .capx?dl=0
Take a look at the XML sheets in some of these. The Construct events probably won't vary much from your examples but the XML is more straightforward and easier to read. I was looking at your examples and was having a hard time following the XML. Your way works, so there is nothing wrong with it, and it probably helps other people so great, but I didn't want to change my whole system so figured out how to work it with what I had already.
Let me know what you think. That is why I am asking, not to be critical but to get your insight.