I’m specifically referring to the Wretched Tiller situation as of right now…but there’s a general question here. I get that the team does not want to rush a fix out to a card and nerf the card into uselessness. I respect that in fact.
But the game has had this broken wretched tiller combo in wild for several days now, to the point where wild is…well broken? How isn’t there a system in Hearthstone to temporarily ban decks and cards with a card in it for the sake of the health of the current meta?
Like, I’m not talking about even overpowered cards that have high win percentage like the knuckles before its nerf. I’m talking cards that have been absolutely toxic to the way the game is played. That way the game can still be played while the fix can be made in the background? We’ve seen similar systems in Tavern Brawls and Duels to ban a card…so why isn’t that in the Main Wild/Standard as well?
Code doesn’t just happen. Adding something like banning certain cards requires touching multiple places:
server APIs so the app can know which cards are banned
possibly card definitions so each card can say whether or not it’s banned
deck-building code so the cards don’t appear
UI so the cards can show in the lists but indicate which format(s) don’t allow them
deck management so if a deck is opened there’s a way to tell it is no longer valid
A way to control which format a deck is valid in. For example, if a card is banned in standard but not in will then there has to be checking done to let it be played in wild
Checking prior to a match to make sure you’re not queueing with a banned card because your deck has never been updated
All of this takes away from time which can be spent on other things: bug fixes, new cards, new mechanics, new game modes. Because code doesn’t just happen.
It’s much better to use the system already in place and fix something then it is to create a brand new system with ripples across the entire ecosystem.
a dev answered about these type of questions/demands about 2 weeks ago
" What are some common misconceptions about game design you see players complain about that are really a result of things being too complex to program/implement?
Why something doesn’t come fast enough is a common one. When you work on a huge team you need approvals from people who have no free time, get QA to do a pass when QA is fully booked, then get approval from third parties like Apple or Google. (Source)
We often know what we want to do but working on a multiplatform behemoth of a game like Hearthstone makes simple work take way more time than it would take a small dev team on one platform. (Source)
It can often make small indie projects appear more in-tune with things like game balance or bug fixes. Big teams on big games want that, too, it’s just more complicated than we’d like. (Source)"
Fair point.
I remember they banned Selfsharpening sword in Duels early after Duels release, but not wether it was via patch or hotfix. I think i was hotfix.
Regardless, if by the time they would hotfix, they would patch, sure, let them just patch it. But then the problem becomes they are too slow to react to broken things, even though they have already shown quickness (DH, Shaman Galakrond).
So I don’t really know what’s the holdup. Maybe they hope the meta adapts to stifle Tiller, but Wild shows clearly that the longer a combo exists, the more efficient it becomes.
ppl dont deserve a ban for running this combo…Malygos Druid and C’Thun rogue can also pull the otk as early as tiller(Turn 5 Cthun…turn 6 Malygos…turn 5 togwaggle druid(mark and roffle i think ? showcase it on youtube for togwaggle)…if you have issue with tiller you rly need to consider ALL other broken cards…like why are you raging on X but not on Y when they both cause the same issue ?..otk decks apart there are also other cards non-otk related that are a problem
I was wondering the same. Like just remove Tiller from the game until the patch is out.
We’re in 2021 and this isn’t possible?
Ginger I appreciate the comment on the complexities of this system and why it doesn’t work so easy. One thing impacts another. It is hard to see that as a player.
you do realize that’s not how code works right? sometimes yes you can transfer code over and it will still work but a vary large majority of the time you’ll have to write out a completely new script which takes time, then bug test the code which takes time, then go back and fix the bug which takes more time. adding in new mechanics to a game like this is complicated and a lot of work to fix an issue doesn’t happen incredibly often and is often fixed fairly quickly
