This Gist is an initial collection of in progress tools for debugging the Visual Scripting language in GotchaGotchaGames' Action Game Maker fork of the Godot Editor.
These GDScripts extension that can be assigned to the Script property for VisualScriptAction (States) and VisualScriptActionLink (Links) to add additional debugging and execution tracking options. This is not yet a full plugin repository because this very much in rough Alpha state. The public knowledge of avaliable AGM APIs is limited https://guild.rpgmakerofficial.com/t/topic/35 .
If you have suggestion or would like to contribute, the current working thread is on https://guild.rpgmakerofficial.com/t/topic/213 . The goal is to either demonstrate or create debugging tools that no/limited coding designers can use to troubleshoot their Visual Scripts.
Check Gist commit history for changes.
AGM API assumptions:
GameObject that executes VisualScripts is a CharacterBody2D. It is unknown how or if VisualScript is split between _process and _physics_process. For safety modifying Conditions and Actions arrays should be done by call or set deferred. Same for directly modifying Condition and Action resources. Let AGM finish the frame, then update any arrays or properties. If dynamic changes are executed from a Node, use _physics_process.
AGM API facts: