Host overview
Original 2016 engine · on-demand places ·
Hosting controls
Available to players. Game engines start when requested.
CPU history
Last 10 minutesMemory history
MiB · tracked processesRuntime & storage
- Manager uptime
- —
- Cached original places
- —
- Original place bytes
- —
- Disk free space
- —
- Inactive place expiry
- —
- Expired this run
- —
Network & transfers
- TCP fallback listener
- —
- TCP connections
- —
- Received / sent
- —
- Transport errors
- —
- Place uploads
- —
- Public tunnel route
Needs attention
Waiting for host status…
Active places
Original place library
Exact files, separate engines, automatic three-day inactivity cleanup.
Files are imported byte-for-byte. Verification checks the header, fingerprint and SHA256; gameplay and rendered appearance need their own checks. Active engines and recent downloads are protected from expiry. Saves remain separate.
Players & joining
Actual engine rosters, grouped by place.
Connection details
- Website
- —
- Game connection
- —
- Discovery & transfer
- Included in the TCP fallback connection
- Join grace
- —
A saved address does not establish public reachability.
Avatar & gear diagnostics
This engine reports rosters and logs, not per-player rendered outfit telemetry. An accepted outfit message confirms a server submission; it cannot confirm how an avatar looks on a client. Use the avatar log filter to inspect dependency, outfit and respawn messages.
Live host logs
Waiting for logs…
Power and place controls use the dedicated buttons. This panel does not expose a system shell or pretend to support engine console commands.
Manager operations
Home server & tunnel
Verify the deployed route before using this address.
Two routes, one clear address
HTTPS proxy or web tunnel → local manager on 127.0.0.1:31880.
Raw TCP relay → host TCP fallback on port 31876. Includes discovery, original-file transfer and gameplay.
An ordinary website tunnel is not a raw game connection. Cloudflare's published TCP applications require client-side cloudflared; the existing Vita protocol needs a reachable raw TCP endpoint. Protocol details ↗
Setup checklist
- Copy the verified host pack.Linux x86 with i386 support, content, original files, saves and inactivity history. Verify the hashes after copying.
- Set a separate manager password.Create the password hash locally, then enable the loopback manager. The reference website password is not bundled.
- Connect the private website route.HTTPS for the configured domain, preserving the Host header and the manager's configured public origin.
- Connect the raw game route.Authenticated outbound tunnel to a public relay. Forward the external TCP game port to home port 31876.
- Check the actual route before cutover.Cold place transfer, avatars, respawn, gear, multiple players, reconnects and shutdown. DNS or an open socket alone is insufficient.
Vita and internet imports
Add an unchanged .rbxl/.rbxlx from Places. Existing Vita discovery/upload and approved internet downloads remain handled by the hoster. Vita-library pulls need the authenticated loopback bridge on 31879. This manager does not auto-connect to a Vita device.
Host settings
Saved on the home host. Applying changes restarts the hosting service.
Original content stays intact
No conversions, script removal, per-place patches, avatar replacements or controller changes are exposed here. Arbitrary shell commands, player kicks and live avatar telemetry are not supported by this engine interface.
Recovery & diagnostics
Keep originals, saves and inactivity history together.
Consistent local recovery copy
Pause hosting first. The manager copies the place cache, saves, inactivity dates and settings into an archive, then reads every entry back and compares SHA256. Source files are not replaced or removed. Archives are stored under the manager state directory.
Restoration is performed offline after checking the manifest and making a safety copy. No live overwrite or unverified “restore succeeded” button is provided.