To be honest, with the current set of features, i'm not sure why i would go with the Flowchart instead of the Arrays (or JSON). Because Array would also allow us to store any number of values ("unlimited column numbers", while Flowchart are just more retrictive and require to parse data contained in just a 3 values max - Name/Value/Tag, it means potential huge token list which are not always very pleasant to deal with).
JSON would even allow us to nest and manipulate any amount of Data/arrays/Dictionaries for each nodes.
So IMO right now Flowcharts compete with Data Plugins while they could become something new that synergize well with Eventsheets
100%, this is also the conclusion I've come to. This is such an exciting feature, and it could be a truly great addition to Construct, but I wonder if it's being designed functionality-first instead of use-case-first.
In the end, Nodes should a) improve workflow of existing methods (make it easier to do what users already can do in Construct); b) make it possible to create new methods with the same ease as Construct (FSM, Dialogue, Quests); or ideally c) both.
That's probably obvious, but if superior workflow and additional capability can't be achieved with nodes in c3, nodes shouldn't exist in c3. There's been a few additions to construct that felt designed in an engineering bubble, and I really hope that all the amazing users here can guide nodes to a truly useful and powerful addition.
It's amazing that this conversation is happening and there are so many great ideas being shared. I can't wait to see how it progresses!