Visual Scripting - Problems with Calling Scripts After Adding Input Parameter

There are two bugs with Visual Scripting that are triggered by adding an Input parameter to a script. The problems happen when you have 2 scripts and one calls the other. In this example, ParentScript calls ChildScript. ChildScript has several input parameters. We start with both scripts being wired up correctly, valid and working as expected.

To trigger the bug, add a new Input parameter to ChildScript. Now open ParentScript. At this point one of the following may happe:

1. All inputs to ChildScript have been detached so ChildScript is no longer wired up at all
2. ChildScript is still wired up except for the new input.

Case 1 is really annoying in a complex script because it's so hard to know how ChildScript was wired up before you changed it. You can't use a diff tool because scripts are XML not plain code. In practice, you mean need to undo the changes with Git or something similar, load the original script and make a note of the wiring so you can reproduce it. Then you can go ahead, make the change and re-wire it.

Case 2 looks good but isn't. If you can wire up the new input you may find that ParentScript no longer builds. The error is "Script node ChildScript missing input data...". If you check ParentScript you'll see that all the inputs are wired up. If you now, detach and reattach all the inputs to ChildScript it will now build. e.g.