Bluetracker

Tracks Blizzard employees across various accounts.

Such a cool callback! But uuuuuh @MyntyPhresh @Celestalon Should it have the Mech tag or is the Old Curator wrong? #Hearthstone https://t.co/ItY86npVEq

Such a cool callback! But uuuuuh @MyntyPhresh @Celestalon Should it have the Mech tag or is the Old Curator wrong? #Hearthstone https://t.co/ItY86npVEq

machadogps

Posted 2 years, 10 months ago (Source)

Such a cool callback! But uuuuuh @MyntyPhresh @Celestalon Should it have the Mech tag or is the Old Curator wrong? #Hearthstone https://t.co/ItY86npVEq

MyntyPhresh

Posted 2 years, 10 months ago (Source)

@machadogps @Celestalon Old curator is wrong - it shouldve never been a Mech since Arcane Guardians/Golems arent mechs (see Arcsplitter in MotLK). Afaik we just never changed it since the card saw enough play where we didnt want to remove gameplay from it

DustyScales

Posted 2 years, 10 months ago (Source)

@MyntyPhresh @machadogps @Celestalon Aren't elves those that primarily use them? What about this, then? I know it's mostly for the balance of it but still https://t.co/7cYTTptbYr

MyntyPhresh

Posted 2 years, 10 months ago (Source)

@DustyScales @machadogps @Celestalon Yeah this one was odd. We needed a mech that could lore-wise be found in Zin Azshari pre-Naga curse but couldnt find anything perfect, so we had an arcane construct and tweaked it to have more mech-y features

opaldiia

Posted 2 years, 10 months ago (Source)

@MyntyPhresh @machadogps @Celestalon so then why not make the Purator a mech too, to keep it consistent?

MyntyPhresh

Posted 2 years, 10 months ago (Source)

@opaldiia @machadogps @Celestalon I think in this case we just leaned towards being more lore-accurate than consistent with lore-inaccurate precedent

Kaelthuzad

Posted 2 years, 10 months ago (Source)

@MyntyPhresh @machadogps @Celestalon I beg your pardon? https://t.co/6esJDs83zZ

Chadd Nervigg

Posted 2 years, 10 months ago (Source)

@Kaelthuzad @MyntyPhresh @machadogps WoW and Hearthstone differ on some rules. (Plants are another such example.)

<blockquote class="quoted">
 
</blockquote>
Such a cool callback!
But uuuuuh @MyntyPhresh @Celestalon 
Should it have the Mech tag or is the Old Curator wrong?

#Hearthstone https://t.co/ItY86npVEq (<a href="https://twitter.com/i/web/status/1624472239600009216">None</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@machadogps @Celestalon Old curator is wrong - it shouldve never been a Mech since Arcane Guardians/Golems arent mechs (see Arcsplitter in MotLK). Afaik we just never changed it since the card saw enough play where we didnt want to remove gameplay from it (<a href="https://twitter.com/i/web/status/1624473671975997441">MyntyPhresh</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@MyntyPhresh @machadogps @Celestalon Aren't elves those that primarily use them? What about this, then?
I know it's mostly for the balance of it but still https://t.co/7cYTTptbYr (<a href="https://twitter.com/i/web/status/1624476034555944960">None</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@DustyScales @machadogps @Celestalon Yeah this one was odd. We needed a mech that could lore-wise be found in Zin Azshari pre-Naga curse but couldnt find anything perfect, so we had an arcane construct and tweaked it to have more mech-y features (<a href="https://twitter.com/i/web/status/1624476888906481665">MyntyPhresh</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@MyntyPhresh @machadogps @Celestalon so then why not make the Purator a mech too, to keep it consistent? (<a href="https://twitter.com/i/web/status/1624474851787390976">None</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@opaldiia @machadogps @Celestalon I think in this case we just leaned towards being more lore-accurate than consistent with lore-inaccurate precedent (<a href="https://twitter.com/i/web/status/1624477171841667072">MyntyPhresh</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@MyntyPhresh @machadogps @Celestalon I beg your pardon? https://t.co/6esJDs83zZ (<a href="https://twitter.com/i/web/status/1625901085855559683">None</a>)
<hr/>

<blockquote class="quoted">
 
</blockquote>
@Kaelthuzad @MyntyPhresh @machadogps WoW and Hearthstone differ on some rules. (Plants are another such example.) (<a href="https://twitter.com/i/web/status/1625918339204939776">Chadd Nervigg</a>)
<hr/>

Tweet

Such a cool callback!
But uuuuuh @MyntyPhresh @Celestalon 
Should it have the Mech tag or is the Old Curator wrong?

#Hearthstone https://t.co/ItY86npVEq

@machadogps @Celestalon Old curator is wrong - it shouldve never been a Mech since Arcane Guardians/Golems arent mechs (see Arcsplitter in MotLK). Afaik we just never changed it since the card saw enough play where we didnt want to remove gameplay from it (<a href="https://twitter.com/i/web/status/1624473671975997441">Source</a>)

@MyntyPhresh @machadogps @Celestalon Aren't elves those that primarily use them? What about this, then?
I know it's mostly for the balance of it but still https://t.co/7cYTTptbYr

@DustyScales @machadogps @Celestalon Yeah this one was odd. We needed a mech that could lore-wise be found in Zin Azshari pre-Naga curse but couldnt find anything perfect, so we had an arcane construct and tweaked it to have more mech-y features (<a href="https://twitter.com/i/web/status/1624476888906481665">Source</a>)
 
 <hr/>

@MyntyPhresh @machadogps @Celestalon so then why not make the Purator a mech too, to keep it consistent?

@opaldiia @machadogps @Celestalon I think in this case we just leaned towards being more lore-accurate than consistent with lore-inaccurate precedent (<a href="https://twitter.com/i/web/status/1624477171841667072">Source</a>)
 
 <hr/>

@MyntyPhresh @machadogps @Celestalon I beg your pardon? https://t.co/6esJDs83zZ

@Kaelthuzad @MyntyPhresh @machadogps WoW and Hearthstone differ on some rules. (Plants are another such example.) (<a href="https://twitter.com/i/web/status/1625918339204939776">Source</a>)
 
 <hr/>