Project looks great!
I have a question though. If making a RPG game with this with a lot of tree's, does the code and variable tracking become overwhelming long? Looking forward to seeing more of it and possible a clean solution to implementing a system with a big story.
So basically right now the dialogue loads all your nodes and parses them - you then call a start("nameofnode") method and you can specify what node to start from("Start" by default). You then step through the dialogue by consuming results with the dialogue.getNext() method kind of like an iterator. These results are things like your Lines/custom commands/options(these link to other nodes which can be in the same file) ect.
I could go into more depth which i think ill save for the wiki(unless requested here) , but basically once you implement the dialogue into your game and are able to read the results - it becomes really easy and scale-able.
The Variable continuity that comes with the lib comes with built in functions so that you can serialize it into a json string: this makes it easy to save it. Also you may use the same variable continuity for different dialogues so you could make the continuity a global variable that you access from anywhere in your game that your dialogues interact with.
To clarify: all the variable continuity is(
UserData.java) , is a <String,Value> object set(objectmap).
TLDR: Keeping track of your variables should not be an issue - i think the hardest part will be implementing it to fit your needs and then its just a matter of loading your dialogues and using the results. Saving the variables is really easy with the toJson(), and fromJson() methods; and you can use the same variable storage for multiple dialogues.
Hope that cleared some stuff up.
Feel free to ask any more questions i am happy to help
