1. Petrirex: a cooldown rollback is not a full rollback

VersionPer allied knockoutCooldown
1.1.030/60/90 Shield and Damage5.5 seconds entering 1.2.0
1.2.020/40/60 Shield only7 seconds
1.3.0No restoration of the Damage component announced5.5 seconds

Separate the guide's two assumptions. A plan that needs a 5.5-second cast can use that timing again; a plan that counts on Petrirex gaining Damage from allied knockouts still needs revision. Do not restore the old Damage calculation just because the cooldown matches it.

The official 1.2.0 update (opens an external site) supplies the shield-only change and slower cooldown. The official 1.3.0 notes (opens an external site) reverse the cooldown change. That is a narrower change than reverting the whole ability.

2. Find the exact dependency in your older guide

Search the guide for the monster or trinket it relies on, then check its stated version. These examples identify specific assumptions to replace; they do not rank the resulting teams.

Guide depends onConfirmed changeAction before following it
Opalion triggering two Rock allies1.3.0: two → one; cooldown 9 → 6 secondsCheck both the target count and timing. A faster cast does not preserve a two-ally sequence.
Steamscuttle casting every 2.5 seconds1.2.0: 2.5 → 3; 1.3.0: 3 → 3.5 secondsReplace the timing before comparing two cast sequences.
Zenith Stone amplifying percentage bonuses1.2.0 removes that interaction; 1.3.0 fixes remaining Cooldown Speed bonuses being boosted.Remove the percentage-bonus assumption. Read the installed item's description before rebuilding that chain.
Older developer image of the Batopedia with monster names, ability text and level controls
Developer-published Batopedia image showing names and ability panels. It is an older interface image, not evidence of the 1.3.0 values.

If you recognize the art but not a name in the notes, use the in-game Batopedia to match the name and ability, then return to the row that affects your guide. Keep a monster's level and Shiny state attached to any comparison.

3. Recheck purchase order and evolution conditions

  • Bug Catcher plus Bargain Bin: 1.3.0 fixes a Common Bug consuming both free buys. Bargain Bin is used first, leaving Bug Catcher's free buy for a rarer Bug. Do not budget a later purchase using the old double-consumption behavior.
  • Sproutquill and Fernfowl: 1.3.0 fixes evolution progress accumulating on the bench; progress now requires being on the team. If an older guide parks one on the bench while waiting for evolution, change that step.
  • Smuggler: 1.2.0 introduces cross-region shop access; 1.3.0 fixes incorrect tier mixes. An old screenshot of three Commons is not a reliable statement of its intended offering. The notes alone do not establish a best mixed-region team.

These checks concern the conditions for a step to work. If your guide uses none of these pieces, keep its unrelated instructions and check only the changes that affect it.

4. Match new keys to the intended action

In 1.3.0, R or D rerolls the shop; E sells the monster under the cursor; Space confirms the end-screen panel and H hides it. Before pressing E, check which monster your cursor is over. For Reroll, Confirm and Hide, hovering the control shows its key.

For older numerical assumptions, retain the 1.1.0 comparison as a historical checkpoint. For a stalled run or login, use the version-specific symptom guide; for continuation entry, use the Extended Mode steps.

These are full-release developer notes. The itch.io demo's current running build remains unverified here; do not transfer this checklist to it without identifying its version. No live team performance or recovery procedure was tested for this guide.