Repository navigation
Add hosted website builds for all scripting languages - #86
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Website exports reject games using Luau, Python, C/C++, C#, Java or PHP because their native process adapters cannot run inside the static WebAssembly player. Add Hosted runtime (all scripting languages) under File → Build Project → Website, packaging the native runtime, verified game data, player and launchers. Browsers send keyboard/mouse/touch input over a same-origin WebSocket and receive PNG frames and mixed audio from independent native sessions.
New build settings select hosted mode; existing saved settings retain static WebAssembly. Hosted games require a matching GPU-capable server with the external toolchains used by the game. The static mode keeps its existing supported languages and static-host deployment. Each hosted connection gets temporary writable files, bounded input/audio, connection limits and timeout cleanup. External toolchains are checked before hosting starts.
Update the engine build guide, generated package instructions and bundled agent authoring guidance. No MCP tool changes are needed: exporting remains an editor-dialog operation. CI now exercises the hosted session against every adapter and a real WebSocket/rendering/Python-input smoke test.
Validation:
powershell: command not found). Keep this PR draft until the required Windows installer and full adapter CI checks pass; no fresh installer was produced locally.Documentation: https://rustic-game-engine.pages.dev/docs/guides/editor/build-project