> 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/basics/weapon-secondary-and-emblem.md).
# Weapon, Secondary & Emblem
## **att / boss / ied**
For endgame setups, **8/1/0** (Boss Damage line on  Secondary) is the strongest configuration, assuming double prime lines. The Boss Damage line on your Secondary is preferred because the Weapon benefits from a higher potential tier for Attack % lines.
Whether your Secondary potential ends up being **12/12/30** or **12/40/9**, the difference is minimal — likely less than 0.2% Final Damage (FD). Feel free to go with whichever rolls first, as the difference is negligible.
When working on WSE for **9 usable lines**, both **7/2/0** and **9/0/0** setups are viable. The difference between them is only about 0.5 - 2% FD, so you can comfortably settle on whichever rolls first and revisit later when optimizing for damage per minute (DPM) or min-maxing your WSE setup.
If you’re using the  Gold Three Paths Emblem (Lv. 100), **2/0/1** is a perfectly acceptable setup **until you can obtain**  **Mitra’s Rage**.
## **Progression Considerations**
From a progression standpoint, any of the above setups will serve you well for a long time—especially if your Weapon and Secondary have double prime lines. Generally, **you won’t aim for 36% attack** on the weapon until everything else in your gear is DP-optimized, or unless you’re feeling particularly lucky with rerolls.
For  **Mitra’s Rage**, the Emblem should ideally be **3L Attack**. However, settling for an IED line is reasonable if you’re working on a tighter budget.
---
# 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 dynamically 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/basics/weapon-secondary-and-emblem.md?ask=&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 `build a script that syncs our docs to a CMS` 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.