Mutant Plants Base Defense Gem Spending Planner

Use this planner before the Shop, not after the wipe

The Gem Spending Planner is a decision template for Mutant Plants Base Defense. Rainbow Isle Base players redeem large gem packs — especially RELEASE1 (500) plus BUGFIX gem codes — and then spend reactively. This page forces a written split across Upgrade Zone caps and rolls before emotions join the party.

Currency definitions: Gems and Currency. Upgrade explanations: Base Upgrades. Parent: Tools Hub.

Caps reminder (write these down)

• Damage 20
• Range 20
• Attack Speed 25
• Diamond Drop 25
• Wins 25
• Luck 25
• Unit Slots 25

Step 1 — count liquid gems

Include unclaimed codes from Active Codes:

• RELEASE 100
• BUGFIX000 / BUGFIX999 / BUGFIX785 200 each
• RELEASE1 500

Redeem with How to Redeem Codes, then note the total.

Step 2 — name the failure mode

Pick one primary mode from How to Survive Waves:

1. Fast leaks → fund Range (and maybe Frozen holds later)
2. Soft DPS → fund Damage, then Attack Speed
3. Thin board → fund merges/rolls for duplicates, not slots yet (How to Merge Plants)
4. Roll starvation → fund Luck after combat floors exist
5. Density spikes → gems are secondary; hold grenades (Grenades)

If you cannot name the mode, default to Damage/Range.

Step 3 — apply a template

Template A: New / leaking early (default)

• 50% Damage
• 30% Range
• 20% rolls aimed at one merge line
• 0% Unit Slots unless literally unable to place a needed second plant

Template B: Mid, combat stable, soft finishes

• 30% Damage (toward cap)
• 40% Attack Speed
• 20% targeted rolls
• 10% Luck only if duplicates feel dead

Template C: Mid/late, hunting secrets

• 20% finish Damage/Range toward 20
• 30% Luck
• 40% rolls with a hard stop-loss (How to Get Secret Plants)
• 10% Diamond Drop / Wins for marathon fuel

Template D: Keeper-rich, slot-blocked

• 40% Unit Slots (only for proven keepers)
• 30% Attack Speed
• 30% rolls for duplicates of S/A lines (Plants Tier List)

Step 4 — fence fruits and grenades

Gems do not buy fruits or grenades in the planning sense — codes already delivered them. Fence those inventories:

• Fruits follow Fruits Priority
• Grenades follow How to Use Grenades

Do not “make up” for a bad gem plan by dumping Void fruits.

Step 5 — write the stop rules

Before you click Upgrade or Roll, write:

• Max gems to spend this session: ____
• Primary track: ____
• Secondary track: ____
• Roll stop-loss: ____
• Slots allowed? yes/no

When the stop-loss hits, leave the Shop. Play waves. Reassess.

Worked example (post-code night)

You redeem 1,200 gems worth of packs and still leak early:

• 600 → Damage
• 360 → Range
• 240 → rolls for one identical merge line
• Fruits parked
• Grenades parked
• Luck delayed

That plan beats 1,200 into random secrets with Damage rank 6.

After planning checklist

Run Loadout Checklist so backpack state matches the plan. If a patch landed, skim UPD-0.5 first.

Closing the planner loop

After you finish the spend script, write the leftover gem total and the next rank you refused to buy. That refusal is part of the plan. When the next code drops from Active Codes, you already know whether Damage, Range, or the roll budget gets first claim. If a teammate flexes Luck 25 while leaking, do not copy them — reopen this planner and trust the failure mode you wrote in Step 0.

Related pages

• Tools Hub
• Getting Started
• Codes Hub
• Items Hub
• Script Safety — gem generators are phishing

Fill the percentages while calm, spend while disciplined, and stop when the paper says stop. The planner’s only job is to keep RELEASE1 from funding the wrong problem on the loudest wave of the night.