> For the complete documentation index, see [llms.txt](https://www.hoyoung.directory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.hoyoung.directory/knowledge-base/bossing/oz-ring-guide.md).

# Oz Ring Guide

## Oz Rings

#### **Optimal Damage**

![:ror4:](https://cdn.discordapp.com/emojis/915039425191362641.webp?size=44)4+ for Burst \
![:wj4:](https://cdn.discordapp.com/emojis/915039451024089108.webp?size=44)4+ for Mini Burst 

#### **Acceptable**

> *better than 22\* stat ring if you don't have optimal rings*

![:ror4:](https://cdn.discordapp.com/emojis/915039425191362641.webp?size=44)3 - use in burst/party setting \
![:Cont:](https://cdn.discordapp.com/emojis/1272319739049279548.webp?size=44)3 - use if no ![:ror4:](https://cdn.discordapp.com/emojis/915039425191362641.webp?size=44) \
![:cont4:](https://cdn.discordapp.com/emojis/1178264097171714088.webp?size=44)4 - potentially better than ![:ror4:](https://cdn.discordapp.com/emojis/915039425191362641.webp?size=44)3 if solo and high uptime \
![:wj4:](https://cdn.discordapp.com/emojis/915039451024089108.webp?size=44)3 - if it's the only ring you have, ring swap between stat ring just for burst

{% hint style="info" %}
Other rings **may be usable in specific situations**. The best way to determine viability is to **perform a Battle Analysis**
{% endhint %}

## Krrr Ring

It's a powerful resource if you use it offensively to get a good set up/burst off. It can help push min clears to be a bit more reachable if you're not ![:gene:](https://cdn.discordapp.com/emojis/1275673675625922593.webp?size=44) liberated and doing challenging fights like black mage.


---

# 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://www.hoyoung.directory/knowledge-base/bossing/oz-ring-guide.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.