Adding execution pins automatically to is_
or get_
prefixed script functions introduces backward incompatibility
#622
Labels
bug/confirmed
Bug/regression has been confirmed.
cherrypick:2.0
Requires cherry-pick to Orchestrator 2.0
kind/bug
A bug or regression in expected behavior.
Milestone
Describe the bug
In #583, a change was added that allows the
is_
andget_
user-defined functions always to render execution pins. The problem is that this introduces a backward incompatibility with existing Orchestrations, making them inoperable.Expected behavior
Old orchestrations should continue to work.
Actual behavior
Old orchestrations that have
is_
orget_
prefixed functions cease to work.How to Reproduce?
No response
Godot full version
No response
Orchestrator version
No response
Additional information
To make this backward compatible, we could add a flag to each
OScriptNodeCallScriptFunction
node that tracks whether to display the execution pins. By default when loading older orchestrations and the function name begins withis_
orget_
, the flag would be set tofalse
to remain backward compatible.For newly added/placed nodes, the flag would be set to
true
for all script function calls.Question: Should this flag be togglable in the inspector?
The text was updated successfully, but these errors were encountered: