Visual Scripting Limitations

In order to maintain compatibility with all of our platforms, and to create a secure experience only nodes in a pre-defined set are allowed to be used in Spatial. If you try to use an unsupported node you will be notified in the issues tab and be blocked from uploading.

What Nodes Can I Use?

The Creator Toolkit limits the nodes that appear in the add-node menu such that almost all nodes available in that menu are compatible. Currently we support over 15,000 nodes from the following modules mscorlib UnityEngine.CoreModule UnityEngine.AudioModule UnityEngine.PhysicsModule UnityEngine.AnimationModule UnityEngine.UIModule UnityEngine.UI Unity.TextMeshPro + all custom-made spatial nodes.

What Nodes CAN’T I Use?

We can’t list all 5000+ currently blocked nodes here… but here are some common nodes we have blocked: Any Application node like Application.OpenURL Any GameObject.Find variant Any GameObject.SendMessage variant Any Expose node Any Scene or SceneManagement related nodes

No Plugins or Custom Nodes

All nodes generated by plugins you downloaded from the asset store, or created yourself will be blocked. SubGraphs that only contain supported nodes should work just fine.

I Need to Use ___ Node But It’s Not Supported

If you need functionality of a certain node/module that is not supported definitely let us know! We might be able to expand our supported modules or write similar functionality in a spatial-unique node. The best place to give this kind of feedback directly to the team is the Creator Toolkit section of the Spatial Discord

• Visual Scripting Limitations
• What Nodes Can I Use?
• What Nodes CAN’T I Use?
• No Plugins or Custom Nodes
• I Need to Use ___ Node But It’s Not Supported