What is metagaming in FiveM, and how to stop it

The short version

Metagaming in FiveM means making your character act on something they never learned in the story, such as a name read off a nametag or a location spotted on another player's stream. No server stops it completely. A clear written rule helps, and so does a staff process that checks what the accused knew and where it could have come from.

In tabletop roleplay, Wikipedia's article on the metagame (opens in a new tab) describes metagaming as having a character act "on knowledge that the player has access to, but the character should not." Server rules also write it as meta gaming or meta-gaming. For metagaming in FiveM, each server's own rules decide where the line sits.

Common examples of metagaming on FiveM servers

Published roleplay server rules list cases like these:

• Names over heads. Calling someone by the name shown above them before your character ever heard it.
• Stream sniping. Watching another player's stream to find their character or where they are hiding.
• Discord and other voice apps. A friend says in a call that they are being robbed at the pier, and you drive there.
• Masked characters. Naming someone behind a mask from their voice alone, where the rules forbid it.
• Cross-character knowledge. Using what you learned while playing one of your other characters.
• Knowledge past death. Acting on what happened before your character died and respawned, against the New Life Rule.

What reaches the character through roleplay counts as in character: a radio call, dispatch, a witness, or a friend's description given in character.

Metagaming, powergaming and the other rule terms

The table gives the meanings found in published FiveM server rules; your own rules set the exact wording.

How to word a metagaming rule

A usable rule has a one-line definition, the sources your server counts as out of character, the edge cases settled, and the penalty. Staff point to its examples when a ruling is challenged.

The edges are where published rules disagree. One server counts what players learn in Discord chat as metagaming, another leaves the server's own Discord out of the rule, and a third says Discord and TeamSpeak do not come under metagaming. Some forbid naming a masked character from the voice alone; others let the character suspect but never be sure. Your rule has to settle each of these in writing.

Why metagaming is hard to prove

A clip shows what a character did, but not what the character knew. A typical report reads "he knew my name and we've never met", and the accused may answer that the two characters met before. Without a record, staff weigh two stories.

• The source is often outside the game. A Discord call or a stream in a second window leaves nothing on the server.
• A right guess is not proof. Players do drive to the obvious place.
• Characters meet off camera. They may really have met days earlier, in a scene nobody recorded.

How servers reduce metagaming in FiveM

Besides the rule, a server can combine several measures:

• In-game voice and a stream rule. Some servers forbid side calls during active roleplay, and a stream rule settles whether players may watch others on the server at the same time.
• Introduction or recognition scripts. A script can keep a name hidden until the two characters have introduced themselves, or give each character a memory of the people they meet.
• A staff process. Write down how long players have to report, whether the players involved must keep their own recording, and who may report. Published rules differ here: some give 24 hours, others 48 or 72, and some accept reports only from the players whose roleplay was affected.

Overhead names deserve their own decision. FiveM can draw gamer tags (opens in a new tab) above players, usually with the player's name, and the stock playernames resource in the server package does that. Turning that resource off, along with any other script that draws names, removes names over heads as a source of metagaming in FiveM. Staff still need to know who did what, so a server that hides names may still show the server ID and ask for it with every clip.

How to handle a metagaming report

These steps need no script:

1. Pin down the claim. Ask what the accused knew and why the character could not have known it.
2. Collect what both sides have. Clips with timestamps and server IDs, and the accused's own recording if your rule asks players to keep one.
3. Look for an in-character route. Had they met before? Could a radio call, dispatch or a friend in character have told them?
4. Let the accused answer before anything is decided.
5. Decide by the written rule and write down why. Keep the evidence together for an appeal.
6. Hand off any case you played in. Another staff member should judge it.

Where 5CODE Recognition fits

Recognition is 5CODE's character recognition and anti-metagaming script. A scan with F3 reads voice, clothing, face and tattoos into one percentage; at 80% by default the character knows that person. How character recognition works explains the scan, the ring, disguises and how long a memory lasts.

What matters for metagaming:

• Nobody knows anybody by default. A player sees a name the other person told them, or an automatic description. Character names appear only in the staff panel and in staff exports.
• Names over heads, only for those who know. Recognition can tell your nametag or chat script which players recognize someone, so only they see a name: the one that person gave them, or a line from their memory of them. It is off by default and has to be set up for your nametag or chat script; the docs page on nametags and chat (opens in a new tab) lists the scripts it works with and how.
• Masks count. A masked acquaintance is scanned like a stranger and saved as a separate memory.
• Memories run out. 5 days, 24 hours or 2 hours by how well you saw them; 30 days when a hidden camera recorded it.
• The New Life Rule, in part. Die without a revive and you forget the people who watched you go down. Keeping away from the scene stays your rule's job.
• Staff get a record. On aim, damage, kill, cuff, rob or search, the server logs what the attacker's character knew. The in-game admin panel has a live pair view and a timeline, plus lookup and Discord export.

It has limits. Recognition never blocks a shot, a robbery or a cuff. It cannot see a Discord call or a stream on a second screen, so your rule and your staff still decide.

Reading the record in Recognition

On a server that runs Recognition, part of step 3 has a record behind it: whether the accused's character remembered the accuser, and where that memory came from. A radio call or a dispatch message still has to be checked by hand.

Open the pair page of the admin panel and read the direction accused to accuser. Every proof stores two numbers: Then, what the character remembered, and Now, what a fresh look at that moment could have reached.

A memory badged DISGUISE was learned behind a mask, so the accused may legitimately recognize the masked person. The case to look for: calling that person by their real name while holding only a disguise memory. A low Now is not proof on its own, so open the proof in the timeline too, then export the pair to Discord as your paper trail. By default the panel refuses any pair that involves your own character. The staff guide in the Recognition docs (opens in a new tab) has the full workflow.

Where to go next

Write the rule first and post it where players read it before their first scene. Then decide how much of the evidence for a metagaming report you want the game itself to record. Recognition requirements and supported frameworks lists what a server needs to run Recognition, which supports QBCore, Qbox, ESX Legacy and Standalone.