FiveM Event Logger & Debugger Tool

Generate event listeners, validate naming conventions, check for security issues, and use ready-made event templates.

What this tool is for

Events are how the client and the server talk to each other in FiveM, and they are also the most common way a server gets robbed. A server event that trusts what the client sends can be called by anyone with an injector. This generator writes correct listeners for both sides and checks your event names against the naming and security rules.

How to use it

  1. Step 1:

    Enter the event name, ideally prefixed with your resource name so it cannot collide with another script.

  2. Step 2:

    Choose the side. A server event needs RegisterNetEvent, a purely local one does not.

  3. Step 3:

    Generate the code and read the security notes. They point at the values that must be checked on the server.

  4. Step 4:

    Copy the listener into your resource and replace the placeholder body with your own logic.

Frequently asked questions

What is the difference between RegisterNetEvent and AddEventHandler?

AddEventHandler registers a handler. RegisterNetEvent additionally allows the event to be triggered from the other side of the network. Without it a remote trigger is ignored, with it anyone on the network can call it, so it belongs only on events that really need it.

Why must I never trust the client?

Everything a client sends can be forged: the amount, the item, the price, the player id. Read the source with source on the server and look up the actual values in the database yourself. A server event that takes an amount from the client is an open till.

How should I name my events?

Always resource:action, for example agency-phone:sendMessage. Without the prefix two scripts can register the same name, and then the wrong handler runs. Colons are the convention, not underscores.

How do I find out which events my server fires?

A handler on the wildcard side plus a print into the console shows the traffic. For a targeted look add a log line at the start of the listener. In production remove them again, because every log line costs performance on a busy server.