> 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/custom-systems/automation-and-daily/auto-support.md).

# Auto Support

Auto Support — current Bloodlust RO guide, reviewed 27 September 2026.

Auto Support follows a selected party member and uses learned support skills. Priest, Crusader, Bard and Dancer families are supported.

1. Join the same party as your chosen master.
2. Select the online party member in Auto Support and complete any required invitation/acceptance.
3. Configure the support skills and supplies you want to use.
4. Start on an eligible map. Keep the required resources available.

## Daily allowance

| Membership   | Auto Hunt | Auto Support |
| ------------ | --------- | ------------ |
| Regular      | 6 hours   | 6 hours      |
| Bronze VIP   | 8 hours   | 8 hours      |
| Silver VIP   | 10 hours  | 10 hours     |
| Platinum VIP | 12 hours  | 12 hours     |

**Reset: 00:00 server time, every day.** Each mode has its own account-wide allowance. Only time with that mode ON is consumed. Turning it OFF pauses consumption; changing characters does not create a fresh allowance.

Unused hours do not carry over. VIP changes the daily limit; it does not refill time already used, and the VIP bonus is not added repeatedly at reset. For example, Bronze with 3 hours used has 5 hours left; at midnight its new daily allowance is 8 hours.

Legacy stamina-refill items belong to an older timer system. They do not increase this daily allowance.

## Allowed maps

Use automation on eligible **fields and dungeons** only. Towns, PvP/WoE/KOE/Battleground areas, instances and other restricted maps are blocked. Maps containing configured **MVP or genuine mini-boss spawns** remain blocked even after the boss has been killed.

Regular farming monsters such as **Kasa, Salamander and Necromancer** are not treated as mini-bosses for this rule. A rejected start stays **OFF/red**. Auto Hunt and Auto Support cannot run together on the same character.

## ✨ Supported Class Behavior

### ⛪ Priest / High Priest

Can heal itself and party members, resurrect fallen members, and maintain learned support skills such as **Blessing, Increase AGI, Assumptio or Kyrie Eleison, Impositio Manus, Angelus, Magnificat, and Gloria**.

### 🛡️ Crusader / Paladin

Can use **Devotion** on supported party members and maintain defensive skills such as **Reflect Shield, Auto Guard, and Endure**. Supported Royal Guard progression can also use **Prestige** when available.

### 🎵 Bard / Clown

* **Mode A:** A Poem of Bragi
* **Mode B:** The Apple of Idun

### 💃 Dancer / Gypsy

* **Mode A:** Service for You
* **Mode B:** Fortune's Kiss

Use **`@changesong`** to rotate the Bard/Dancer song mode.


---

# 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/custom-systems/automation-and-daily/auto-support.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.