> 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/competitive/pvp-system.md).

# PvP System

PvP System — current Bloodlust RO guide, reviewed 27 September 2026.

Compete on enabled PvP and competitive maps. The ladder tracks **kills, deaths, personal kill streaks and guild ownage**. Use the PvP ladder interface to inspect current records and eligible archived rewards.

Only qualifying kills on enabled maps count. Self-character farming is rejected, and repeated sit-killing is checked by the anti-farming system. Do not arrange kills to inflate rankings. Weekly ranking processing runs at **Sunday 00:00 server time**.

Auto Hunt and Auto Support are unavailable in PvP/WoE/KOE and other competitive areas. Equipment restrictions, facet requirements and map-specific Soul Link reductions still apply.

## Prepare your build

* Compare defensive elements and tradeoffs rather than stacking only damage.
* Review your chosen facet and its matching Soul Link signature; several signatures have reduced boss/PvP effectiveness or separate cooldowns.
* Read exact consumable durations and restrictions before entering combat. Activity/Event items cannot be freely transferred to other players.
* Solo/PvP/WoE starter-package proposals are not a published gear guarantee in this guide.

[Facet and Soul Link effects](/bloodlust-ro-docs/custom-systems/legacy-progression/legacy-path.md) · [Consumables and equipment](/bloodlust-ro-docs/server-modifications/point-shop-equipment.md)


---

# 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/competitive/pvp-system.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.