Latest revision |
Your text |
Line 1: |
Line 1: |
| <noinclude>__NOTOC__
| | __NOTOC__ |
| {{NavBar|5C61|[[Battle of Helm's Deep Index]]|[[Siege Engine (5U60)|Siege Engine (5U60)]]|[[Uruk Sapper (5C62)|Uruk Sapper (5C62)]]}}
| |
| {{CardTabs|Isengard}}
| |
|
| |
|
| [[{{ROOTPAGENAME}}]] is a {{C|Isengard}} [[Minion]] from the [[Battle of Helm's Deep]] set.
| | {{NavBar|Lotr05061|Battle of Helm's Deep Index|Siege Engine (5U60)|Uruk Sapper (5C62)}} |
| {{CardInfobox|5C61}}
| |
| {{QueryCardCategories|5C61}}</noinclude>
| |
| = 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.
| | {{LegacyCardInfoBox |
| | | TLHHImage=LOTR05061 |
| | | WikiImage=LOTR05061 |
| | | SetNum=05 |
| | | CardNum=061 |
| | | SetName=Battle of Helm's Deep |
| | | Side=Shadow |
| | | Culture=Isengard |
| | | Twilight=3 |
| | | FullCardType=Minion • Uruk-hai |
| | | Stat1Name=Strength |
| | | Stat1=8 |
| | | Stat2Name=Vitality |
| | | Stat2=2 |
| | | Stat3Name=Site Number |
| | | Stat3=5 |
| | | Stat4Name= |
| | | Stat4= |
| | | GameText=Damage +1. When you play this minion, you may place an [ISENGARD] token on a machine. |
| | | Lore=Trained Uruk-hai operated Saruman's siege engines at Helm's Deep. |
| | | Rarity=C |
| | | Notes= |
| | }} |
| | |
| | |
| | = General Strategy = |
| | |
| | In this section, describe: |
| | |
| | * Deck design strategy. |
| | * Gameplay considerations. |
|
| |
|
| = Strengths and Weaknesses = | | = Strengths and Weaknesses = |
| == 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... === |
| | |
| | * Add cards and explanations here. |
| | |
| | === Weak Versus... === |
| | |
| | * Add cards and explanations here. |
| | |
| | = Example Decks = |
| | |
| | * Decklists or links to decks that use this card. |
|
| |
|
| == Strong Versus... == | | = Rules and Clarifications = |
|
| |
|
| * 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. | | * Clarify existing rules if needed. |
| | * Link to rules discussions on TLHH. |
|
| |
|
| == Weak Versus... == | | = Extra Information = |
|
| |
|
| * [[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. | | * Add other information regarding printing, rarity, trivia, etc. |