> 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/criminal-rp-expectations.md). # Criminal RP Expectations ## Illegal Activity Must Be RP’d Properly Drugs, weapons, laundering, scams, they all need solid RP. * Think before you act * Treat it like an organised operation, not a repetitive money farm ## No Unrealistic or Reckless Behaviour Don’t shoot or rob people in front of police stations. Don’t kidnap someone at Legion during peak hours. Think like you’re trying to survive and build power, not rack up arrests. ## You Can’t Own the Whole Map No gang should dominate every route, turf, or plug. Let other groups breathe. Competition and collaboration are key parts of good RP. ## Gangs Must Have Structure Every gang must show leadership and organisation. * Roles like boss, underboss, and soldiers should be in play * Don’t assign ranks just for the title RP them out properly --- # 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/criminal-rp-expectations.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.