Code & Custom UI
Most Portals game ideas can begin with visual building tools and Interactive Studio. Move into code or a custom interface only when your tested no-code version cannot express the player behavior you need.
Choose the simplest tool that works
| Need | Start with |
|---|---|
| Place, move, and configure world content | Build Your Game |
| React to a player action without writing code | Interactive Studio |
| Combine values and conditions in visual game logic | Function Effects |
| Run supported custom game behavior | JavaScript Function |
| Show a custom in-game interface | displayHtml and the supported JavaScript bridge guides |
| Ship your own HTML, ThreeJS and JavaScript game instead of a room | Web Games |
Build the interaction before the interface
For example, make a door open with a task and effects before you build a custom door-control panel. When the core behavior already works, a custom interface becomes a focused improvement rather than a second way to debug the same problem.
Keep custom work testable
- Give every interaction a player-visible result.
- Start with one small supported function.
- Test after each change from the intended player spawn.
- Keep a no-code fallback while you experiment.
- Use the JavaScript reference for supported functions instead of assuming browser APIs are available in the game runtime.