Quick Answer
- Patch 1.08 added Baby Wyvern pets, pond construction, fish breeding, and a dedicated tool slot.
- Baby Wyverns are expected to grow into mount-registerable creatures in a future update, according to patch coverage.
- Ponds matter most if you are building out Howling Hill or Pailune Camp systems.
Patch 1.09 is the newest update, but Patch 1.08 is still worth revisiting because it added systems that keep growing in value: Baby Wyverns, ponds, tool slots, and more animal interactions.
Baby Wyvern priority
If you skipped the Baby Wyvern feature, put it back on your checklist. The important point is not just the pet itself; Pearl Abyss has framed Baby Wyverns as creatures that may grow into permanent mount options later. That makes early familiarity useful even if you are not chasing every pet.
Pond management
The pond system connects camp construction with fish management. Complete the required pond construction mission first, then use the pond as part of your camp routine rather than treating it as a one-time novelty.
Dedicated tool slot
The dedicated tool slot is a quiet win. Logging axe, shovel, scythe, pickaxe, drill/chainsaw, fan, and similar tools are easier to fold into routes when they do not compete with your core combat rhythm.
Suggested revisit order
- Check your active tool slot and assign the tool you use most.
- Finish pond construction if available.
- Register or track Baby Wyvern progress.
- Run one material route that uses tool slot plus pond/fish management.
Sources and update note
This draft is original editorial coverage based on the sources below. It should be reviewed before publishing if Pearl Abyss posts a hotfix or platform rollout update after May 29, 2026.
How to revisit an older patch feature
Older patch pages are useful as history, not as a guarantee that every detail remains current. Confirm the interaction in your own menu, start with one small pond or companion goal, and compare the page with the newest official update. Future-facing language should be treated as a watch item until a later note confirms it.
Patch advice stays useful when it separates a confirmed change from a player habit. Check the current game version and platform first, then test the feature in a normal activity rather than rebuilding an entire setup around one patch note. A small, repeatable test reveals whether the change matters to your own route.
Keep historical update pages dated. A feature may change again, arrive differently on another platform, or be described more broadly than it works in practice. The safest reading order is current official notes first, then this page for the practical way to try the system without wasting time.
When you find a difference, capture the useful context: platform, version, control method, area, and the action you tested. That turns a comment such as 鈥渋t does not work for me鈥?into information another player can verify. It also gives this page a clear path for correction when later patch notes change the original answer.
Before you move on
- Separate confirmed live features from future plans.
- Test one system before investing extra resources.
- Verify platform availability in the newest official notes.
- Keep the Last checked date visible on historical patch pages.
