Language direction
ESB Studio scripting is being designed around Lua. The goal is to give creators a familiar, readable scripting language for game logic while ESB Games defines the platform-specific runtime, services and security boundaries.
What creators should expect
- Scripts attached to appropriate project objects or runtime locations.
- A script editor and output/debugging workflow inside ESB Studio.
- Documented client/server or execution boundaries once those contracts are stable.
- Platform APIs that are versioned and documented before creators are expected to depend on them.
- Security restrictions that prevent scripts from bypassing platform permissions or accessing unauthorised data.
Why there are no fake examples here
A code example becomes a compatibility promise very quickly. Until the actual runtime surface is stable, ESB Games would rather publish a smaller accurate guide than documentation for functions that may not exist in the shipped product.