> 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/download-guides.md).

# Download & Installation

Download & Installation — current Bloodlust RO guide, reviewed 27 September 2026.

1. Obtain the current **Bloodlust RO** client from the official Facebook/Discord announcement.
2. Extract the complete package into a clean folder.
3. Run the supplied patcher and let it finish.
4. Start through the supplied Bloodlust RO launcher. Keep all packaged executable, DLL and GRF files together.

**Do not rename internal client files to match the new branding.** The launcher/encryption component may rely on their exact packaged filenames.

## “GRF Encryption — File not found”

This means the launcher cannot locate its expected client executable. Check that you extracted the full package, that the shortcut starts in the client folder, and that security software has not quarantined a required file. Repatch or restore the current official package instead of renaming arbitrary EXEs.

No verified direct download URL is configured on this wiki yet. Get release links from the official channels below.

[Official Links](/bloodlust-ro-docs/start-here/official-links.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/start-here/download-guides.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.