Collecting GuideMagic: The GatheringMTG

Amass and Army Tokens: Zombie Horde Building in Ixalan Block

Amass takes a different approach to token strategy than almost anything else in Magic: instead of spreading value across many separate tokens, it concentrates everything into a single, growing Army token that gets bigger every time you amass again.

The mechanic was introduced in War of the Spark, but its roots as a horde-building tool trace back to the Ixalan block's Zombie tribal theme, where the black Zombie deck wanted exactly this kind of single-threat, ever-growing board presence.

This guide breaks down how Amass actually works under the rules, how the Army token creature type functions, and why building around one big token plays so differently from a traditional wide token strategy.

It is part of this pillar's broader look at Magic's token-generating mechanics, alongside the Populate, Fabricate, and Convoke breakdowns published elsewhere in this series.

How Amass Actually Works

When you amass a number, you put that many +1/+1 counters on an Army token you control. If you do not already control an Army, you instead create a 0/0 black Army token first and then put the counters on it.

This means every subsequent amass ability strengthens the same token rather than creating a new one, so a deck with several amass triggers ends up building one increasingly threatening creature turn after turn instead of a board full of separate small tokens.

What an Army Token Actually Is

Army is a black, token-only creature type introduced specifically for the Amass mechanic; there is no nontoken card that is natively an Army, so the classification exists purely to give these growing tokens a consistent creature type to reference.

Later Amass variants added new creature types on top of Army, layering a Zombie Army, Orc Army, or similar hybrid creature type depending on which cards generated the amass trigger in that particular deck.

Amass's Roots in Ixalan's Zombie Tribal Theme

Ixalan block leaned hard into tribal synergy across its four factions, and the black Zombies of the River Heralds' Secret tied directly into a horde-building, sacrifice-adjacent game plan that rewarded a large, expendable board of undead creatures.

Amass, introduced the following year in War of the Spark, formalized that horde-building instinct into a repeatable keyword action rather than a collection of individually worded token-making cards, giving future Zombie and horde strategies a cleaner mechanical backbone.

Single Big Threat vs. Many Small Tokens

A traditional go-wide token deck wants a battlefield full of separate small creatures so that removal spells and blockers can only ever answer one threat at a time. Amass takes the opposite approach, concentrating that same accumulated power into one large creature instead.

The tradeoff is real: a single Army token dies to one removal spell, wiping out everything you have invested, while a wide token board survives a single-target answer with the rest of the board intact.

Amass Orcs and Later Design Evolution

The Lord of the Rings: Tales of Middle-earth and its companion set The Hobbit introduced an Amass Orcs variant, where amassing gives the Army an Orc creature type in addition to its existing types, tying the mechanic into that set's own tribal theme.

This evolution shows how Amass has been reused as a flexible chassis across different sets and tribal themes rather than staying locked to its original Zombie-focused Ixalan-adjacent identity from War of the Spark.

Building Around Amass in Constructed Decks

An Amass deck wants a reliable stream of amass triggers, ideally starting early so the Army has time to grow into a real threat before opponents can find an answer for it. Protecting that single token becomes the deck's central defensive priority once it starts amassing.

Cards that grant hexproof, indestructible, or other protective effects to your Army specifically turn an otherwise fragile single-threat plan into a resilient win condition that is much harder for an opponent to simply remove and move on from.

Answering an Amass Threat From the Other Side of the Table

Because an Army token represents a single point of failure for its controller, opponents facing an Amass strategy should prioritize holding a removal spell in reserve rather than spending it on smaller threats earlier in the game.

Timing that removal for the moment right after a large amass trigger resolves, rather than before, denies the Amass player the maximum possible value from their most recent counters, since the Army cannot be rebuilt to the same size instantly.

Common Mistakes to Avoid

  • Amassing before checking whether you already control an Army token.
  • Building an Amass deck without any way to protect the single Army from removal.
  • Assuming Army is a creature type that exists on nontoken cards.
  • Forgetting a second Amass Orcs-style trigger adds a type rather than making a new token.

Frequently Asked Questions

What happens the first time you amass if you have no Army?

You create a 0/0 Army token first, then put the counters on it.

Does a second amass trigger create a second token?

No, it adds more counters to the Army token you already control.

Where did the Amass mechanic first appear?

Amass debuted in War of the Spark in 2019.

Is Army a creature type found on any nontoken cards?

No, Army exists only as a token creature type tied to Amass.

Grow Your Army Without Losing Track

A single growing threat is easy to lose track of on a crowded board, so keep the rest of your deck organized and protected with a set of Matte Card Sleeves before your next game.

Related Guides

Recommended Products