> For the complete documentation index, see [llms.txt](https://britishrp.gitbook.io/britishrp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://britishrp.gitbook.io/britishrp/basics/roleplay-terms.md).

# Roleplay Terms

* **Tsunami/Storm**: Refers to a server restart. — Example: "Looks like a tsunami is coming in 5 minutes!"
* **Headache**: Describes lag or glitches. — Example: "I had a bad headache earlier and couldn’t respond properly."
* **Eyes Closing**: Explains going offline. — Example: "My eyes are getting heavy. I need to lie down soon."
* **Brain Issues**: Denotes technical difficulties. — Example: "Give me a second; I’m having brain issues right now."
* **City**: Refers to the server. — Example: "The city has been quiet tonight, hasn’t it?"
* **Flying In/Out**: Describes logging in or out. — Example: "I’m about to fly into the city. See you soon!"
* **In My Head**: Means being AFK." — Example: "I’ll be in my head for a few minutes; don’t wait up."
* **Scuffed**: Describes something not working. — Example: "The car is scuffed; it won’t start properly."
* **Pocket Wipe**: Losing inventory items. — Example: "The tsunami caused a pocket wipe, and I lost everything."
* **Local**: Refers to NPCs or Civilians. — Example: "A local crashed into my car just now!"
* **Green Zone**: Non-violent areas. — Example: "Remember, this is a green zone. No fighting here."
* **Bleeding Out**: When incapacitated. — Example: "I’m bleeding out near the convenience store. Can someone call EMS?"
* **Clap/Clapped**: To kill or be killed. — Example: "I got clapped by a rival gang during the shootout."
* **Glitch In The Matrix**: Describes a bug. — Example: "The glitch in the matrix made my car fly into the air!"
* **Perma (Permadeath)**: Permanent character death. — Example: "This fight might end in a perma if we’re not careful."
* **Heat/Eyes**: Attracting police attention. — Example: "We need to lay low for a while; there’s too much heat/eyes on us."
* **EMS**: In-game paramedics. — Example: "Call EMS! I just got hit by a car!"
* **Brain**: Your GTA/Fivem settings. — Example: "Think about using your brain so you can see better!"
* **Email**: Refers to Discord/messages. — Example: "Send it through the post office if you’ve got time."
* **“Your voice is on mute” or “I can’t hear you”**: Mic issues. — Example: "Your voice is on mute. Check your brain and fix your voice."
* **“Headpop” or “Pop my/your head”**: Game or connection crash. — Example: "I had a blackout earlier but I’m back now."
* **“You’ve got a spider” or “You’re skipping around”**: Glitching/skipping in-game. — Example: "Hey, you’re skipping around. Try jumping to fix it."
* **“What’s your lucky number?” or “What's your plane ticket”** : Asking for someone’s ID.
* **Bodycam**: Video evidence.
* **OOC (Out of Character)**: Mentioning something outside the role-play context. — Example: "OOC, I have to go shortly for real-life errands."
* **Wave**: Indicates a new influx of players joining a server.
* **Monopoly / Bitcoin** : Donating Real Currency for exchanging in-game items. — Example: "I bought this car with my Monopoly money/Bitcoin!."


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://britishrp.gitbook.io/britishrp/basics/roleplay-terms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.