Provenance, scope, and trust
About the Fantasy Online 2 Database
This player reference connects game facts to the mechanics that use them. It publishes facts only after the underlying data and relationships have been reviewed for meaning, safety, and player value.
Current coverage
Counts describe the reviewed data used by this site. A count can include clearly labeled historical entries when an older URL or useful identity remains worth preserving.
- Items
- 3,053
- Mobs
- 504
- NPCs
- 739
- Quests
- 568
- Player skills
- 281
- Enemy debuffs
- 54
- Zones
- 32
- Shops
- 85
- Recipes
- 699
- Achievements
- 408
Source and publication process
Pages use validated, read-only game data and do not query the live game database when a visitor opens a page. Every content family has explicit validation and tested relationships. New or unknown fields remain private until their meaning and safety have been reviewed.
In-game names, descriptions, stats, objectives, costs, and relationships remain distinguishable from values calculated by this site. Generated files are checked before a site build can complete.
Current, released, and historical labels
“Released” means content is connected to a reviewed player-facing source such as a current location, reachable NPC, shop, quest, recipe, or zone. “Historical” preserves a previously public identity or URL but does not claim that the entity is obtainable or present in the current released world.
Missing information is described as unknown or unavailable. It is not replaced with a guess. Older URLs are kept when safe, while private or developer-only content remains excluded.
How derived values are calculated
Derived values are produced from reviewed source fields and verified game behavior. Examples include reverse “used in” links, per-location drop contexts, party-adjusted probabilities, repeated-roll quantity distributions, crafting unit totals, item-set tier selection, and build attribute budgets.
The drop-rate guide, crafting guide, and build guide explain those rules in player-facing language. Mechanics review dates change only after a meaningful review; update dates can change when the validated data is refreshed.
Privacy and safety boundaries
The publication pipeline excludes accounts, characters, ownership, private instance provenance, player names, tokens, webhooks, mail, moderation, payment, and administrative data. The public site does not need game-database credentials and does not serialize those categories into generated assets.
Market fields on item pages are saved reference values, not live player listings. Build links contain only the equipment and planning state the visitor chooses to encode; individual shared states are not intended for search indexing.
The production site uses Google Analytics to understand aggregate visits, referral sources—including search engines and AI services—and feature use. Google may receive page URLs, approximate location, and browser or device information, and may store a first-party analytics identifier. Local and preview builds do not load the analytics tag, and no game account or private database data is sent with analytics.
Known limitations and interpretation
- Listed probabilities describe the game rules, not observed sample rates or a guarantee for future attempts.
- Maps cover released, reviewed locations; hidden-zone locations are excluded.
- Advice can become patch-sensitive even when an item, mob, or quest remains unchanged.
- A page may state that no reviewed source is known; that is a coverage statement, not proof that no source can ever exist.
Visit the Fantasy Online 2 game site to play, or return to the database home to search the current database.