Which bugs are the worst kind of bugs?

Pantagruel
Pantagruel Posts: 79 Match Maker
in MtGPQ General Discussion

Which type of bugs grind your gears the most?

Which bugs are the worst kind of bugs? 16 votes

Bugs that have been present since the game was launched
0%
Bugs that have only existed for a couple of years or so
0%
Brand new bugs introduced in a new update
12%
jtwoodnaabaldan 2 votes
Previously working code which became bugged in a new update
25%
madwrenTomBMburn7WulFgaR77 4 votes
Old bugs which had been fixed which were reintroduced in a new update
56%
DragonSorcererAvahadStormcrowBubbles_CSFindingHeart8Julie71McclaineKlepPantagruel 9 votes
Old bugs that transmuted into new bugs without intervening period of working properly
6%
Narcoticsagent 1 vote
Forum rule 13 mandated neutral bugs
0%

Comments

  • jtwood
    jtwood Posts: 1,285 Chairperson of the Boards
    Brand new bugs introduced in a new update

    Specifically, the kind of bugs that would have been very obvious with the smallest amount of QA, like playing the event or even just trying to use the card.

  • Julie71
    Julie71 MTGPQ Mod Posts: 707 Critical Contributor
    Old bugs which had been fixed which were reintroduced in a new update

    They all suck although I really am intrigued by the newest ones. In my head I say how did they do that one. Although trying to recreate them is a pain in the butt.

  • Mburn7
    Mburn7 Posts: 3,427 Chairperson of the Boards
    Previously working code which became bugged in a new update

    Hmm, would I rather be kicked in the face or the balls?

    I wish I could select multiples. Old bugs that were fixed that come back are awful, but at least we know how to avoid them I guess? Brand new bugs are spirit-crushing, but at least kind of understandable sometimes since QC is tough. Ancient bugs are whatever, they suck but everyone should know about them and how to play around them.


    But when something was working perfectly fine and then suddenly isn't for no reason, those bugs are the ones that really suck. Because there is often absolutely no reason anything should have changed with those cards or abilities, so there is absolutely no reason there should be a bug there. But there is!

  • Klep
    Klep Posts: 52 Match Maker
    Old bugs which had been fixed which were reintroduced in a new update

    Old bugs that had been fixed and are reintroduced are definitely the worst. When they fix a bug best practices involve creating tests to check whether that bug has truly been fixed, and then running those tests on every update before it gets pushed out. For old bugs to be reintroduced means those tests either don't exist or were poorly designed.

  • Bubbles_CS
    Bubbles_CS Posts: 332 Mover and Shaker
    Old bugs which had been fixed which were reintroduced in a new update

    It is demoralizing when an old bug resurfaces because it suggests that bugs are covered up, not fixed, and that as more cards and features are added not only can we expect new bugs but old ones, too. It also suggests that the developers don’t understand their own codebase (it could also be the result of an unstable codebase, but devs wrote that, too).

    Bugs are inevitable, but the level of game-, event- and card-breaking bugs should be taken seriously and addressed for the stability and longevity of this game. Many on these forums have shared that they want to play, enjoy and spend money on this game but the bugs not only make it unenjoyable and raise serious doubt about the longevity of this game, making it a poor investment. It’s a vicious cycle that the devs must end decisively if this game is to have a future.

    I was also hoping for more than a new set, one event, and the usual lot of planeswalkers and bugs out of “v4.0” but this feels more like “v3.10”. This is probably just semantics but usually a new version number comes with more. It makes me wonder if something fancier was cut, but I don’t expect that level of communication.

    I would love to see a roadmap for this game so we can understand what is coming in the longer term and to know what dev priorities are. I think that kind of communication would Help build some trust.

  • __Adam
    __Adam Posts: 111 Tile Toppler

    To be fair to QA, they could very well be citing these bugs and incompetent management ships it anyway.

    And yes, calling this 4.0 is just them trying to make it looks like this isn't a dead game walking.

  • Bubbles_CS
    Bubbles_CS Posts: 332 Mover and Shaker
    Old bugs which had been fixed which were reintroduced in a new update

    I think v4.0 is just sequentially after v3.9 and nothing more.

  • Machine
    Machine Posts: 857 Critical Contributor

    The bug that causes you to lose all the points AFTER winning a match, but when the ribbons are not awarded yet and the game locks up!

    How many times do we have to ask for a recovery system??

  • __Adam
    __Adam Posts: 111 Tile Toppler
    https://forums.d3go.com/discussion/comment/914620#Comment_914620

    It's actually 3.10. They aren't decimals, this is pure shennanigans on the dev's part to make development look more significant than it is.

  • __Adam
    __Adam Posts: 111 Tile Toppler
    https://forums.d3go.com/discussion/comment/914650#Comment_914650

    The obvious solution is something that's been around for decades: transactions. There are thousands of software packages to do this.

  • Pantagruel
    Pantagruel Posts: 79 Match Maker
    Old bugs which had been fixed which were reintroduced in a new update
    https://forums.d3go.com/discussion/comment/914670#Comment_914670

    Oktagon are not fond of reusing other people's solutions to problems.

    Or, indeed, their own older solutions to problems.

  • FindingHeart8
    FindingHeart8 Posts: 2,731 Chairperson of the Boards
    Old bugs which had been fixed which were reintroduced in a new update

    Not too long ago I saw ye 'ol "Convert duplicate to runes" button from the beginning of Octagon times. It makes me wonder if some update in the future might remove our ability to Booster Craft until Octagon can fix it, considering it looks like they just built over it instead of fixing it.

  • madwren
    madwren Posts: 2,259 Chairperson of the Boards
    edited February 2020
    Previously working code which became bugged in a new update

    I actually picked the wrong one--fat fingers and tiny phone--but my vote is really OLD BUGS THAT ARE REINTRODUCED.

    Things that re-break are infuriating. If they ever why we aren't confident in their abilities, they should consider how many times bugs re-occur. Why would we have any kind of faith?

Categories