Version notes: locate the announcement that supports a claim

Editorial correction: October 6, 2026. Unverified species fields, spawn claims and blanket version labels have been withdrawn. Official store description · Developer update index. These links establish product and update context, not every mechanic or field in a save.

Start with the installed build

Use the developer update index to locate the release note for the change you are investigating. Record its title, publication date and the build it names. The previous site-wide v1.0 stable label has been removed.

Make a useful comparison

A product release date and an installed patch number are different facts. Check the game’s displayed version before using a mechanic or recipe from an older note.

Keep the limits explicit

A release note normally describes changes, not the entire current dataset. It cannot independently prove every species habitat, work skill or drop. Link the specific announcement when a claim depends on one.

A record you can check later

Write the platform and build, the task or encounter, the input you changed and what you observed. Include the relevant help text or announcement if it supports the result. Leave unobserved fields blank. This is an editorial method for keeping useful notes, not a claim of first-hand testing by Luminesca.

Open the party notebook to keep observations locally. It uses your entries and does not import our retired species dataset. Review the build before reusing an old note.

Sources and scope

Official store description · Developer update index. The store provides general product context and the update index leads to developer announcements. Neither is used here as proof of a species-specific recipe, spawn, drop or statistic.