This would require sanitizing the strings from the name entry box for the editor, the compile tag for the mod, and the slot name for exports for the mod.

There are many examples of nodes that have two versions, one that has a Context generic attribute, and one that doesn't. This includes, but is not limited to, Value/ObjectWrite, Value/ObjectWriteLatch, ValueIncrement/Decrement, and a bunch of other Action and Flow nodes.

For whatever reason, a script I exported from an existing ProtoFlux script used the dual generic Context version of ValueWrite rather than the single generic version. It gets exported completely fine, and in the editor it also works completely fine, but when compiling it back, the Variable reference refuses to connect.

Edit: I figured out why it wasn't compiling, I was previously writing to a DataModelStore, and switched it to a Store for network optimization purposes. The dual generic was using FrooxEngineContext, while Store only implements ExecutionContext, so the actual bug there is that the editor allowed the connection at all. There's still probably other edge cases involving execution contexts.

I have no idea why the script used the dual generic version, my guess is early Resonite shenanigans, and I have no idea why it does not compile properly. The game probably auto-casts the non-context nodes to context nodes despite not needing to, so while I likely originally spawned a non-context node when I originally wrote the script, the game converted it, and it ended up like that when I exported it to pfscript. There are likely other edge cases involving these nodes that needs to be investigated, and if there's truly no fix, then they should be automatically converted to the proper single generic versions of the nodes.