> For the complete documentation index, see [llms.txt](https://new-legion-rp-la.gitbook.io/newlegionrp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://new-legion-rp-la.gitbook.io/newlegionrp/general-rp/xvi.-erp-erotic-roleplay.md).

# XVI. ERP (Erotic Roleplay)

\
**I. Core Principles**

1. **Adherence to Terms of Service:**
   * All players must comply with **Rockstar Games' Terms of Service**, which explicitly prohibit ERP. Engaging in such activities can lead to penalties, including bans.
2. **Respect for Community Guidelines:**
   * Players should uphold the community standards that promote a safe and respectful gaming environment. This includes avoiding any form of roleplay that could be deemed inappropriate or offensive.
3. **Focus on Immersive Roleplay:**
   * Encourage roleplay that enhances the narrative and character development without resorting to explicit content. This fosters a more engaging and inclusive atmosphere for all players.

#### **II. Guidelines for Roleplay**

1. **No ERP Scenarios:**
   * Players are strictly prohibited from initiating or participating in any ERP scenarios. This includes any dialogue, actions, or situations that could be interpreted as erotic in nature.
2. **Alternative Roleplay Themes:**
   * Focus on alternative themes that can provide depth and excitement to the roleplay experience, such as:
   * **Adventure:** Engage in quests or missions that challenge characters.
   * **Conflict:** Explore rivalries or alliances that can lead to interesting story arcs.
   * **Mystery:** Create scenarios that involve investigation or problem-solving.
3. **Clear Communication:**
   * If a player feels uncomfortable with any roleplay scenario, they should communicate this clearly and respectfully. Open dialogue helps maintain a positive environment.

#### **III. Enforcement and Reporting**

1. **Warnings:**
   * Players who violate these rules may receive a warning from moderators or admins regarding their ERP behavior.
2. **Temporary Bans:**
   * Repeated violations or severe instances of ERP may result in temporary bans from the server.
3. **Permanent Bans:**
   * Persistent offenders who disrupt the roleplay experience through ERP may face permanent bans.
4. **Reporting Violations:**
   * If you witness any violations of these rules, report them to the appropriate staff member or administrator. Provide clear evidence and context to support your report.

#### **IV. Promoting Fair Play**

* Encourage a **collaborative and respectful environment**. Engage with other players in a way that enhances the roleplay experience for everyone involved. The goal is to create enjoyable and immersive scenarios that everyone can appreciate.

By adhering to these rules, players can ensure a more respectful and enjoyable roleplaying experience while complying with Rockstar Games' Terms of Service. If you have any further questions or need more details, feel free to ask! 😊\
\
Rockstar Games - Legal\
<https://www.rockstargames.com/legal>\
\
Creator Platform License Agreement\
<https://runtime.fivem.net/platform-license-agreement-12-sept-2023.pdf>


---

# 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://new-legion-rp-la.gitbook.io/newlegionrp/general-rp/xvi.-erp-erotic-roleplay.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.