> 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/miscellaneous.md). # Miscellaneous ## Disciplinary Policy Disciplinary actions can take many forms and are not subject to a single standard approach. Disciplinary actions can be formal warnings, day or week bans or a permanent ban. It will all take place in our Discord ticket area. Disciplinary actions can result in a member being assigned the banned role, if applicable. If you are assigned this role, the permanent bans are appealable. You must create a ticket to advise staff of your ban appeal. You can create and launch your appeal as soon as you are ready, but please note that you will only receive one appeal. Once you have created a ban appeal, a staff member other than the staff member who issued the role/ban will review the appeal and make a final judgement. If the decision is made to keep your ban, you will either serve your ban and it will stay on your punishment history, or you will be permanently removed from Second Life RP. If your ban is overturned, you will be permitted to re-join our server. You can create a Discord ticket to discuss any ban you received for clarification. --- # 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/miscellaneous.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.