Task Bar Hero Wiki

A useful game database should answer more than “what is this item?” It should show how a record connects to the rest of the game: which hero can benefit from it, which stat it changes, where it can drop, what box contains it, and which stage is worth farming. This reference organizes those questions around permanent entity pages instead of temporary search results. Every catalog family has a dedicated directory, and every published entry has a clean URL that can be bookmarked, shared, and revisited after a release changes.

The coverage map is intentionally broad. It includes 5,944 item records, with 5,760 equippable gear entries inside that larger family, plus 6 heroes, 120 stages, 197 runes, 107 active skills, 107 passive skills, 61 monsters, and a focused set of status effects. Source material spans 16 game languages. The current interface begins with English while the underlying release model keeps locale, identity, and update metadata separate, so a translated title never has to break an established entity link.

Browsing is useful for discovery, but many play sessions begin with a decision. If you need one named item, open its gear page and review every published source. If you only know the desired level, rarity, or stat, narrow the directory first. If the question is “where should I spend my time?”, use the Drop Finder to approach the catalog through farming sources. The drop chance calculator then helps compare base, Hunter, Slayer, and combined scenarios without treating a displayed percentage as a guarantee.

Equipment planning often requires a second pass. The gear calculator supports direct comparison of published equipment facts, while the Cube calculator summarizes the values currently available to that tool. These utilities use the same catalog identities as the directories, so a calculation can lead back to the underlying record. That traceability matters: players should be able to inspect the source values, confirm the active release, and understand why two options produce different results.

Game information loses value when readers cannot tell when it was captured. The publication panel near the top of this page identifies the current data release, publication date, schema, and source version whenever the release service is available. Directory results and entity details carry the same release identity. This makes a discrepancy diagnosable: it can be tied to a particular import or patch instead of silently mixing values collected at different times.

Entity slugs are treated as permanent once published. A balance update can change a title, description, stat, effect, or drop relationship without forcing users and search engines onto a new URL. Invalid records are rejected before publication, missing detail pages return a real 404, and temporary upstream failures are not disguised as valid empty entries. Together, those rules make the site easier to cite in a guide, save in a browser, or use as the factual layer beneath future builds and tier lists.