Data & client reference · Client references
Spawn IDs
Spawn records connect creatures to observed maps and support monster and drop indexes.
Practical guide
3 steps for this topic- Record the creature ID, name, map, region, coordinates or roam area, time, event state, and observed respawn conditions.
- Match the ID with the monster record and keep variant creatures separate even when their sprites or names look similar.
- Add drop evidence to the exact spawn and avoid treating an unobserved map as proof that the creature never appears there.
Key details
Keep these with the route- Coverage
- Spawn lists are observational and can be incomplete on restricted or event-controlled maps.
- Variant risk
- The same art can represent creatures with different stats or loot.
Detailed reference
3 concrete notes- A spawn record needs creature ID and name, map ID and name, observed attack and defense elements, and an observed count. A zero count is not proof that the spawn cannot occur.
- Event schedules, boss triggers, kill-count doors, and server-side changes can make a static capture incomplete. Check several visits before publishing absence.
- Use the maintained monster and map records for player-facing hunting; retain numeric spawn IDs for research and cross-referencing only.