Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Browser-local worksheet · no game or save access

The Isle branch and migration report

Enter only details you are comfortable sharing. This creates a draft in this tab; nothing is uploaded or submitted.

Draft preview

The Isle branch and migration report — notes from my session
Guide: undefined
Platform: PC
Displayed version/build: unknown
Branch/world/session: unknown
Mode or context: unknown
Observed (not inferred): not entered
Already changed/tested: nothing entered
Next check: Record Legacy/Evrima/Test branch, build, species, group state, zone label, and exact status-panel text.

The values stay in this browser tab and are cleared on reload. This does not read or change saves, inspect your account, verify a diagnosis, post to a forum, or transmit data. Remove usernames, invite codes, server addresses, and other private information before sharing a report elsewhere.

Collect the smallest reproducible evidence set

A screenshot of a map alone may omit the branch and diet conditions that explain the question. Use the status screen and version label first; keep player-specific server names private if you plan to post publicly.

  1. Write down the branch (Evrima Public, Horde Test, or Legacy) and displayed version.
  2. Record species, group status, current migration zone label, and diet/nutrition status shown by the live interface.
  3. If the issue started after an update, compare the installed build with the corresponding official Steam announcement; do not substitute a Reddit summary.
  4. Change only one condition at a time (for example, zone position) and record the panel before/after; do not infer hidden mechanics from one observation.
  5. Use the local worksheet to assemble a text-only report. It does not attach screenshots, contact a server, or confirm a server-side bug.
  6. Ask other players in the external discussion area only after naming the branch and build; treat replies as unverified until confirmed in the game or official notes.
RecordWhy it mattersPrivacy boundary
Branch/buildSeparates public mechanics from test/historical contextDo not share account credentials
Species and group stateDevblog describes species diets and group-leader sharing designAvoid posting private server details
Zone/diet UI textShows what the game currently reportsDo not call it a bug before a matching-build check
One changed conditionMakes the observation easier to repeatNo save or account data is uploaded

References: The Isle developer: DevBlog #71 · The Isle official Steam announcements

Interpret replies conservatively

A player report may be useful as a hypothesis, but it cannot establish official server rules or current mechanics by itself. Prefer same-branch, same-build evidence and distinguish personal observations from patch documentation.

  1. Check whether the reply names the same branch and build.
  2. Reject advice that assumes a different species/diet without explaining the difference.
  3. Confirm any proposed action in the current interface before risking a creature.
  4. If a discrepancy remains, report the exact visible wording with the official patch link.

References: The Isle Steam Community Discussions

Before you play

  • The branch/build is explicit.
  • The migration panel and species are recorded.
  • I changed only one variable at a time.
  • I did not treat player comments as official confirmation.

Frequently asked questions

Can this report tool tell me where to migrate?

No. It organizes values typed by the player and has no live map or server data.

Should I rely on the newest Reddit map?

Not by itself. Match the branch/build, then verify zone labels and rules in your current game and official update notes.

Sources & revision notes

Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

  1. The Isle developer: DevBlog #71 (Official)

    Developer post checked November 7, 2026. It explains the intended migration redesign and Entomb Save boundaries, but those details are development notes; follow the live Evrima UI and current branch patch notes rather than assuming every announced change shipped unchanged.

  2. The Isle official Steam announcements (Official)

    Developer-published update archive; use the announcement matching the installed Evrima branch. The official Steam news page showed public-branch 0.21.772 in August 2026 when checked November 7, 2026; this may not be the current build later.

  3. The Isle Steam Community Discussions (Community)

    External player posts are unverified and may refer to Legacy, Evrima, or a test branch. Include branch/build, creature, group status and the in-game zone label.

What changed in this revision

November 7, 2026: first publication. Added a branch-specific evidence checklist, not a map route; no migration was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.