Flowchartless operation

[stevehalliwell]

A number of questions and requests around either creating flowcharts at runtime or using parts of fungus without using Flowcharts, Blocks, and Commands to talk to systems. Creating flowcharts at runtime is not recommended and often using parts of Fungus is very dependant of the code running inside a Command's OnEnter.

Describe the solution you'd like Moving much of the intricate logic out of commands and into systems themselves, similar to Conversation, would allow users to more easily extend and manipulate Fungus from script or potentially use Fungus without flowcharts at all.

Additional context This would have a nice side benefit of making it easier to update editor systems in the future, as most Flowchart and other elements based on MonoBehaviours would only be corralling data to give to systems, not the logic to make them run. It would also make writing editor and playmode tests for Fungus systems easier as they would not have to be tied to a editor prefab with a flowchart on it.

This may also increase the likelihood of addition community contributions as there will be lower required understanding of Fungus' Flowcharts in order to achieve a minimum desired result.

[breadnone]

This actually a brilliant idea, it also opens the possibility for users to build their own VN framework on top of Fungus, currently this is not possible due to how Fungus relies heavily to prefab-workflow and how little the internal APIs being exposed.

And please, Fluent like API :)