The scanner looks for common FiveM event patterns in your source files (.lua, .js, .json, .cfg, .yaml, etc.). This includes TriggerServerEvent, TriggerClientEvent, RegisterNetEvent, AddEventHandler, on/onNet, emit/emitNet, export calls, RegisterCommand, state bag handlers, global/player state, UI callbacks, HTTP handlers and string-based event references.
Yes. Drop a .zip or .rar file and the tool will load the Unarchiver.js library automatically, extract the contents in your browser, and scan every supported file inside. Nothing is uploaded to any server — everything runs locally in your browser.
Does my code leave my computer?
No. The entire scan happens client-side using JavaScript in your browser. No file content is ever sent to a server. The only external resource loaded is the Unarchiver.js script (for archive extraction), which comes from a CDN.
How does the Event Parser work?
The Event Parser takes a single line such as TriggerServerEvent("esx_PawnShop:BuyItem",1,1,"weapon_combatpdw") and splits it into the event Name (the first quoted string) and the Payload (everything after the first argument). This is useful for quickly seeing what data a trigger sends.
What is the difference between Scanner and Shared Triggers?
The Scanner analyzes your own uploaded files. Shared Triggers is a curated, premium library of well-known FiveM event names from popular frameworks (ESX, QBCore, etc.) that you can reference without having to scan anything yourself. Access to Shared Triggers requires a passcode.
How do I export the results?
After a scan, use the TXT or JSON buttons in the results panel. The export respects your current filter, so you can narrow down to a specific trigger type or search term before exporting.
The scan is slow on large dumps — what can I do?
Use the Exclude folders setting to skip directories like node_modules, .git, or cache. You can also add common non-event names to the Ignore trigger names list to reduce noise in the results.