Absolute disregard

HotCarl
HotCarl Posts: 10 Just Dropped In
edited 11 November 2024, 00:20 in MtGPQ General Discussion

Do you guys even bother to troubleshoot anything before you set it out for a coalition event on the weekend? If you’re not going to have Support available to respond to issues that arise, you would think that the best option is to, at least, make sure what you’re putting out is functional. What a waste of time on my weekend. What a waste of time in the hours spent leading up to the weekend and crafting decks for it! I cannot say with enough emphasis how nonplussed I am right now. I have seen monkey **** fights orchestrated with more foresight than this mess. FFS if you’re going to do something try to achieve at least a modicum of adequacy. Seacrest out.

Comments

  • Tremayne
    Tremayne Posts: 1,673 Chairperson of the Boards

    @HotCarl - you have every right to be frustrated and possibly angry about the performance of WebCore this weekend!

    Please remember that the devs are real persons, when expressing your grievances.

  • Machine
    Machine Posts: 859 Critical Contributor

    I would have thought the forum to be ablaze due to the bottom two nodes being nearly unplayable because of the freezes. Yes, the devs are real persons, but this is the second time in a row that this event is bugged in one way or the other. This time even worse than before.

    This week we brought a new player in and seeing him write in our Discord that this game is not worth his time due to the bugs almost makes me feel ashamed for the mess the devs are putting out. I think asking why no one is available during the weekend to fix stuff when needed is a very valid question. And why not stop the event entirely and replace it with a different one, like has been done before? This is one of the worst performances I've seen from the current developers.

  • NickBKK
    NickBKK Posts: 98 Match Maker

    While I understand that mistakes can happen, what I find unacceptable this weekend is the Devs’ response after discovering the severe bugs. Instead of taking the event down and replacing it, they just made an announcement about the next update fix and left everyone to deal with it as if it wasn’t a big deal. It’s such an inconsiderate and mean slap in the face to the players.
    Also, if the Devs still haven’t learned their lesson, it’s now time to stop obsessing over legacy events! Why keep digging up landmines that you don’t even know how to handle? Seriously, are you intentionally trying to sabotage yourselves?!

  • Tremayne
    Tremayne Posts: 1,673 Chairperson of the Boards

    @Machine - that is indeed sad to hear about how a new player has felt about the event (and the game).

    By expressing your disappointment with WebCore without resorting to personal attacks, it sends a much more powerful message in my view.
    Secondly, if we, the players, want to get more interaction with the devs on these forums, I’m positive that we will achieve more with honey than with vinegar.

  • HotCarl
    HotCarl Posts: 10 Just Dropped In

    @Tremayne I agree with you on all accounts and, typically, I am more civil than not. I reread my post and with the exception of removing a “FFS” I will stand by what I wrote.
    This is not the first or even third time there has been an issue like this. Each time players have addressed them in what seems to be a reasonable manner. IIRC there has been the decency to restart or replace the event previously. This time it’s “Sorry ‘bout that, see ya Monday!”
    After all the honey sippin’ with minimal adjustments I thought spiking the drink with something a bit more vitriolic would catch some attention.
    I invest 30 bucks a month and between 3-5 hours a week developing decks for competitive play. I’m kind of done with purple and gold gems. I would rather be compensated with competency.

  • HotCarl
    HotCarl Posts: 10 Just Dropped In
    edited 10 November 2024, 20:37

    As an afterthought “Seacrest out” is pretty dated I might have to let that one go too…

  • naabaldan
    naabaldan Posts: 557 Critical Contributor

    Ok, the event was a mess.
    I guess it wasn't easy to let the event go but it looks to me as if they had no other choice.

    So we all tried to make the best out of it.

    After it was proven that the permanent support caused the freeze most of the time game strategy shifted to trying to get that gem out of a possible match avoiding the freeze.
    Unfortunately Greg was desperately seeking to match that gem as soon as possible and he won way to often.
    If so it was a very short match.

    Conclusion:
    I am not disappointed, it is an opportunity. Take it as it is. Find a smart way to deal with it. I saw scores like 160 and around 150. That's tons of luck and brain too. Congratulations.

  • naabaldan
    naabaldan Posts: 557 Critical Contributor

    Please, change the title of this post.

  • HotCarl
    HotCarl Posts: 10 Just Dropped In

    Agreed, I don’t think it’s a matter of competancy.

  • Sorin81
    Sorin81 Posts: 558 Critical Contributor

    I don't belive they had no other choice. We've seen events removed and replaced before, it could have been done with this one too.
    Having nobody around for the weekend should not be a valid excuse when the weekend coalition events, I assume, bring the most traffic to the game.

  • naabaldan
    naabaldan Posts: 557 Critical Contributor
    edited 11 November 2024, 05:33

    Thank you @HotCarl for changing the title

  • gozmaster
    gozmaster Posts: 263 Mover and Shaker
    edited 11 November 2024, 22:40

    @HotCarl said:
    This is not the first or even third time there has been an issue like this. Each time players have addressed them in what seems to be a reasonable manner. IIRC there has been the decency to restart or replace the event previously. This time it’s “Sorry ‘bout that, see ya Monday!”

    Yeah man, after the last event that got an extra event thrown in as a replacement, the player base went ape $#!t and grumbled that it should have been left alone and all players play the same broken event... so, damned if you do, damned if you don't situation here for the devs, it seems.

    That said, and as has been mentioned, I had fun (In my main account) working to figure out how to beat the "Player-Death-Touch" support (Nalthy came up with that name, I like it lol) I felt it was a new challenge we'd never seen before...

    However in my alt account, ooooh chile... that was a tough cookie to break lol, and for new players a REALLY bad experience. I just hope we didn't lose too many players permanently from it.

    I invest 30 bucks a month and between 3-5 hours a week developing decks for competitive play. I’m kind of done with purple and gold gems. I would rather be compensated with competency.

    I 100% agree, again, I have all the cards so mythic non-dupe packs from the set block aint going to do me any good, but I hope they both do something to compensate the player base as a whole (even if I already have the cards :tongue: ) but more important...

    ...I hope this event gets fixed so we don't have issues like this going forward.

  • Magic:PQ Support Team
    Magic:PQ Support Team ADMINISTRATORS Posts: 3,452 Chairperson of the Boards
  • Lightafire
    Lightafire Posts: 3 Just Dropped In

    I am also very disappointed how this fiasco was handled by Webcore.

    There was a post reporting the bugs in Bugs Report 1hr24mins after the event started. Webcore acknowledged the bugs about 1hr later.

    Instead of replacing the bug infested event, Webcore would still make the KHM booster and VG packs available in the vault 5mins later in response to another player's request earlier. Curious how those players would feel after buying those packs and then found out the event was unplayable in the bottom nodes.

    I would like to know how they managed to push the booster packs to the vault while they claimed their staff was gone for the weekend. If it was done remotely, then why the event could not be replaced?

  • gozmaster
    gozmaster Posts: 263 Mover and Shaker
  • Janosik
    Janosik Posts: 590 Critical Contributor

    Ok now tag all the other threads in the bug forum with [To Be Fixed] too :)

  • Janosik
    Janosik Posts: 590 Critical Contributor

    @Lightafire said:
    I am also very disappointed how this fiasco was handled by Webcore.

    There was a post reporting the bugs in Bugs Report 1hr24mins after the event started. Webcore acknowledged the bugs about 1hr later.

    Instead of replacing the bug infested event, Webcore would still make the KHM booster and VG packs available in the vault 5mins later in response to another player's request earlier. Curious how those players would feel after buying those packs and then found out the event was unplayable in the bottom nodes.

    I would like to know how they managed to push the booster packs to the vault while they claimed their staff was gone for the weekend. If it was done remotely, then why the event could not be replaced?

    Perhaps Webcore thought they were doing the right thing leaving it up; there was a huge problem when they ran ATV, and they tried to replace it mid-weekend, but it was done poorly and the response was not well received.

    Bugged events are not uncommon and Webcore probably need an official policy on what will happen when a bugged event occurs so we know what to expect. IMO this should include not only appropriate progression prizes and/or compensation being paid out to players, but also player points for the weekend being scrubbed from player's coalition scores. Competition and coalitions are an important part of the game, and all kinds of players, not just those at the top of the leaderboard, like to do the best for their team, and that can include feeling pressure to compete in a broken event (especially if we think the event might vanish and those potential points be lost... this didn't happen with DC or ATV, but has happened in the past)

  • Janosik
    Janosik Posts: 590 Critical Contributor

    Hmf. Same bug again a week later in Skoti Bloodlines.

    @gozmaster said:
    That said, and as has been mentioned, I had fun (In my main account) working to figure out how to beat the "Player-Death-Touch" support (Nalthy came up with that name, I like it lol) I felt it was a new challenge we'd never seen before...

    Honestly you know I was looking forward to messing about in this version of Skoti Bloodlines, since it's not a coalition event, and so the stakes were very low.

    Kinda laughable isn't it that this bug is probably the most innovative gameplay experience that Webcore have ever created :P

    However, shortly after I paid my 20c entrance fee, and before I'd had the chance to play a single game and win some progression rewards, they prematurely ended the event without warning...