Uruk Engineer (5C61): Difference between revisions
(Fixing the generated stinger using the culture icon rather than the full culture name + icon) |
(reducing extra space at the top of each article) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | <noinclude>__NOTOC__ | ||
{{NavBar|5C61|[[Battle of Helm's Deep Index]]|[[Siege Engine (5U60)|Siege Engine (5U60)]]|[[Uruk Sapper (5C62)|Uruk Sapper (5C62)]]}} | {{NavBar|5C61|[[Battle of Helm's Deep Index]]|[[Siege Engine (5U60)|Siege Engine (5U60)]]|[[Uruk Sapper (5C62)|Uruk Sapper (5C62)]]}} | ||
{{CardTabs|Isengard}} | {{CardTabs|Isengard}} | ||
[[{{ROOTPAGENAME}}]] is a {{C|Isengard}} [[Minion]] from the [[Battle of Helm's Deep]] set. | [[{{ROOTPAGENAME}}]] is a {{C|Isengard}} [[Minion]] from the [[Battle of Helm's Deep]] set. | ||
{{CardInfobox|5C61}} | {{CardInfobox|5C61}} | ||
{{QueryCardCategories|5C61}}</noinclude> | |||
{{QueryCardCategories|5C61}} | |||
= Strategy = | = Strategy = | ||
'''Uruk Engineer''' is a [[Glue|glue]] [[minion]] for [[Uruk Machines]] or occasionally [[Uruk Archery]]. It exists just to power up [[machine]] [[condition]]s like {{Card|Weapons of Isengard}} or {{Card|Devilry of Orthanc}}, either for their own effects or for later use by a minion like {{Card|Berserk Savage}} or {{Card|Berserk Slayer}}. Uruk Engineer adds tokens to machines rather than [[Reinforce|reinforcing]] them, so there's nothing stopping you from stacking tokens on cards that don't have any at all, or on a machine like {{Card|Siege Engine}} that can't use them itself. | |||
'' | |||
Uruk Engineer competes with its cheaper cousin, {{Card|Uruk Sapper}}. The Sapper has the same game text and [[vitality]], so it's a matter of whether it's worth a small price increase to have just enough [[strength]] to occasionally win skirmishes with support [[companion]]s, or whether its game text is so important that you'd like to have more than four minions that add tokens to machines. If you're not interested in is game text, there are better alternatives like {{Card|Uruk Warrior}}, {{Card|Uruk Lieutenant}}, or {{Card|Uruk Captain}}. Because it rarely does anything on its own but costs more than the Sapper, it's very easy to cut it from your deck so that it runs a bit more efficiently. | |||
'' | |||
Always remember to play it using {{Card|Siege Engine}} if you have that card in play, rather than playing it on its own. It's easy to forget. | |||
= Strengths and Weaknesses = | = Strengths and Weaknesses = | ||
== Synergizes With... == | == Synergizes With... == | ||
* ' | * [[Machine]]s. This card does one thing and that's stack [[culture tokens]] on machine [[condition]]s like {{Card|Weapons of Isengard}} or {{Card|Devilry of Orthanc}}. In turn, it works well with the minions that work well with those machines, including the berserker [[uruk-hai]] who consume [[culture tokens]], like {{Card|Berserk Savage}} and {{Card|Berserk Slayer}}, and [[uruk-hai]] [[archer]]s like {{Card|Ranged Commander}}, {{Card|Uruk Crossbow Troop}}, and {{Card|Uruk Crossbowman}}. | ||
== Strong Versus... == | == Strong Versus... == | ||
* ' | * Uruk Engineer mainly enables an [[machine]]-based strategy rather than working against the Free Peoples player directly. There's no common strategy that it is strong against on its own. | ||
== Weak Versus... == | == Weak Versus... == | ||
* | * [[Condition Removal|Condition removal]]. There are no practical ways to prevent it from placing [[culture token]]s except for making sure that there are no [[machine]] [[condition]]s for it to affect. | ||
[[ | |||
Latest revision as of 02:00, 1 December 2022
 Siege Engine (5U60)
|
 Back to Battle of Helm's Deep Index |
Uruk Sapper (5C62) 
|
Uruk Engineer (5C61) is a 
Isengard Minion from the Battle of Helm's Deep set.
| ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
Strategy[edit]
Uruk Engineer is a glue minion for Uruk Machines or occasionally Uruk Archery. It exists just to power up machine conditions like Weapons of Isengard (4R211)
or Devilry of Orthanc (5R49)
, either for their own effects or for later use by a minion like Berserk Savage (5R46)
or Berserk Slayer (5R47)
. Uruk Engineer adds tokens to machines rather than reinforcing them, so there's nothing stopping you from stacking tokens on cards that don't have any at all, or on a machine like Siege Engine (5U60)
that can't use them itself.
Uruk Engineer competes with its cheaper cousin, Uruk Sapper (5C62)
. The Sapper has the same game text and vitality, so it's a matter of whether it's worth a small price increase to have just enough strength to occasionally win skirmishes with support companions, or whether its game text is so important that you'd like to have more than four minions that add tokens to machines. If you're not interested in is game text, there are better alternatives like Uruk Warrior (1C156)
, Uruk Lieutenant (1R148)
, or Uruk Captain (2R46)
. Because it rarely does anything on its own but costs more than the Sapper, it's very easy to cut it from your deck so that it runs a bit more efficiently.
Always remember to play it using Siege Engine (5U60)
if you have that card in play, rather than playing it on its own. It's easy to forget.
Strengths and Weaknesses[edit]
Synergizes With...[edit]
- Machines. This card does one thing and that's stack culture tokens on machine conditions like Weapons of Isengard (4R211)
or Devilry of Orthanc (5R49)
. In turn, it works well with the minions that work well with those machines, including the berserker uruk-hai who consume culture tokens, like Berserk Savage (5R46)
and Berserk Slayer (5R47)
, and uruk-hai archers like Ranged Commander (4R169)
, Uruk Crossbow Troop (4U182)
, and Uruk Crossbowman (4C183)
.
Strong Versus...[edit]
- Uruk Engineer mainly enables an machine-based strategy rather than working against the Free Peoples player directly. There's no common strategy that it is strong against on its own.
Weak Versus...[edit]
- Condition removal. There are no practical ways to prevent it from placing culture tokens except for making sure that there are no machine conditions for it to affect.
