Nobody tells you the city has a config file.
Most FiveM guides describe role-play in general and never mention the software you are actually running. This one does the opposite. A FiveM city is an FXServer install, a stack of resources, a pinned game build and a framework with numbers in its config, and almost every problem a new player hits (the empty car park, the missing vehicle, the inventory that says 30 kilograms, the paycheck that lands on a timer, the voice that carries eight metres and no further) is one of those numbers doing exactly what it was told. Below: how the platform is put together, how to read a city before you commit a character to it, the rule sheet every server enforces, how to write /me and /do so veterans want to play with you, how to get through a whitelist application, and the short list of fixes that resolves most client problems in under five minutes.
The client, the server binary and the six numbers that shape your session.
Six kinds of server, and the one that is not on this platform at all.
The largest of these, NoPixel among them, gate the application form behind a supporter tier because volume is unmanageable otherwise. Budget weeks, not days.
This is the correct place to make your beginner mistakes. Make them here, not in a whitelist interview.
Etiquette is the whole culture: lead car sets the pace, chase car never dive-bombs, and you pull off the road before you respawn.
Useful as a range, dangerous as a habit. Players who arrive in a role-play city straight from combat servers are the ones who get removed for shooting first.
Read the ruleset document end to end here. On themed servers the rules are the content, not the paperwork around it.
Worth knowing because it is constantly listed as a FiveM server and is not one. If typing is what you want, you need the other client.
Ten steps from a clean install to your first believable conversation.
1. Own and launch the base game once. A legitimate Grand Theft Auto V on Steam, the Rockstar Games Launcher or Epic, updated, launched once to the main menu so its files are current. FiveM reads that install; it does not replace it.
2. Keep a clean Legacy copy. Single-player script modifications, trainer DLLs and replaced vehicle files in the game directory are the single most common cause of a connect that dies on the loading screen. If you want a modded single-player setup, keep it in a separate copied folder.
3. Install the client and sign in. Create or link a Cfx.re account during setup. That account becomes one of your identifiers, and several whitelisted cities will not process an application without it.
4. Put the data folder somewhere with room. The client keeps per-build game data and every city's transferred assets. Twenty to forty gigabytes is a realistic allowance once you play on three or four servers.
5. Find the city, not the server list. The browser is noisy and half of it is boosted. Pick a community first (its Discord, its rules document, a few hours of someone streaming it), then use its join link or the Direct Connect tab with the address and port.
6. Join the Discord before the server. Rules, whitelist status, restart schedule, known bugs and the ticket system all live there. Read the rules channel completely. On a heavy city you will be quoted those rules in your first argument.
7. Let the first connect finish. Several minutes on a large city is normal. Alt-tab, do not close, do not repeatedly reconnect. A half-transferred asset set is how people end up with invisible cars.
8. Build a plain character. Height, build, face, a name you can say out loud in a scene and a look that matches the job you intend to do. Skip the elaborate backstory. Your character becomes interesting through what happens to them in the city, not through what happened before it.
9. Check the keybind page immediately. Escape, Settings, Keybinds, then the FiveM section, which holds the keys the server itself registered: inventory, interaction, emote menu, radio, voice range. Fix conflicts now rather than during a traffic stop.
10. Spend thirty minutes listening. Stand at a fuel station or a mechanic yard and watch how people greet, how they call radio, how long scenes run. Then start one small conversation. New players who observe first are absorbed into groups in a night; new players who arrive shouting take a week to recover.
Every menu you touch belongs to a stack with a name and a config.
The defaults most cities start from, and what they mean for your evening.
Ranges, radio submixes, and the microphone habits that get you invited back.
Ten rules, what each one actually means in play, and what breaking it costs.
| Rule | What it actually means | What it costs you |
|---|---|---|
| Value of life | Your character fears death. Two rifles pointed at you means you comply, and you do not reach for a pistol because you are quick. | The most common removal on heavy cities, and the hardest habit to unlearn if you came from combat servers. |
| Random deathmatch | Shooting a player with no build-up. A demand, a grievance or a conversation has to exist first. | Open cities usually run three strikes; whitelisted cities often remove on the first clear case. |
| Vehicle deathmatch | Using a car as a weapon without justification, including the classic drive-by-ramming of a fleeing suspect. | Treated as the same tier as random deathmatch nearly everywhere, with the added ban of vehicle privileges on some cities. |
| Metagaming | Acting on knowledge your character has no way of holding: a stream, a Discord voice channel, a friend's message. | Hard to prove and heavily punished when it is proved, because it poisons every scene you were in that night. |
| Powergaming | Writing outcomes for other people, or performing actions the world cannot support: lifting a car, shrugging off a broken arm. | Usually a warning plus a rewind of the scene, and a fast reputation as someone nobody wants to be robbed by. |
| New life rule | After a death your character does not remember the events that led to it and does not return to that location or that grievance. | Breaking it drags the whole previous scene back into play and normally voids whatever you recovered by doing it. |
| Combat logging | Disconnecting while a scene is live, including a convenient crash during a pursuit. | Counted as a death on most cities; repeated cases are treated as intentional and removed. |
| Green zones | Hospitals, police stations and spawn areas where hostile action is banned outright, in both directions. | People get removed for the counter-attack far more often than for the original provocation. Walk away and report it. |
| Police baiting | Manufacturing a pursuit for entertainment with no criminal purpose behind it, then repeating it nightly. | Burns the goodwill of the department you will need later, and most cities have an explicit rule against it. |
| Breaking character | Out-of-character remarks inside a live scene instead of a local out-of-character channel or a ticket afterwards. | Rarely a removal, always a cost: it ends the immersion for everyone present and marks you as someone to avoid pairing with. |
The two commands that separate a fluent player from a tourist.
Voice covers what your character says. It cannot cover what your character does with their hands, what a room smells like, or whether the blood on your shirt is visible from the doorway. That is what the two text commands are for, and most new players use them interchangeably, which is the single clearest tell that someone is new.
/me is your character performing an action
It is in your control, it is observable, and it is short. "/me wipes the counter down with a bar rag." "/me presses two fingers to the man's wrist, counting." "/me slides the envelope across the table, keeping one hand on it." Pair it with a matching emote from the emote menu when there is one, so the animation and the line agree.
/do is the world, or a question about it
It states a fact nobody owns, or asks another player for one. "/do The door is locked from the inside." "/do Would the smell of petrol be obvious in here?" "/do Is there anything visible in the back seat?" A /do that asks is an invitation. A /do that states is a set piece. Both are fine; a /do that decides something belonging to another player is not.
Never write another person's body
"/me knocks him out" is not yours to write. The version that works is "/me swings the bat toward his shoulder" followed by their response. You propose, they dispose. This one rule prevents most of the arguments that end up in tickets, and veterans notice immediately when you observe it.
Keep it to one action per line
Three chained actions in a single /me are impossible to respond to, because the other player cannot interrupt any of them. One action, wait, react to what comes back. The rhythm is a conversation, not a paragraph you deliver.
Six roles with an honest account of the hours each one demands.
Expect an academy block of a few hours plus a probation period of shifts before you patrol alone. Attendance matters more than aim.
Chronically understaffed at peak hours on nearly every city. A reliable medic gets remembered by name faster than anyone else.
The role that ages best. Long-running mechanics routinely outlast every criminal crew and half the police roster.
The role most damaged by players who treat it as pure combat. Cities watch it closely for exactly that reason.
Without civilians there is nobody to police and nobody to rob. Cities with strong civilian play feel alive; cities without it feel like a lobby.
Only exists on cities with a real judicial system. Check for an active court before you build a lawyer.
What reviewers are actually reading, and the six patterns that get rejected.
A whitelist application is not a creative writing test. It is a reviewer with two hundred forms open asking one question: will this person make scenes better or create tickets. Everything below serves that question.
Read the rules document first and answer in its vocabulary. If the city calls it value of life, do not call it fear RP. Using the server's own terms proves you read the document, which is exactly what the scenario questions are testing.
Write one page, not five. A reviewer reads the first paragraph properly and skims the rest. Put the hook, the flaw and the reason this character is in this city up front.
Give the character a weakness that creates scenes. A debt, a temper, a dependency, a sibling in the wrong crew. A flawless character generates nothing for anyone to play against, and reviewers have read a thousand of them.
Answer scenario questions with process, not outcome. "Someone points a gun at you in an alley" is not asking what you would do to win. It is asking whether you comply, whether you remember the details for a later report, and whether you know that losing is a legitimate result.
Prepare for a voice interview. Several cities run one, in character. Have your character's voice ready and consistent, and make sure your microphone is clean before you join the call, because audio quality is a stated rejection reason on the larger cities.
Expect the queue, and the cost of skipping it. On the biggest whitelisted cities, NoPixel included, the application route is effectively gated behind a supporter tier because the volume of forms is unmanageable otherwise. That is worth knowing before you plan your week around an acceptance that may not come.
The short list that resolves most problems, in the order to try it.
Eight habits that decide whether people seek you out in six months.
How the FiveM client and independently operated roleplay servers each answer a modified client, and how far a platform level ban reaches.