📄️ Design
Godot Sandbox is serious software. It requires knowledge about build systems, deep knowledge about C++ and does not have a design goal of being zero upfront effort. It's main task is to provide high-performance safely-sandboxed functionality to games intended for an audience. That said, it does have a goal of being low effort once it has been set up properly.
📄️ Unboxed Arguments
Unboxed arguments is a default-enabled property on a Sandbox node. It makes function calls into the Sandbox unwrap Variant arguments into primitive types or class wrappers when available. These class wrappers aim to provide the functionality of both GDScript and godot-cpp when it makes sense to do so.
📄️ CMake Projects
It's possible to use complex projects with dependencies while scripting with C++ in Godot.
📄️ C++ Examples
Currently, the Godot Sandbox has access to all of Godot through calls, properties, objects, nodes and so on. This might not be apparent from looking at the APIs, especially if one is unfamiliar with how Godot works under the hood.
📄️ Memory
Memory in the Sandbox works just as you would expect. If you store something in memory, it will be there when you come back. All language-native code will work like normal, until the Sandbox is freed.
📄️ Adding sugar
Sugaring
📄️ Binary Translation
alt text
📄️ Modding and APIs
Loading programs at run-time
📄️ Profiling & Debugging
Live-profiling
📄️ Restrictions & Isolation
Enabling restrictions
📄️ C++ API Reference
The current C++ API is likely to change over time, however it is mostly complete. Feel free to contribute improvements to the API. The run-time generated API comes in addition to this API and covers the rest of Godot by adding all classes known at run-time, including loaded extensions.