How to limit the scope of available functions?

[anton petrovParticipant]

I want to make specific flow scripts. For example specific “Quest Script” or “Player Ability Script” and I want some limited API to be available there so that game-designers were not lost in the forest of possibilities.

Is it possible some how?

Thank you!

[GavalakisKeymaster]

Hello Anton,

Unfortunately right now there is no ability to limit the possible options shown other than using the Preferred Types Editor. The types in the list of the Preferred Types editor are a way of limiting possible options (members declared in those types), but I presume you mean something even more restrictive? If so, do you have any suggestions on how would this work (front-end wise)?

Thanks!

[anton petrovParticipant]

My first idea is to have all nodes organaized by category first and not by their type. See CryEngine’s FlowGraph window panel 2:

Then you can have checkboxes which enable or disable qick search through corresponding categories.

Ofc, it is not a blocker, I am trying to reduce a cognitive load for game designers ))

[GavalakisKeymaster]

Hey,

Categorizing reflection-based functions or types alogether will require manually deciding and creating some kind of a “map” to categorize them. In CryEngine these categorizations are probably made by namespace, however in Uniy most types are simply in UnityEngine namespace and without any further sub-namespaces, but I will try to think of something in this regard. 🙂

Thank you

[anton petrovParticipant]

Suddenly I came to an idea that we can have an extension point to filter what types are displayed in that graph.

We should be able to somehow register our custom graph type and specify a filter of node types available to that type of graph.

The first idea is to inherit FlowGraph and override some virtual method which filters node types or something like that :thinking_face:

 

[GavalakisKeymaster]

Hey,

Yes that is also possible. It could also be done via some inspector per-graph without the need to derive FlowGraph. 🙂 However, the question still remains on what/how the filter should work? Would it be per Type (including all its members like existing Preferred Types), or per Member (which would of course require a really heavy time on setup and I think is very cumbersome). 🙂

[Author]

Posts