> For the complete documentation index, see [llms.txt](https://doj.secondliferp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doj.secondliferp.com/second-life-rp/gang-rules/final-note-rp-over-rule-play.md). # Final Note: RP Over Rule-play While all of the above rules are in place to maintain structure and fairness, we want to make one thing very clear... **Roleplay always comes first.** If a situation arises where exceptional, high-quality RP is taking place — and it slightly deviates from the set rules — it may be permitted if it serves the story and enhances the experience for everyone involved. However: * This is not a free pass. * It must be justified by proper roleplay — not personal gain, cliques, or OOC arrangements. Any exceptions to the rules will be carefully reviewed, and the Head of Gangs and Gang Staff will make the final decision. These are trusted individuals responsible for upholding the standards of serious RP while allowing creative freedom where earned. Always refer back to the main server rules, as they apply at all times. Gang rules are an extension of those — not a replacement. We expect gang leaders and members to set an example, push creative RP, and be part of what makes the city come alive. If you’re unsure about anything, please speak with gang staff before taking any action. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doj.secondliferp.com/second-life-rp/gang-rules/final-note-rp-over-rule-play.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.