The boss frame shows the larger threat that an evolution route eventually has to answer.Steam
An update matters when it changes the job carrying the creature: food, damage, movement, sustain, biome adaptation, boss timing, or a challenge objective.
The short version
Do not restart the whole plan after every patch. Keep the route that was working and find the first pressure point affected by food, damage, movement, sustain, biome, boss, or challenge changes.
The challenge screen separates run goals from the creature choices made inside a fight.Steam
The launch-impact guide connects release changes to beginner routing, evolution builds, genetics, biomes, recovery, boss preparation, and challenges.
Follow the Change to One Route Job
Read the changed system. Do not assume every patch changes every build.
Match the note to a route job. Food, damage, movement, sustain, biome, boss, or challenge goal.
Keep one normal route. Find the first place where the stable plan now fails.
Update the decision, not the whole identity. If food changed, fix food first. If bosses changed, fix readiness first.
When a Patch Should Change Your Build
A patch should change the route when it affects the part that made the last run stable. If food access carried the build, food and healing changes come first. If movement solved bad biomes, terrain and hazard changes matter more than a small damage adjustment.
No update makes every mutation better or worse at once. Change the job that broke before chasing a brand-new creature identity.