Confirm branch and version first
Record your version, server and check date. Read release notes for that branch; a DevBlog describing ongoing work does not by itself establish public availability.
Read official notes in context
Check the title, date and branch mentioned. Separate released changes from tests and plans. When community guidance conflicts with the game, record the discrepancy instead of combining two versions into one.
Check what matters to this life
You do not need to retest the entire game. Prioritise mechanics involved in your current plan and items mentioned in the patch notes.
- Controls and interactions: feeding, drinking, carrying and species abilities.
- Diet, growth and status: reread character-panel descriptions.
- Mutations, Prime, Entomb or nesting if these are your goals.
- Terrain, travel routes and server rules after the update.
Run small tests and record conditions
Use a low-risk location, change one factor and record species, growth, condition and outcome. Avoid risking a valuable character on an unclear mechanic when a simpler observation or trial can answer the question.
Help EFG correct the right detail
When reporting a discrepancy, include the article link, section, version, server and observed evidence. Distinguish “I just saw this” from “this always happens”. Clear conditions are more useful than a general claim that the whole guide is wrong.
Sources and scope
Tactical decisions and checklists are EFG editorial suggestions. The references below provide mechanic guidance or update announcements; community sources may lag behind the game. Check the branch, version and server rules when information differs.