What to Build From Two Cloaks in TFT

Current Set: Set 17 — Space Gods
Patch: 17.9
Last Verified:
Guide Type: Evergreen component decision guide

This guide focuses on practical decisions from two Negatron Cloaks. Exact item effects and preferred holders can change between patches, so confirm current tooltips in game before relying on a specific interaction.

Quick Answer

Two Cloaks do not automatically mean you should stack all the magic resistance on one tank. Combine them when one upgraded frontline holder is taking most of the magic damage and extra resistance clearly extends the fight. Split them when two units need protection, your main tank already has enough magic resistance, or the board also needs health, armor, utility, or damage. The correct decision depends on the damage you are actually facing, not only the components on your bench.

The First Question: Is Magic Damage the Real Threat?

Magic resistance only solves part of a frontline problem. Before combining two Cloaks, scout the strongest opponents and identify whether your holder is dying to magic damage, physical damage, mixed burst, poor positioning, or insufficient health.

  • Heavy magic pressure: concentrating magic resistance may create a large improvement.
  • Mixed damage pressure: one Cloak may be more valuable in a mixed defensive item.
  • Coverage problem: two frontline units may each need one defensive item.

When Combining the Two Cloaks Makes Sense

1. You Have a Clear Main Tank

The safest reason to combine two Cloaks is an upgraded frontline unit that already absorbs most enemy abilities. The holder should be positioned to take meaningful magic damage and should remain on the board long enough to justify the commitment.

Use How to Choose an Item Holder in TFT before assuming the highest-cost tank is automatically the correct destination.

2. Magic Damage Is Breaking the Frontline

If enemy spells are the main reason your frontline disappears, concentrated magic resistance can solve the actual problem. In that case, immediate protection may be more valuable than preserving two flexible paths.

3. You Are Low HP

Low HP reduces the value of waiting for ideal partners. When a usable tank exists and the lobby is dealing heavy magic damage, a completed item now may protect more health than two unused components.

See When Should You Slam Items in TFT? for the broader timing framework.

4. Your Board Already Has Enough Damage

Combining becomes safer when your carry items and damage output are already acceptable. Extra frontline time can then create more total value than another offensive path.

When Splitting the Two Cloaks Is Better

1. Two Frontline Units Need Protection

One heavily protected tank does not always create the strongest board. If the second frontline unit collapses immediately, enemies may reach your backline from another angle. Splitting the Cloaks can improve total frontline coverage.

2. Your Main Tank Already Has Enough Magic Resistance

More magic resistance can have lower practical value when the holder already handles spell damage well but lacks health, armor, healing, or utility. Save one Cloak for a mixed defensive item that fills another need.

3. The Enemy Damage Is Mixed

Stacking magic resistance is risky when major threats also deal heavy physical damage. Split the Cloaks when the board needs a broader defensive profile rather than one narrow counter.

4. Your Final Tank Is Unclear

Two separate Cloaks preserve more options for temporary holders and future tanks. This is especially useful early when your final board and frontline pair are not decided.

Two-Cloak Decision Table

SituationRecommended decisionWhy
Upgraded main tank, heavy magic pressure, low HPUsually combine nowImmediate magic resistance has high survival value
Two frontline units both die quicklyConsider splittingDistributed protection may improve total fight time
Main tank already has high magic resistanceUsually splitAnother defensive layer may add more value
Enemy damage is heavily mixedDo not overstack magic resistanceThe defense may not match the full threat profile
No clear final tank, healthy boardWait briefly with a deadlineSeparate paths preserve flexibility
You are holding both through repeated lossesBuild something usableUnused components are costing HP

Check the Holder Before the Recipe

Before committing two Cloaks, ask:

  • Is the holder upgraded?
  • Will the unit absorb meaningful magic damage?
  • Does the holder already have enough magic resistance?
  • Would a second frontline unit gain more from one Cloak?
  • Does the board need health, armor, utility, or damage more than extra magic resistance?

For the broader frontline framework, read Tank Items Explained.

How Scouting Changes the Choice

Two Cloaks are more sensitive to lobby damage profiles than many other component pairs. Before committing both, scout the opponents you are most likely to face next and the boards that threaten your placement.

  • If most dangerous boards rely on spell damage, concentrated magic resistance becomes more attractive.
  • If threats are split between physical and magic damage, preserve a mixed defensive route.
  • If the main threat bypasses or overwhelms the tank for another reason, positioning or board changes may matter more than the item.

How Stage Changes the Choice

Stage 2

Preserve flexibility when your board is stable and lobby damage types are unclear. Combine when an upgraded early tank can use the item immediately and the slam protects a streak or prevents heavy losses.

Stage 3

Your main frontline units and common opponents should be becoming clearer. Holding both Cloaks without a plan becomes more expensive as player damage rises.

Stage 4 and Later

Scout before committing. If magic resistance clearly improves the next important fight, waiting for a perfect pairing is difficult to justify unless the board is already extremely stable.

Common Two-Cloak Mistakes

Automatically Stacking One Tank

The strongest individual tank does not always create the strongest board. Check whether spreading protection would keep enemies away from your backline longer.

Ignoring the Enemy Damage Type

Magic resistance is only efficient when it matches the damage you are taking. Scout before committing both Cloaks.

Ignoring Health and Armor

A tank with high magic resistance but too little health or armor can still fail quickly. More resistance is not always the missing layer.

Holding Both for a Perfect Tank

A future frontline unit does not recover the HP lost while the components were unused. Build earlier when a temporary holder can create value now.

A Five-Question Checklist

  1. Do I have a reliable main tank right now?
  2. Am I losing mainly to magic damage?
  3. Would combining protect meaningful HP this round?
  4. Would a second unit gain more from the other Cloak?
  5. Does the board need another defensive layer more than extra magic resistance?

If most answers support concentrated magic resistance and a reliable holder exists, combine. If the board needs coverage, mixed defenses, or protection across multiple units, split and wait with a deadline.

Browse the Component Guides archive for the complete double-component series.

For the full component overview and recipe framework, see TFT Item Components & Recipes Cheat Sheet.

Official Patch Reference

Patch 17.9 is the current Space Gods patch used for this guide’s freshness label. Riot’s Patch 17.9 notes do not list a broad standard-item recipe change, so the magic-resistance-versus-coverage framework remains applicable. For current frontline-holder and unit changes that can affect defensive item decisions, see TFT Patch 17.9 Item Decisions.

Final Takeaway

Two Cloaks give you a choice between one heavily magic-resistant frontline holder and two flexible defensive paths. Combine when a reliable tank is taking heavy magic damage and extra resistance clearly extends the fight. Split when two units need protection, the main tank already has enough magic resistance, or the board needs mixed defenses more than another narrow resistance layer. Do not wait forever, and do not combine only because the components match.