Roblox enforces a security model based on where code runs and which APIs it can call. Main dimensions - Client versus server scripts - Normal scripts versus Studio plugins - In game code versus external Open Cloud tools Client side LocalScripts - Can read local player input and camera state - Can change local UI and some visual aspects of the world - Cannot write to DataStores or make HttpService requests - Should never contain secrets or API keys Server side Scripts - Can write to DataStores and MemoryStores - Can use HttpService to talk to external services - Are authoritative for game rules and anti exploit logic - Must assume untrusted clients and validate all remote events Studio plugins - Run only inside Studio not in published games - Can access the developer s machine in limited ways such as reading plugin settings and some file dialogs - Must not be used as a backdoor to exfiltrate data or credentials Open Cloud tools - Authenticate with API keys owned by the creator or group - Are scoped to specific permissions such as DataStore read write or asset management - Live entirely outside the Roblox client and server code paths # Third Party Apps Third party apps are external tools or websites that connect to Roblox via Open Cloud A third party app can - Read and write DataStores for a specific experience - Manage assets and place versions as part of a CI pipeline - Provide dashboards and configuration UIs for creators A third party app cannot - Log in as a player account or ask for Roblox passwords - Circumvent the permissions system attached to its API keys - Run arbitrary code inside a live Roblox client For a Hitchhiker ecosystem a third party app can become the central brain for things like Voz and the Hitchhiker Passport while respecting Roblox boundaries # Limitations For Child Safety Many Roblox technical limitations exist specifically to protect children Important constraints - No direct real money payments in scripts only Robux purchases via official APIs - No raw network access that could leak IP addresses or identifiers - No webcam or unrestricted microphone access from Luau - Strict rules against unmoderated user generated text and images depending on the game s age rating These constraints shape how coding extensions must be designed Any Hitchhiker style system needs to work within these limits and treat Roblox as a partially closed garden # Example Hitchhiker Integration A simple end to end pattern for extending Roblox with Hitchhiker logic - In game Luau modules implement UI for Voz the Hitchhiker Passport and the Hitchhiker Guide - Server scripts call HttpService to send anonymised events to a Hitchhiker backend such as session summaries or Voz increments - The backend aggregates events into per player and per project stats and stores them in its own database - The backend uses Open Cloud DataStore access to set high level flags and totals that games can read at login - Studio plugins help creators wire up this pattern by inserting modules remotes and configuration templates into their places The result is a connected ecosystem of Hitchhiker games that all respect Roblox s sandbox but share a common external brain # Extensibility Boundaries When designing coding extensions it helps to think in layers - Inside Roblox you can extend behaviour through Luau scripts services and Studio plugins - At the platform edge you can extend tooling through Open Cloud APIs - Beyond Roblox you can build full custom systems that interpret Roblox events but cannot reach back into the engine except through official gateways If a proposed extension needs more than these layers offer it is probably outside the Roblox model and better suited to a different platform or a parallel web mobile experience linked via accounts # Open Questions Topics for further pages - How to version and share Hitchhiker focused Luau libraries across many games - How to sandbox community contributed code modules safely - How to document extension points for creators who are new to Roblox but familiar with other engines - How to blend Roblox coding extensions with non Roblox tools such as web apps or real world workshops in a coherent narrative