Install & Launch
Getting the External running alongside Roblox and confirming it has found the process.
- Windows 10 or Windows 11, 64-bit.
- The 64-bit Roblox client. Both the web build and the Microsoft Store (UWP) build are supported.
- Nothing to install by hand — the download is the program.
- 1
Run the External
It opens its own window. Roblox does not need to be running yet.
- 2
Join a game
The External watches for the Roblox process and resolves its base address once the game is live.
- 3
Wait for the base to resolve
Until get_base() returns something, no script can read anything. The overlay shows the state.
- 4
Run a script
Scripts execute in the External's own Luau VM, from its editor or from its script folder.
-- Confirm the External has found Roblox and resolved the tree.
print(get_base()) --> a large number, not 0
print(get_datamodel())
print(get_place_id(), get_game_id())Pointers do not survive a rejoin
Every address you resolved belongs to the session you resolved it in. After a rejoin, or a Roblox restart, resolve everything again from get_datamodel(). Caching an address across a rejoin is the single most common cause of a script reading garbage.
The External finds properties by byte offset. Roblox moves those offsets whenever it rebuilds, so the External ships an offset set matched to a Roblox version and updates when Roblox does.
If accessors start returning nonsense after a Roblox update, that is what happened — the build is behind. The Offset Accessors chapter links to the current set.