> ## Documentation Index > Fetch the complete documentation index at: https://summer-18f03259-codex-native-multiplayer-entry.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Banned APIs Reference > Complete list of blocked APIs/patterns during Summercraft submission, with rationale and safer alternatives. ## Why These APIs Are Blocked Summercraft's submission policy is designed for creator code that may eventually run inside a shared production sandbox. The static scanner and human review enforce these boundaries today even though the automated production runtime sandbox is not live yet. To protect platform security and stability, submission blocks patterns that enable: * shell/process execution, * uncontrolled filesystem/network access, * runtime reflection/eval bypasses, * loading or embedding unsafe native/binary resources. ## Important: Scanner Is Pattern-Based If a blocked pattern appears in submitted source, upload fails, even when: * it is in an editor/debug branch, * it is inside dead code, * it is conditionally executed. ## Full Blocked Pattern List | Pattern | Why it is blocked | Use instead | | ------------------------------------ | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `OS.execute` | Executes arbitrary system commands on server hosts. | Use Summer SDK gameplay/data APIs. | | `OS.shell_open` | Opens external shells/URLs and escapes runtime boundaries. | Use in-game UI flow; no direct OS shell access. | | `OS.create_process` | Spawns unmanaged processes from game code. | Submitted packs cannot own process control; no production platform runtime is live yet. | | `OS.create_instance` | Creates new runtime instances outside allowed flow. | Use standard scene instantiation and SDK systems. | | `OS.kill` | Can terminate infrastructure or peer processes. | Use gameplay lifecycle APIs only. | | `FileAccess` | Unrestricted read/write to filesystem. | Target the scaffolded `Summer.data` contract; production persistence is not live yet. | | `DirAccess` | Directory traversal/manipulation on host filesystem. | Target the scaffolded `Summer.data` contract; production storage is not live yet. | | `HTTPRequest` | Arbitrary outbound HTTP from game logic. | Target the scaffolded `Summer.data` / `Summer.economy` contracts; their production backends are not live yet. | | `HTTPClient` | Low-level custom network egress from untrusted scripts. | Use SDK networking and platform endpoints only. | | `JavaScriptBridge` | Bridge escape to browser/JS runtime. | Keep logic in GDScript + SDK only. | | `ClassDB.instantiate` | Dynamic class loading can bypass allowed surfaces. | Instantiate explicit scene/resources you control. | | `Thread.new` | Unmanaged concurrency can impact determinism/stability. | Use deterministic main-loop gameplay logic. | | `Mutex.new` | Same as above, often paired with unsafe concurrency patterns. | Keep gameplay state updates on main thread. | | `Semaphore.new` | Same as above; can hide blocking/synchronization hazards. | Use frame/tick-driven state machines. | | `StreamPeerTCP` | Raw socket networking bypasses the platform contract. | Use the Summer SDK transport contract when the production path is available. | | `PacketPeerUDP` | Raw UDP bypasses platform-level auth/routing. | Use the Summer SDK transport and replication contract. | | `TCPServer` | Opens custom server sockets inside creator game scripts. | Keep server ownership outside the submitted game pack. | | `UDPServer` | Same as above for UDP. | Keep networking outside the submitted game pack. | | `WebSocketPeer` | Arbitrary socket communication channel. | Use the Summer SDK transport contract when available. | | `.call(` | Reflection can be used to bypass direct API checks. | Explicit method calls on known safe objects. | | `.callv(` | Same reflection bypass risk. | Explicit typed calls. | | `.call_deferred(` | Reflection/deferred execution can hide unsafe paths. | Use explicit logic flow and signals. | | `Callable(` | Dynamic invocation surface for bypass patterns. | Direct signal/method wiring with known methods. | | `Engine.get_singleton` | Accesses internal engine singletons outside approved API. | Use Summer SDK abstractions. | | `Expression.new` | Runtime expression eval can execute dynamic untrusted code. | Static, explicit gameplay logic. | | `Expression(` | Same runtime eval surface. | Static logic and pre-defined scripts. | | `Marshalls.base64_to_variant` | Unsafe/deserialization abuse vector for crafted payloads. | Use validated JSON and typed schema checks. | | `ResourceSaver` | Writes resource files at runtime; persistence boundary risk. | Target the scaffolded `Summer.data` contract; production persistence is not live yet. | | `ProjectSettings.load_resource_pack` | Runtime pack loading from game scripts is not allowed. | Pack loading belongs to a future runtime; no production loader is live yet. | | `get_node("/root` | Root traversal can reach infrastructure internals. | Use scoped scene tree access in your game subtree. | | `get_node(\"/root` | Same root traversal risk (escaped quote variant). | Use local node paths. | | `get_tree().root` | Global root access to internals outside game boundary. | Access only local game nodes and SDK APIs. | ## Reserved Paths (Blocked In .pck) Packs are rejected if they include infrastructure paths, including: * `res://sdk/` * `res://core/` * `res://server/` * `res://client/` * `res://official_games/` * `res://bootstrap.gd`, `res://bootstrap.tscn` * `res://project.godot` * `res://summer.cfg` * `res://export_presets.cfg` * `res://test_runner.gd`, `res://test_runner.tscn` ## Blocked Native/Binary Resource Extensions Packs are also rejected if they include: * `.gdextension` * `.so` * `.dll` * `.dylib` * `.framework` * `.res` ## Practical Guidance For AI-Generated Code When generating code from prompts: 1. Never generate “debug fallback” branches with blocked APIs. 2. Prefer SDK primitives (`Summer.data`, `Summer.economy`, score/teams/sync helpers). 3. Keep all file/network/process interactions out of creator game scripts. 4. Use explicit method calls instead of reflective invocation helpers. The alternatives in this table are contract guidance, not a deployment-status promise. Check [platform capability status](/knowledge-base/source-status#platform-capability-status) before promising hosting, matchmaking, transport, persistence, or economy behavior. ## Related Docs * [Exporting and Uploading Your Game](/api-reference/summer-sdk/exporting-and-uploading-your-game) * [Submission Guide](/api-reference/summer-sdk/submission-guide) * [AI Agent Playbook](/api-reference/summer-sdk/ai-agent-playbook)