Dominion Strategy Forum

Please login or register.

Login with username, password and session length
Pages: [1]

Author Topic: Card text versus card behavior mismatches in Hearthstone, and Joust Giants  (Read 2060 times)

0 Members and 1 Guest are viewing this topic.

popsofctown

  • Adventurer
  • ******
  • Offline Offline
  • Posts: 5477
  • Respect: +2860
    • View Profile
+1

I complain a lot about when card text doesn't match behavior, because I really hate it.  Leeroy + Knife Juggler, Warsong + Bloodsail Raider, and Divine Favor+Fatigue don't do what their text says they should do.  Neither does Wild Growth or Mindgames technically in that they have unwritten rules for corner cases, which I feel should at least be noted somewhere in game.

Their lazy, sloppy determinations that whatever the code they wrote is doing is what the card "really" says might make the new expansion a little less fun due to the new Joust mechanic.  The Giants (and their cousins, the mourners like Volcanic Drake) all have variable cost abilities that don't specify when they function, and therefore should function at all times.  They all say "This costs X less for whyever".  But it was easier to code "While this is in your hand, this costs X less for whyever".  It's a really great example of why a good starting point is to implement the cards to do what they say.  If instead of narcisstically insisting that the card is somehow correct as is the development team faced up to a need to correct the text to match the code, they would raise a question of "Why do we need the "while this is in your hand" restriction? Is the card better designed with that restriction?", and design and R&D would actually have to think about it, and ArenaWarriorsMatter kinda demonstrates that they prefer to avoid striving for good design or, moreover, thinking, altogether. 
OTOH, if the code matched the original text in the first place, these new Joust cards would have a more fun feel to them.  As it stands, the best Jouster is a Giant, one that you usually cast for 0 mana.  The second best Jouster is also a Giant, one that you usually cast for about 4 mana. 

ALL the runners up after that group require you to have lots of mana crystals when you slam them on the table, which is supposed to add the coherency and insular feel to the mechanic.  You play some ramp, you play some jousters, you play some fatties.  That pattern creates a new subtype of decks that feel different to play, and fun to play because their new.  They are fun to play against because they have new characteristics that can be addressed for specific weaknesses: if you don't like losing to Joust decks, you run Faerie Dragon to punish the lack of cheap minions and go aggro, voila.  That being just one example.

It seems likely that this vision will just get betrayed in favor of exploitation of the incorrect implementation of the Giants, and Jousting will just become a Handlock accessory if we actually get any real viable Jousters.  Handlock cuts a couple cheap dudes from their builds, throws the jousters in, calls it a day.  Every other new deck designer then decides: should I make this a joust deck? Hm, I need to at least tie the other decks that contain joust, therefore this would need to be a Giants deck.  Can I make this a Giants deck?

Giants is already an insular, cohesive deck, so adding a little smidge of value to it is not as exciting as adding a different build-around-me mechanic would have been.  There's no Faerie Dragon anymore, Giants are a more dominating and dramatic feature than joust, so the answers are just whatever the answers to a Giants deck were in the first place, things like Equality, BGH, Shadow Word Death, and tauntskipping damage that counters Molten Giant, generally.  This all arises because drawback written on the text of Joust is just overwritten by "lol ignore that drawback" on the software of Giants. 

Just a rant.  It seems kinda like a lose lose.  Maybe joust is never competitively costed enough to see play in any way, so that's a lose.  It becomes a Handlock accessory or creates new class Giant decks that feel like Handlock and add no archetype variety (while buffing an existing archetype, making it more likely that a finite number of archetypes are major players).  Or they actually fix the bug, but leave Divine Favor, Knife Juggler, and Bloodsail Raider with incorrect behavior so I get extra relative deprivation whenever I feel upset about those bugs (mostly Bloodsail Raider, if you're wondering, since it is more fair about how it circumvents the restriction than other cards that are permitted to circumvent).
« Last Edit: August 13, 2015, 12:17:54 pm by popsofctown »
Logged

popsofctown

  • Adventurer
  • ******
  • Offline Offline
  • Posts: 5477
  • Respect: +2860
    • View Profile
0

I should admit it's possible that other factors become more important than the software loophole so Giants merely randomly block Jousts instead of taking them over.  For instance, all the good jousters or joust strategies being in a class that struggles to use Giants as effectively as Warlock, or some unexpected double BGH popularity during TGT meta.  I'm still worried though.
Logged

Twistedarcher

  • Witch
  • *****
  • Offline Offline
  • Posts: 494
  • Respect: +177
    • View Profile
0

Can you provide an example of the Giant/Joust "bug"? I'm not sure what you're talking about.
Logged

popsofctown

  • Adventurer
  • ******
  • Offline Offline
  • Posts: 5477
  • Respect: +2860
    • View Profile
0

I'm at one life.  You have 40 life.  I Holy Wrath you for 20 damage and play the Molten Giant for 0.  I Holy Wrath you again and win.

It's a selectivity that the cost modifying ability on the Giant doesn't apply if it's not in your hand.  If text on cards in your deck was ignored consistently, Captain's Parrot would never make any friends. 

Unless code changes, Molten Giant will always use the value "20" for its cost in jousts. 
« Last Edit: August 13, 2015, 01:36:50 pm by popsofctown »
Logged

werothegreat

  • Adventurer
  • ******
  • Offline Offline
  • Posts: 8172
  • Shuffle iT Username: werothegreat
  • Let me tell you a secret...
  • Respect: +9630
    • View Profile
0

I'm at one life.  You have 40 life.  I Holy Wrath you for 20 damage and play the Molten Giant for 0.  I Holy Wrath you again and win.

It's a selectivity that the cost modifying ability on the Giant doesn't apply if it's not in your hand.  If text on cards in your deck was ignored consistently, Captain's Parrot would never make any friends. 

Unless code changes, Molten Giant will always use the value "20" for its cost in jousts.

I think this is a feature, not a bug.  This is the intended implementation of Molten Giant.  Would it be nice if it said "...while in your hand"?  Sure it would.  But I think Blizzard is going for succinctness over pedantry, which, to a Dominion enthusiast, is cringe-inducing, I'll grant you.
Logged
Contrary to popular belief, I do not run the wiki all on my own.  There are plenty of other people who are actively editing.  Go bother them!

Check out this fantasy epic adventure novel I wrote, the Broken Globe!  http://www.amazon.com/Broken-Globe-Tyr-Chronicles-Book-ebook/dp/B00LR1SZAS/

markusin

  • Cartographer
  • *****
  • Offline Offline
  • Posts: 3846
  • Shuffle iT Username: markusin
  • I also switched from Starcraft
  • Respect: +2437
    • View Profile
0

I'm at one life.  You have 40 life.  I Holy Wrath you for 20 damage and play the Molten Giant for 0.  I Holy Wrath you again and win.

It's a selectivity that the cost modifying ability on the Giant doesn't apply if it's not in your hand.  If text on cards in your deck was ignored consistently, Captain's Parrot would never make any friends. 

Unless code changes, Molten Giant will always use the value "20" for its cost in jousts.
Tribe tags don't count as card text though. You can't silence the beast tag for example.

If it said "Draw a card with Charge", then yeah we can say for sure that card text not applying for cards not in hand is inconsistent.

And I agree on the Jeeves/Divine Favor inaccuracy being lame.
Logged
Pages: [1]
 

Page created in 1.432 seconds with 23 queries.