Run Lua in the FiveM client, dump any resource on the server, log and block events, and load premium menus — including VisionMenu, the in-game Lua overlay you see below.
Paste a script, hit Execute, and it runs inside the game process. By default
it targets isolated,
FiveM's own scratch resource, so nothing gameplay-related is touched.
.lua or .txt from disk into the editor and runs it.isolated. Switch to Auto for the safe allow-list, or pick any live resource.A live list of every resource on the server you are connected to, with a filter, a file tree and a built-in viewer. Dump one resource or all of them.
Watch the events a server fires at your client, and stop the ones you do not want.
Stays empty until you activate it. From there it records every event with its payload, so you can pick one out and replay it.
Anything on the block list never reaches your client. Add entries straight from the logger or by name.
One executable. It opens an authenticated session with our server and identifies your machine. No account, no password.
Our API returns the current build AES-256-GCM encrypted. The loader decrypts it in memory and maps it into the process.
The window opens on the Lua Executor tab, and VisionMenu is one launch away.
A Lua executor for the FiveM client with a resource dumper, an event logger and blocker, and premium Lua menus such as VisionMenu.
Yes. Layout, proportions, the sliding tab fill, the highlight bar and the whole menu tree are taken from the VisionMenu resource itself.
Inside the game process, against the native FiveM API. The default target is isolated, FiveM's own scratch resource, whose stop or start touches no gameplay code.
The resources the server has sent to your client. It lists them live, lets you filter and browse the file tree, and writes them to a dump folder on your machine.
No login, no password, no form. The loader identifies your machine when it opens a session with our backend.
The loader asks our API for the current build on every launch. If a newer one exists, that is what streams in.
Only the loader itself, plus whatever you deliberately dump or save. The build arrives encrypted and is decrypted in memory.