Catalog values originate in the game project
Exported reference data
The interactive catalogs read a structured data file exported from the Unity project. It contains the fields needed by the public wiki, including enemy level and stat ranges, boss values and rewards, item types and effects, map relationships, character multipliers, achievements, release-state flags, and image references.
Using a project export reduces transcription mistakes and keeps related pages consistent. For example, an item link on a monster page and the same item's detail view refer to one exported identifier. A map's boss relationship uses the same identifiers as the boss archive.
Information that is not published
The export is intentionally limited to player-facing reference information. It does not publish player save data, purchase receipts, advertising identifiers, cloud credentials, private service keys, source code, or internal account records. Website analytics and game privacy practices are described separately in the privacy policy.
Some internal development records are excluded when they are templates, duplicates, unused assets, or explicitly hidden from the in-game collection. The public bestiary represents enemies assigned to active route zones. Implemented but locked expansion content may be included as a clearly marked preview.
Some player stats are derived from gameplay code
Current level-power calculation
HP, ATK, and DEF use the logarithmic level-power formula 2.35 × ln(1 + level / 100)%. It applies to the complete stat foundation, including equipment and permanent bonuses. Item percentage bonuses also apply to that complete total. AGI and LUC remain outside the level multiplier.
Catalog values versus final battle values
Enemy pages publish their configured values and resistance fields. A player's final battle result also depends on level power, equipment, character and achievement bonuses, crit/combo overflow, armor pierce, weaken, and mode-specific reward rules. The stat guide explains those calculations in player-facing terms.
Automated consistency checks plus human explanation
Checks before publication
After an export, the site should be checked for missing names, broken images, duplicate catalog records, invalid item links, bosses without usable map references, and maps that do not belong to a reachable route. HTML, JavaScript, sitemap URLs, canonical links, and important internal links are also validated before changes are published.
Numbers that appear surprising are compared with the active game configuration. This is particularly important for permanent bonuses, Hard Mode scaling, purchase values, drop chances, and newly connected maps because those systems can affect many pages at once.
Editorial content is written separately
Raw data can state that a monster has a certain attack value or where an item can drop. It cannot explain whether spending Adventure Points to farm that enemy is sensible for a particular run. Strategy sections are therefore written and reviewed as editorial guidance. They describe tradeoffs and link readers back to the current catalog.
Recommendations are not presented as guaranteed optimal solutions. Character choice, collected equipment, route access, remaining Adventure Points, and future balance changes can all alter the best decision.
Why a live game and a reference site can briefly differ
Build timing
A site export and a TestFlight, App Store, or Google Play build may be published at different times. The store build installed on a device is the final authority for what the player experiences.
Random outcomes
A drop chance describes an independent probability, not a guaranteed schedule. Receiving an item unusually early or late does not by itself prove that the published chance is wrong.
Display rounding
The game or website may abbreviate large values for readability. A shortened value such as 130K or 1M can hide smaller differences that still exist in the underlying number.
Send the page URL, the game version shown on the device, the relevant character or mode, and a screenshot to tonyzorz@naver.com. That information makes it possible to compare the correct build and data record.