CookieRun: Crumble Builds for Red Pepper, Sugar Gnome, Blueberry Bird

Red Pepper, Sugar Gnome, and Blueberry Bird fill separate damage, front-line pressure, and sustain roles. Build Sugar Runes around those jobs instead of forcing the same offensive setup onto all three.

CookieRun: Crumble lets players build teams of up to 12 Cookies, but these three make more sense as a functional core than as interchangeable attackers. Red Pepper supplies damage and short-cooldown disruption, Sugar Gnome creates repeated Charge pressure from the front, and Blueberry Bird keeps the group alive long enough to reach another skill cycle. The cleanest early Arena split is simple: give Red Pepper the best offensive Sugar Runes, give Sugar Gnome enough durability to stay active, and build Blueberry Bird around cooldown and survival.

Blueberry Bird is the safest broad investment when a roster loses through attrition. Red Pepper becomes the priority when the team already survives but cannot close fights, while Sugar Gnome is a practical front-line addition when there is no stronger developed Charge unit. Do not sink heavy resources into all three at once if the real problem is basic structure, such as a front line collapsing before Blueberry Bird can cast.

Table of Contents (7)

Role Breakdown and Build Priorities

• Red Pepper Cookie: Fire Charge, Rarity U. Burst damage and disruption. Primary Sugar Rune focus: ATK and Skill AMP, the stat that boosts skill-based damage. Useful secondary stats: cooldown, critical rate, DMG Resist, HP, or DEF. Best early use: Arena pressure against fragile damage and support units.
• Sugar Gnome Cookie: Grass Charge, Rarity C. Front-line pressure. Primary Sugar Rune focus: ATK Amp and Skill Amp. Useful secondary stats: cooldown, HP, DEF, and damage reduction. Best early use: frequent Charge skill use and Revolution-style ATK teams.
• Blueberry Bird: Water Support, Rarity C. Healing and DEF support. Primary Sugar Rune focus: cooldown, then healing effectiveness where that stat is available. Useful secondary stats: HP, DEF, and damage reduction. Best early use: Arena stabilization and mission progression.

Red Pepper Cookie Build: Damage First, Then Cast Reliability

Red Pepper Cookie is a Fire Type Charge Cookie at Rarity U. Start with ATK because both major offensive effects scale from it. Add Skill AMP next, then cooldown if the team can keep Red Pepper alive. Critical rate is a secondary improvement rather than the first target, because extra crit potential does very little if Red Pepper never reaches a second skill cycle.

Jolly Candy has a 2.75-second cooldown and deals 119.9% to 154.9% of ATK across its upgrade levels. It can apply a 25% ATK Down effect for 2.5 seconds, with a 35% chance at earlier levels and a 45% chance at later levels. That is why Red Pepper works in early Arena teams: the skill adds direct damage while also cutting enemy output when the debuff sticks.

Burning Spirit adds more ATK scaling. Its kick deals 25.9% to 33.5% of ATK, while the burn ticks for 5.5% to 7.5% of ATK every 0.33 seconds over five seconds. Burning Spirit reaches range 2. That profile clearly favors an offensive build, but it still does not justify ignoring defenses when Arena opponents have fast back-line pressure or a disruptive opening.

• Primary Sugar Runes: ATK-focused pieces first, then Skill AMP.
• Secondary priorities: cooldown for more frequent Jolly Candy access, then critical rate if survival is already stable.
• Defensive correction: trade out a low-value offensive secondary stat for HP, DEF, or DMG Resist when Red Pepper is dying before the second rotation.
• Formation requirement: pair Red Pepper with a Charge or Tank unit that can absorb pressure so your main damage slot is not exposed immediately.

Red Pepper works best as the designated damage investment. If the roster already has a stronger carry, Red Pepper is more useful as secondary pressure than as a replacement. Spreading premium offensive resources across several fragile attackers usually leaves the team without enough sustain or front-line coverage to cash in on that damage.

Sugar Gnome Build: Repeated Charge Pressure

Sugar Gnome Cookie is a Grass Type Charge Cookie at Rarity C. Hammer of Revolution is the whole point of the build: its cooldown is 4.25 seconds through the first three upgrade levels, then drops to 3.75 seconds at the final three. Frequent activation matters more here than forcing a pure ATK setup onto a front-line Cookie that cannot survive the return damage.

Hammer of Revolution opens with a drop hit worth 18.1% to 23.3% of ATK in a 1.5 range, followed by an explosion worth 54.1% to 69.9% of ATK in a 2.5 range. That larger explosion area is what gives Sugar Gnome a pressure role instead of a finisher role. Sugar Gnome creates activity at the front; Red Pepper should still get the better burst investment.

• Aggressive build: use ATK Amp and Skill Amp Sugar Runes, then add cooldown to preserve frequent Hammer of Revolution casts.
• Front-line build: keep some offensive scaling, but move into HP, DEF, or damage reduction when Sugar Gnome drops before the next cast.
• Cooldown rule: take cooldown after the unit can reliably stay on the field. A shorter listed cooldown means nothing if the Charge slot disappears on contact.
• Team role: use Sugar Gnome as pressure, not as a substitute for a dedicated tank against teams with heavy opening burst.

Sugar Gnome can be deployed with Knight Cookie to gain Range Synergy. That is useful when Knight Cookie already fits the formation, but synergy should stay a bonus, not the whole roster plan. Do not cut a clearly stronger tank, controller, or damage dealer just to force a lower-value synergy line.

Blueberry Bird Build: Cooldown, Healing, and DEF Stability

Blueberry Bird is a C-rarity Water Support whose Wish Delivery heals low-HP allies and raises DEF on a 6.25-second cooldown. That gives you the build direction immediately: prioritize repeated casts and enough survivability to keep those casts happening. Cooldown is the leading Sugar Rune priority, with HP and DEF close behind when Blueberry Bird is getting knocked out too early.

Blueberry Bird is the safest investment of the trio because the role is clean. If your team survives the opening exchange but loses over time, Blueberry Bird patches the exact problem. If Blueberry Bird is being removed before the team stabilizes, add HP, DEF, or damage reduction before chasing more cooldown. A faster cycle only matters when the support lives long enough to use it.

• Primary Sugar Runes: cooldown first, then healing effectiveness if your rune pool supports it.
• Defensive secondaries: HP and DEF are worth more here than any offensive stat.
• Best partners: Red Pepper benefits from the extra time to deliver burst, while Sugar Gnome benefits from the healing and DEF support that let front-line pressure continue.
• Roster purpose: use Blueberry Bird when the team survives the first exchange but loses health over time, or when an early roster has no stronger healer.

Best Teams for the Three Cookies

• Arena control — Sugar Gnome, Red Pepper, Blueberry Bird: Sugar Gnome keeps forward pressure going, Red Pepper supplies damage and ATK Down access, and Blueberry Bird heals and raises DEF. The weakness is obvious: there is no dedicated hard-control specialist, so the trio can struggle if the front line folds immediately.
• Revolution-style ATK pressure — Sugar Gnome, Red Pepper, ATK or damage-amplifying support: Sugar Gnome creates repeated Charge activity while Red Pepper gets the main offensive investment. The tradeoff is lower sustain unless another slot covers healing or defensive support.
• DEF and healing sustain — Blueberry Bird, Red Pepper, Tank or defensive Charge: Blueberry Bird extends the team’s effective health while Red Pepper remains the primary damage source. The weakness is reduced closing power against very durable opponents.
• Budget progression — Sugar Gnome, Blueberry Bird, strongest available carry: low-rarity front-line pressure and sustain cover common early roster gaps while your best attacker handles damage. The ceiling is lower than a lineup built around stronger, more developed carries.

Red Pepper plus Blueberry Bird is the safest two-Cookie starting point when the roster already has a workable tank or Charge unit elsewhere. Add Sugar Gnome when the formation needs another aggressive front-line body and still has enough protection behind it. Drop Sugar Gnome for a stronger tank or control Cookie when Arena opponents punish a fragile front line before Blueberry Bird can stabilize it.

Rune and Investment Decision Rules

• Fix survival before damage. If a Cookie dies before casting, swap out an offensive secondary stat for HP, DEF, or damage reduction.
• Prioritize repeated skills for the support and Charge slots. Cooldown has the most structural value on Blueberry Bird and Sugar Gnome because their jobs depend on recurring casts.
• Concentrate premium offensive pieces. Red Pepper should get the strongest ATK and Skill AMP allocation when the team needs a damage carry.
• Do not duplicate a role without a reason. Multiple fragile attackers fight over offensive Sugar Runes, while several front-line damage units can leave Blueberry Bird exposed.
• Use synergies after the core roles are covered. A synergy bonus is useful when it fits naturally, but it should not replace a stronger Cookie that fills a missing tank, control, or sustain role.

Practical Build Order

Start with Blueberry Bird when the team loses gradual health wars or lacks reliable recovery. Move to Red Pepper when survivability is already adequate but Arena damage is not. Invest in Sugar Gnome when a Charge slot is needed for forward pressure, frequent Hammer of Revolution use, or Knight Cookie Range Synergy. That order changes only when Red Pepper is already heavily developed or Sugar Gnome is the only workable front-line Cookie on the roster.

The division of labor is straightforward: Red Pepper takes the damage resources, Sugar Gnome takes the pressure-and-survival balance, and Blueberry Bird takes cooldown and defensive stats. Build the missing role first, then use the rest of the roster to add a real tank, control effect, or damage amplifier instead of repeating a job this trio already covers.