> For the complete documentation index, see [llms.txt](https://bloodlust-ro.gitbook.io/bloodlust-ro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bloodlust-ro.gitbook.io/bloodlust-ro-docs/start-here/server-rules.md).

# Server Rules

Server Rules — current Bloodlust RO guide, reviewed 27 September 2026.

{% hint style="info" icon="shield" %}
These rules are here to keep **Bloodlust RO** fair, friendly, and enjoyable for everyone. Playing on the server means following the latest rules published here and any system-specific rules shown in game.
{% endhint %}

## ⚡ Rule Summary

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>🤝 Respect Players &#x26; Staff</strong></td><td>Keep communication respectful and avoid harassment, threats, impersonation, and disruptive behavior.</td></tr><tr><td><strong>🛡️ Play Fair</strong></td><td>Use only approved server systems. Do not exploit bugs, manipulate packets, or use unauthorized tools.</td></tr><tr><td><strong>🔐 Protect Your Account</strong></td><td>Keep credentials secure and never provide your password to anyone claiming to be staff.</td></tr><tr><td><strong>🏆 Compete Fairly</strong></td><td>Do not manipulate PvP, events, rankings, or other competitive systems.</td></tr></tbody></table>

## 🤝 General Conduct

* Respect other players and staff.
* Harassment, hate speech, threats, and disruptive behavior are not allowed.
* Do not impersonate staff members or other players.
* Keep public channels readable and avoid excessive spam.

## 🛡️ Fair Play

* Do not use unauthorized third-party tools, exploits, packet manipulation, or automation outside the server's approved systems.
* Do not abuse bugs or unintended mechanics for personal gain.
* Report serious exploits privately to staff instead of spreading them.

{% hint style="warning" icon="bug" %}
If you discover a serious exploit, **do not demonstrate or distribute it publicly**. Report it privately so staff can investigate it without creating further abuse.
{% endhint %}

## 🔐 Accounts & Trading

* Keep your account credentials secure.
* Staff will never ask for your password.
* Follow the server's official trading and RMT policies when exchanging items or services.

## ⚔️ PvP, Events & Competition

* Follow event-specific and PvP-specific rules announced by staff or shown by the event NPC/system.
* Win-trading, match manipulation, and intentional abuse of ranking systems are prohibited.

## 📜 Rule Updates

Rules may be expanded or clarified as server systems are finalized. Players are responsible for following the **latest published version** of the rules.

{% hint style="danger" icon="triangle-exclamation" %}
A mechanic being technically possible does not automatically make intentional exploitation acceptable. When in doubt about an unusual interaction, ask staff before repeatedly using it for an advantage.
{% endhint %}


---

# 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://bloodlust-ro.gitbook.io/bloodlust-ro-docs/start-here/server-rules.md?ask=<question>&goal=<user_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.