Now I'm Mad

Mburn7

So I just lost a match in Hour of Devastation.  Normally, that's expected.  There are some filthy decks out there.

But this time, it wasn't my opponent's fault, it was a buggy card.

Blightcaster, a support that has worked properly for ALMOST 3 YEARS is suddenly not working.

It no longer triggers on Servos or Clues entering the battlefield.

This is a problem on a node where you cannot cast spells, and thus only include one removal spell in your deck.  I have been running this deck in HoD since it first came out with no issues, but now due to a bug that has come out of nowhere I not only have to completely re-do a deck, I am now out of the top 50 (possibly even top 100) in personal rewards and my coalition is possibly out of the top 2 for those rewards.  That is hundreds of Jewels and Crystals (Purple and Gold) lost because of a bug in a card that, I must say again, has been working properly for almost 3 years.

Its **** like this that makes you want to quit this game.

Boogeyman

I lost my first because I am a terrible player.  Not sure which is worse.  

Theros

This brings another issue concerning brackets and ranking. Lack of mention does not mean acceptance by the community. As it stands people are  ranked and rewarded differently depending on bracket size. The smaller the bracket, the more room for errors. In effect, I could get more reward at 40% less effort than someone who completed all nodes and lost some secondaries in larger brackets.

If I recall, the system was set by hybernum not to give too many rewards when ties arise. The real intent was not to make competition harder.

I understand the frustration of @mburn7. Bugs and freeze's are the reason why I don't play competitive games as often as I like to. Losing to players is fine. But losses caused by bugs are unacceptable.

I found out it helps to have a look at known bugs and draft your decks accordingly whenever you decide to play competively. 

Brigby

@Mburn7 Did you by any chance save screenshots of the Battle Log? It seems odd to me that a card's behavior would suddenly change when there hasn't been a new build introduced to cause a potential change.

Do you know what creatures or supports were on the board?

Laeuftbeidir

Brigby said:

@Mburn7 Did you by any chance save screenshots of the Battle Log? It seems odd to me that a card's behavior would suddenly change when there hasn't been a new build introduced to cause a potential change.

Do you know what creatures or supports were on the board?

You are aware that this bug has been reported and confirmed? It's not out of the blue.. It's just on position 739 of bugs that might or might not have been looked into. And one of the reasons why posting in the subforum or using supports is a gamble whether it's worth the effort or not.

ArielSira

Blightcaster has been bugged ever since the treasures change was made (that for a while also ruined Vraska's first ability). It should have been fixed months ago or at least when they fixed Vraska.

Brigby

Laeuftbeidir said:

Brigby said:

Mburn7 Did you by any chance save screenshots of the Battle Log? It seems odd to me that a card's behavior would suddenly change when there hasn't been a new build introduced to cause a potential change.

Do you know what creatures or supports were on the board?

You are aware that this bug has been reported and confirmed? It's not out of the blue.. It's just on position 739 of bugs that might or might not have been looked into. And one of the reasons why posting in the subforum or using supports is a gamble whether it's worth the effort or not.

I am aware that there is a known issue with Blightcaster and supports, however I wanted to gather the full details first, since the way Mburn7 described their specific occurrence made it seem like it might potentially be a different and new issue.

If it is in fact the same issue as the one discussed in Blightcaster not triggering off token supports, then the team is aware of it. In fact, I just took a look in the database, and it would appear that it has been confirmed as fixed, and is scheduled to be implemented in the 3.1 build.

Laeuftbeidir

Brigby said

If it is in fact the same issue as the one discussed in Blightcaster not triggering off token supports, then the team is aware of it.

Mburn7 said:

It no longer triggers on Servos or Clues entering the battlefield.

Yeah, I'm most likely just mad that this card hasn't been fixed in months ; maybe my tone was a bit off. I was also highly irritated about a question that suggested to me that you were  not aware about this bug (which is indeed quite realistic, since there are more than one or fifty open bug reports, but it takes seconds to find this one). After a while I was convinced nobody would care, since no updates are delivered.

You should really join our Slack: Every day I or someone else have to confirm for one or more players whether they have been facing known bugs or not, or what might be the reason why their decks won't work/locks the game / have been wrecked by buggy enemy interactions / why cards don't do what they're saying they do.

So, I have finished ranting, sorry if I stepped on your feet

madwren

That sucks.  It's very hard to keep track of all the bugs.  I highly recommend running any potential event decks through the gauntlet of TotP/AX/TG prior to each event to make sure everything's working as intended--because as we've all learned in the last few months, things spontaneously stop working with great regularity.

Aeroplane

I stopped using Blightcaster  when treasures stopped working with it. Just another random effect when updates happen. I've become less serious about this poorly coded game. Its still fun , but I won't spend 15 minutes making a deck(which I did enjoy)only to be shut out by S.Decree or other bugs. The lack of urgent/immediate updates befuddles me. 

bk1234

I think it’s super unfair to expect Brigby to know every single bug. He has 4 games and other job duties to keep track of. 

MtGPQ is not the center of the universe. 

Mburn7

@Brigby I sadly do not have any screenshots from the game, I closed out of the app very quickly after I lost and put it away for a while.

I did not know that the card was bugged, since I really only use it in this specific event on that specific node and not even all of the time there.

There are so many bugs being reported that I must have missed it in the forum.

Brigby said:

If it is in fact the same issue as the one discussed in Blightcaster not triggering off token supports, then the team is aware of it. In fact, I just took a look in the database, and it would appear that it has been confirmed as fixed, and is scheduled to be implemented in the 3.1 build.

At least its being fixed though!

And for an update:  After completing all of my other matches with a perfect score I am now ranked 52nd.  This means that once everyone else finishes up their nodes I'll be somewhere between 75 and 125th.

On the bright side, since the nodes are still bugged I was able to switch to a better walker and deck for that node.

What the bugs giveth the bugs taketh away

Froggy

I do not believe this is a bug. If I recall, this was part of the patch with support targeting and since then, I know blightcaster has not worked as it previously did - ignoring all servos - since the 2.9 update. I don't recall any specific thread or post where this may have been mentioned as a "fix", but I noticed it shortly after 2.9 was released and I'm surprised that this is coming up as a discussion (I didn't make much of it at the time). It is always a little disheartening to see players take a hit on game losses due to such things however.

madwren

Froggy said:

I do not believe this is a bug.

At the end of the thread Brigby linked, Tombstone specifically says the team is aware and it's been added to the bug list.

https://forums.d3go.com/discussion/comment/831258/#Comment_831258

Stormcrow

Boogeyman said:

I lost my first because I am a terrible player.  Not sure which is worse.  

I lost a match because I accidentally selected Gideon 1 and ran a deck that I put together before I even owned Blightcaster. (Is it racist to say that all Gideons look the same to me?  )

More on topic, while I'm glad to hear the Blightcaster will go back to working correctly, I'm a little dismayed that we're going to have to wait until (the as-yet not-even-whispered-about) build 3.1 to get the fix. The looooong turnaround time on fixing bugs is an issue, especially when every build seems to introduce new bugs and/or break formerly working cards. Even if we get fixes for that, and Ambuscade, and Etali, and whatever other cards got broken in recent updates, that just means we're going to be waiting until build 3.2 or later to get fixes in for whatever inevitable bugs arise in the 3.0 build's new card releases, when fixing the bugs in 3.0 is really what one would expect a 3.1 build to be for.

I don't know how much influence you have to affect the way the team handles bugs, Brigby, but if there's a way they squeeze in an extra, 100% pure bug-fixing patch so they can maybe get a little closer to "on track" in terms of the delay between "bugs introduced" and "bug fixed", that would do a LOT to calm the restless natives around here, I think.

Grixis197

I thought Blightcaster was nerfed cause of servos and clues seemed a bit OP to kill creatures, thought it was just supports you cast out yourself from now on I learnt this a few months ago now, maybe I was wrong.

Mburn7

Grixis197 said:

I thought Blightcaster was nerfed cause of servos and clues seemed a bit OP to kill creatures, thought it was just supports you cast out yourself from now on I learnt this a few months ago now, maybe I was wrong.

The reason it is assumed to be a bug is because no change was announced in any patch notes or posts.

If they announced the change in some way it would have been known (and complained about) as a nerf.

Now, Oktagon does have a habit of intentionally changing things without telling us, but that is usually how one can tell the difference.

Skiglass6

Mburn7 said:

Grixis197 said:

I thought Blightcaster was nerfed cause of servos and clues seemed a bit OP to kill creatures, thought it was just supports you cast out yourself from now on I learnt this a few months ago now, maybe I was wrong.

The reason it is assumed to be a bug is because no change was announced in any patch notes or posts.

If they announced the change in some way it would have been known (and complained about) as a nerf.

Now, Oktagon does have a habit of intentionally changing things without telling us, but that is usually how one can tell the difference.

It may be OP but fun. A good compromise would be to make it cast and a permanent debuff instead of until the end of turn. 

Mburn7

Update:  Lost another match due to a SWW error when I tried to start the fight.  Hit "retry" a couple times to no avail, then hit "cancel" and got returned to the event screen with -1 charge.

For those keeping score I now have 2 losses due to bugs, and 0 losses due to me.  Thats ~200 spots of final placement gone due to bugs. 

Kinesia

The thing is... I knew ages ago that this change had happened but I thought I knew BECAUSE it was in the 2.9 change notes and was very deliberate...

Maybe a weird memory thing and I'd just read about it in the bug thread instead...

ElfNeedsFood

"Bugs", "features", "expected effects", these terms are all very fungible here....