I've been using both C# script and schematics. So far only use the schematics when following tutorials, and script everything else. This question is me trying to understand what is the design goal of ORK schematics.
So I understand that schematics is pretty much Makinom's own visual scripting tool, and I have no doubt that it would be the tool of choice if everything I develop relies on ORK.
My question is, in a scenario where there are a large part of the game not done in ORK (in C# script in my case, but for others it would be other visual scripting tool), what should be the preferred tool?
https://makinom.com/guide/documentation/features/schematics/ mentions schematics is good for
communication with 3rd party software
An example scenario for discussion purpose:
Say a game mixes RPG with other game genre. Of course ORK is excellent in handling anything RPG-related, but when it comes to the non-RPG part of it, is there any advantage of using ORK schematics to do as much as possible? (For example write nodes for functions that both ORK and Makinom do not provide, use schematics just like a generic visual scripting tool)
Or, the design intention of ORK schematics is more encouraging on design the non-RPG part of the game in script or other visual scripting tool, and then somehow interfaces the two systems?