Mercury Core provides a flexible client integration system designed to work with Roblox clients. Client integration involves serving loadscripts, corescripts, and handling client-facing API endpoints that the Roblox client expects.
How Client Integration Works
When a Roblox client connects to Mercury Core, it makes requests to various endpoints to:
- Download signed loadscripts (join, visit, studio, host)
- Fetch assets and privileged assets
- Report client presence and server status
- Retrieve character appearance data
- Access client configuration settings
All script requests are served as cryptographically signed Lua code using a private key stored in data/PrivateKey.pem. The corresponding public key must be patched into your client.
Privileged Assets
Privileged assets are any assets with IDs hardcoded into the client or depended on by scripts sent to the client. These include:
- Corescripts - Core game functionality scripts
- Loadscripts - Scripts for different game modes:
visit.lua - Visiting placesjoin.lua - Joining multiplayer gamesstudio.lua - Studio modehost.lua - Hosting game servers
- External libraries - Any third-party libraries your scripts depend on
Privileged assets must be placed in the data/server/assets/{id} directory following the specific folder structure detailed at tp-link-extender/2013. Asset Loading Priority
When a client requests an asset by ID, Mercury Core checks multiple sources in this order:
- Privileged assets -
data/server/assets/{id}
- User-uploaded assets -
data/assets/{id} (with visibility checks)
- Open Cloud API - Falls back to Roblox’s asset delivery API (cached in
data/assetcache/{id})
Privileged assets are served without URL substitution, while user assets have roblox.com/asset references automatically replaced with your domain.
Script Signing
The private key for corescript signing should be placed in data/PrivateKey.pem, with the corresponding public key patched into the client. Never share or commit your private key.
--rbxsig%{signature}%--rbxassetid%{assetId}%
{script content}
URL Rewriting
Different client versions access endpoints with varying URL patterns. Mercury Core uses Caddy to rewrite legacy endpoint URLs to their modern equivalents:
/Asset/Default.ashx → /asset/Game/Join.ashx → /game/join/Game/Visit.ashx → /game/visit/Game/Studio.ashx → /game/studio
See the Site/Caddyfile for the complete list of rewrites.
Client Versions
Mercury Core is designed to be client-agnostic, but you may need to modify loadscripts and corescripts based on your target client version. Older clients often require significant modifications to work properly.
If you’re using original corescripts provided with the client instead of custom ones, expect to encounter issues that may require heavy modification or complete rewrites. This requires significant internal client knowledge and maintenance effort, with very sparse documentation available for beginners.