Development workflow
Use this workflow after setting up a local server.
Apply script and UI changes
Section titled “Apply script and UI changes”-
Edit your project files. If you use a compiler or bundler, rebuild the changed target and wait for it to finish.
-
Press Ctrl+C in the server terminal and wait for the process to exit.
-
Start the server again from its folder:
Terminal window .\revo-server.exe
Keep GTA open. After the connection closes, the client retries automatically. Once the server is available, it checks for resource changes, prepares the updated bundle, and starts the client scripts again.
Server scripts, client scripts, and a WebView frontend can have separate build
steps. Only rebuild the targets affected by your change. Their output paths must
match the server entry and client resource folder in config.toml.
A build tool’s watch mode can keep these outputs up to date. The local server packages client files at startup, so saving or rebuilding them still requires a server restart.
When to restart GTA
Section titled “When to restart GTA”| Change | Required action |
|---|---|
Server scripts or config.toml |
Restart the server. Existing clients reconnect. |
| Client scripts, WebView files, or scripted audio | Restart the server to package the changes. GTA can stay open during reconnect. |
| Native game assets | Restart the server, then follow any restart message shown by the client. Adding or removing native assets and changing game metadata, maps, or collision files require a GTA restart. |
| Revo client binaries | Close the running GTA clients and launch through the helper again. |
If the client requests a restart, close GTA and run the launch command from the connection guide.
Test with two local clients
Section titled “Test with two local clients”With the first client connected, run this command again from the helper folder:
.\client-helper.exe launch --join-code devThe helper opens another GTA client with a separate profile. It prepares the profile automatically and shares the downloaded resources.
Multiple Release clients are supported through dev or dev:<port> when the
server resolves to 127.0.0.1. Public-server connections run as a single client.
Use both views when checking multiplayer behavior:
- Perform an action in one client and observe it from the other, then swap roles.
- Join the second client after creating an entity or changing its state to check what a late joiner receives.
- Restart the server with both clients open to check resource updates and session cleanup.
Launching through the helper again creates another local client. The existing client reconnects on its own after a server restart.
Read the logs
Section titled “Read the logs”For console filters, commands and connection readings, see Console and network graph.
| Location | What to check |
|---|---|
Server terminal and logs/revo-server-runtime.log in the server folder |
Configuration, resource packaging, server script startup, and errors. |
| F2 console in GTA | Client script output and runtime errors. Requires console = true under [client_features]. |
<storage>/projects/<projectId>/logs/revo-client-runtime-<session>.log |
Client startup, connections, resource updates, and script errors. |
<storage> is the resource storage folder selected during
client setup.
Each client launch creates a separate log. <session> contains the process
start time in UTC and its PID.
If a change does not appear, check these in order:
- The build completed and wrote to the configured entry or resource folder.
- The server restarted successfully after that build.
- The client finished reconnecting without a resource or script error.
A temporary startup log message with a revision label can help confirm which script version is running.