> For the complete documentation index, see [llms.txt](https://onebit-3.gitbook.io/onebit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onebit-3.gitbook.io/onebit/guidelines-and-rules/rules/power-gaming.md).

# Power Gaming

## Abusing in game mechanics to benefit your character or group is prohibited.

&#x20;Examples include but are not limited to:&#x20;

-Engaging a person in hostile RP while they are in a customization menu such as the clothing store menu. You can wait and get them once they come out the door.

-Accessing menu systems through walls that your character would not be able to access.&#x20;

-Falling from great heights or severely crashing a vehicle, and walking away as if your character was unharmed.&#x20;

-Forcing specific injuries OR death on other players without consent ("/me breaks John's leg" vs "/me is aiming her blows toward John's knee").


---

# 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://onebit-3.gitbook.io/onebit/guidelines-and-rules/rules/power-gaming.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.
