imported>Warmachine University contributors: Imported from HTTrack HTML mirror

2022-02-03T22:56:02Z

Imported from HTTrack HTML mirror

New page

<html>
<table width="100%">
<tr>
<td> <b><strong class="selflink">Repurpose</strong> [ <a href="/index.php?title=Dread_Rots" title="Dread Rots">Dread Rot</a> ]</b> - When this weapon boxes a living enemy warrior model during this model's activation, <a class="mw-redirect" href="/index.php?title=RFP" title="RFP">RFP</a> that model and <a class="mw-redirect" href="/index.php?title=Add_to_play" title="Add to play">add to play</a> one Grunt to a friendly Dread Rot unit in this model's <b><span style="color:green">command</span></b> range. Place the Grunt in formation and in this model's <b><span style="color:green">command</span></b> range. The Grunt must forfeit its Combat Action the turn it is put into play.
</td>
<td> <a class="external text" href="../indexfa0a-2.html?title=Template:Repurpose&action=edit" rel="nofollow">Edit description</a>
</td></tr>
<tr>
<td> <b><a href="/index.php?title=Category:Death_Toll" title="Category:Death Toll">Death Toll</a> [ [[{{{1}}}]] ]</b> - When this weapon boxes a living enemy warrior model during this model's Combat Action, <a class="mw-redirect" href="/index.php?title=RFP" title="RFP">RFP</a> that model and <a class="mw-redirect" href="/index.php?title=Add_to_play" title="Add to play">add to play</a> one Grunt to a friendly {{{1}}} unit in this model's <b><span style="color:green">command</span></b> range. Place the Grunt in formation and in this model's <b><span style="color:green">command</span></b> range. The Grunt must forfeit its Combat Action the turn it is put into play.
</td>
<td> <a class="external text" href="../index7a7e.html?title=Template:Death_Toll&action=edit" rel="nofollow">Edit description</a>
</td></tr></table>
<p><br/>
</p>
<table cellpadding="5" class="" width='style="font-size:90%"'>
<tr valign="top">
<td align="center" style="border-right: 2px solid #20B2AA;" width="2.5%"><a class="image" href="File_RC_symbol.html"><img alt="RC symbol.png" height="60" src="/images/thumb/1/1c/RC_symbol.png/60px-RC_symbol.png" srcset="/images/thumb/1/1c/RC_symbol.png/90px-RC_symbol.png 1.5x, /images/thumb/1/1c/RC_symbol.png/120px-RC_symbol.png 2x" width="60"/></a>
</td>
<td style="border-top: 0.5px dashed #20B2AA; background: #EBEBF0;border-bottom-right-radius: 12px;border-top-right-radius: 12px; padding-right: 20px;" valign="top">
<p><b><span style="color:#20B2AA">Rules Clarification : <a href="/index.php?title=Category:Death_Toll" title="Category:Death Toll">Death Toll</a> </span></b>and/or<b> <strong class="selflink">Repurpose</strong>     (<a class="external text" href="../index3735.html?title=Template:RC_Death_Toll&action=edit" rel="nofollow">Edit</a>)</b><br/>
</p>
<ul><li> You can trigger the RFP even if there is no valid unit for you to add a Grunt to. (<b><a class="external text" href="https://privateerpressforums.com/showthread.php?276722-Does-Death-Toll-still-RFP-if-no-friendly-unit-exists&p=3862211&viewfull=1#post3862211" rel="nofollow">Infernal Ruling</a></b>)</li>
<li> At least one model from the unit must be in your CMD range, <i>as well as</i> the Grunt you spawn.</li>
<li> There is no limit to how many models you can create simultaneously. For instance, if you have Death Toll on an AOE weapon, then you can create one Grunt for each model killed in the AOE.</li>
<li> You don't need LOS to the model(s) you spawn.</li></ul>
<p><u>Return/Add to Play - Typical</u> (<a class="external text" href="../indexbde3.html?title=Template:RC_Return_to_Play&action=edit" rel="nofollow">Edit</a>)
</p>
<ul><li> If you're returning/adding multiple models simultaneously, they are placed sequentially. Often this will let you leapfrog the <i>"within 3" of [x]"</i> requirement.</li>
<li> If you're <b>adding</b> models to a unit, then typically there is no limit and you can go over the unit's starting size. However, some abilities do have a limit (such as <a class="mw-redirect" href="/index.php?title=Stir_the_Dead" title="Stir the Dead">Stir the Dead</a>)<br/>If you're <b>returning</b> models to a unit, then you're limited by how many there are in the "dead but not <a class="mw-redirect" href="/index.php?title=Removed_from_play" title="Removed from play">removed from play</a>" pile.<br/>    (See <b><a href="/index.php?title=LPG_-_Add%2C_Return%2C_and_Remove_From_Play" title="LPG - Add, Return, and Remove From Play">Add, Return, and Remove From Play</a></b> for further detail.)</li>
<li> If you're adding more models than you started with, then in a Tournament you must physically own the correct models - proxies are not allowed in tournaments. (<b><a class="external text" href="https://privateerpressforums.com/showthread.php?259503-Shanghai!&p=3648499&viewfull=1#post3648499" rel="nofollow">Locked thread</a></b>)</li></ul>
<p><u>Return/Add to Play - Other Units</u> (<a class="external text" href="../indexbde3.html?title=Template:RC_Return_to_Play&action=edit" rel="nofollow">Edit</a>)
</p>
<ul><li> <div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-hgfd">"Return to Play" and "Add to Play" are quite simple if you only return models to your own unit (like <a class="mw-redirect" href="/index.php?title=Blood-Bound" title="Blood-Bound">Blood-Bound</a>) or only return independent models (like <a class="mw-redirect" href="/index.php?title=Thagrosh1" title="Thagrosh1">Thagrosh1</a>'s feat). But if you're returning/adding models to <i>other</i> units, then click to read more.   <span style="vertical-align: super; font-size: smaller;">[<span class="mw-customtoggle-hgfd" style="color: #0645ad">Show/Hide</span>]</span><div class="mw-collapsible-content">
<ul><li> If you can return multiple troopers at once, they don't all have to be the same unit. Spread the love around.</li>
<li> Troopers must return to their original unit. Even if you have two units of the same type (such as two units of Convergence Eradicators) then you can't have 4 die from unit [A] and return them all to unit [B].</li>
<li> If your rule is something like <i>"return d3 models to units within CMD range"</i> (<a class="mw-redirect" href="/index.php?title=Old_Witch3" title="Old Witch3">Old Witch3</a>) then it is d3 models <i>total</i>, not d3 models to each and every unit.</li>
<li> If your rule is something like <i>"spend 1 soul to return 1 Grunt"</i> (<a href="/index.php?title=Enigma_Foundry" title="Enigma Foundry">Enigma Foundry</a>) then it doesn't matter where the souls came from originally. Think of them like currency, in this case.</li>
<li> You can Return models even after a unit is reduced to just Attachments (Weapon or Command)
<ul><li> If your Return ability lets you return a Leader or Officer model, then they will immediately become the unit commander and redefine the "in formation" bubble.</li>
<li> If your Return ability only allows Grunts, then the Grunt will <i>not</i> be field promoted when he arrives. <br/>This means that, in the unusual scenario where the Leader model has different wargear to the Grunts (such as Cygnar <a class="mw-redirect" href="/index.php?title=Stormguard" title="Stormguard">Stormguard</a>), then that wargear is effectively 'lost'.</li></ul></li></ul></div></div></li></ul>
</td></tr></table>



<div class="mw-category-generated" dir="ltr" lang="en"><div id="mw-pages">
<h2>Pages in category "Repurpose"</h2>
<p>This category contains only the following page.
</p><div class="mw-content-ltr" dir="ltr" lang="en"><h3>I</h3>
<ul><li><a href="/index.php?title=Isaiah%2C_Dread_Harvester" title="Isaiah, Dread Harvester">Isaiah, Dread Harvester</a></li></ul></div>
</div></div>
</html>

Category:Repurpose - Revision history

imported>Warmachine University contributors: Imported from HTTrack HTML mirror