Merge without breaking your next wave

The merge action is part of the game loop, but a useful merge is one you can explain and recover from.

Last checked August 18, 2026 · Official game linked

Safe merge order

Keep one option in reserve.

Check the current field and inventory before opening Merge.
Identify the matching plants and the plant you still need for defense.
Confirm the preview, then merge only the spare pair.
Place or test the result before the next wave becomes urgent.

What to record

Build your own version notes.

Write down the two inputs, the result, and what changed on the field. That creates a better guide for your server than copying a recipe from an older update.

Compare the upgrade route

Avoid this trap

Do not merge your only working plant.

Early runs are information gathering. If a merge leaves you with no reliable defense, the cost is bigger than the possible rarity jump.

Keep a deployed fallback.
Test one change at a time.
Do not infer a permanent recipe from a single visual result.

What should I merge first?

Start with matching plants you can replace. Keep at least one usable option for the next wave before confirming a merge.

Are there fixed merge recipes?

A complete recipe table was not verified for the current game version. Use the live merge menu and record the result from your own session.