**WINTER OF WOE - BONUS OBJECTIVE POINT**
As previously announced, the team will be distributing an additional point toward milestones to anyone who completed the Absorbing Man fight in the first step of the Winter of Woe.
This point will be distributed at a later time as it requires the team to pull and analyze data.
The timeline has not been set, but work has started.
There is currently an issue where some Alliances are are unable to find a match in Alliance Wars, or are receiving Byes without getting the benefits of the Win. We will be adjusting the Season Points of the Alliances that are affected within the coming weeks, and will be working to compensate them for their missed Per War rewards as well.

Additionally, we are working to address an issue where new Members of an Alliance are unable to place Defenders for the next War after joining. We are working to address this, but it will require a future update.

MODOK’s Lab is half over and there’s STILL no fix in site for the known randomizer bug?!?!?

Bryman187Bryman187 Posts: 204
edited March 2018 in General Discussion
@Kabam Miike @Kabam Wolf @Kabam Vydious @Kabam Loto @Kabam Zibiit

Seriously, what is going on?? This bug is obviously, easily recreate-able and affecting all devices on all softwares. @kabam is clearly deliberately ignoring this bug and that’s unacceptable. While this isn’t the most significantly impactful bug to date, it’s BY FAR the most obvious and egregious instance of KABAM ignoring an easily fixable known issue because it serves them to just leave it the way it is. This issue was first reported 12 days ago and it is easy to understand how it is costing players hard earned randomizers prematurely and no one has updated players with the status on a resolution since. I’m not asking for compensation, I’m just asking for this company to stop being so transparently nefarious. Stop ignoring this bug, address the players that are losing randomizers prematurely and do what’s right.

Comments

  • MhykkeMhykke Posts: 431 ★★★
    What's the bug?
  • DarkestDestroyerDarkestDestroyer Posts: 2,870 ★★★★★
    But that’s if your quitting out or leaving the game... just randomise and do the fight, it doesn’t reset if you do it properly lol
  • Bryman187Bryman187 Posts: 204
    edited March 2018
    But that’s if your quitting out or leaving the game... just randomise and do the fight, it doesn’t reset if you do it properly lol

    No, it’s if you use a randomizer on a match and then go claim one from your stash before you start the match that the buffs reset. The proper way to manage randomizers is to use what you need, even on the last fight, but before you start the match you claim from your stash what you’ve used and then you begin the final match. If you do what you said and use a randomizer and then start the match the new randomizer you receive for completing the fight will go into your main inventory instead of the back of your stash as it should. Not managing your inventory/stash correctly results in randomizers expiring before you can use them. The buffs shouldn’t revert under any circumstances if you used a randomizer.

    lol
  • KhanMedinaKhanMedina Posts: 927 ★★★
    This will be fixed on the last day, just like the Mordo/mesmerize bug in the last event.
  • Bryman187Bryman187 Posts: 204
    edited March 2018
    KhanMedina wrote: »
    This will be fixed on the last day, just like the Mordo/mesmerize bug in the last event.

    Most likely lol. So annoying. I guarantee this is a relatively simple thing to fix. A simple save state cache and a condition check would solve this. Probably only a few lines of code. Especially since this wasn’t an issue in the last Lab so all they’d have to do is compare the code. According to them all they did was change the interval/time period of the labs(which is a simple interger value change) and added a few buffs(which is probably just plugging a few more values into an array). But this benefits them so why would they fix it 😒
  • edited March 2018
    Hey there, we actually already have a thread going for this issues here. We're still working on getting this issue resolved as quickly as possible and this thread is where we're keeping track of the issue, as well as where we'll be updating everyone as soon as we have more information to share. Please feel free to share any extra info you may have about experiencing this issue and to keep an eye on this thread for future updates.
This discussion has been closed.