> For the complete documentation index, see [llms.txt](https://wiki.sidusheroes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.sidusheroes.com/nidum/collections/equipment/weapons/weapon-power.md).

# Weapon Power

The game features six Weapon Tiers, and each Tier has a specific Power value, which contributes to the team when equipped on a hero.

\* This base Weapon Power may differ from the actual Power added to the team. This happens because each race and selected attribute affects the final Power value. So, experiment with attributes and heroes you equip weapons on to maximize your team's strength.

\*\*Factors like Damage, Crit Chance, Resistances, and HP that boost the strength of the hero wielding the weapon influence Power. The better these stats, the higher your team's overall Power.

### Weapon Power Table

<figure><img src="/files/Dko6n5SWIflJ3QPAsOvS" alt=""><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.sidusheroes.com/nidum/collections/equipment/weapons/weapon-power.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
