Grandmaster bug compensation

Saquongoat

The mistake they're making here is people averaged 3 more revives PER GRANDMASTER FIGHT. As someone who did the fight twice while bugged, I feel 3 is an insult. 6 is still not as much as I used, but I'm below average skill-wise. Why should I be getting as many revives as Fred who only did one path, or George who did 4 paths?

Dawnbringer_1

Well @Kabam Miike this fight was bugged in addition to parry and dex issues so the compensation for that better be in insane if it’s gonna account for all the items I used.

Skiddy212

Kabam Miike said:

Thank you all for the feedback, and I'm sorry that this Comp package isn't what you were expecting.

Context: The Comp Package went out to all players that started the quest before the Bug was fixed, and is based on the difference between resources we saw Players using before and after the bug was fixed. I see a lot of players saying that they used a bunch of revives, but players that played the fights after the Bug was fixed (roughly 6 hours after launch) also still used a lot of resources. The difference on average was what we based the package on.

This is NOT compensation for the ongoing control issues we've been experiencing.

I've also let the team know about the feedback here. Obviously, there are lots going on right now, and we're looking at many things, but I can make the sentiment known. No Promises that will go anywhere though.

This alone guarantees the parry/def bug compensation package is going to be absolute **** an not account for the MONTH(S) long **** we’ve dealt with. Losing out on shards, spending credits, potions etc. our stashed should be FULL with potions.

Thank you miike for me clear with us in this thread. But with the crappy stuff going on in game and all the bugs this is just not what the community wants to here an is off putting for the upcoming parry/dex compensation.

I hope I’m wrong, but I already know that comp package is gonna not be worth playing through the bugs in SOP an dealing with all these “where’s the compensation” posts.

Oh, an I bet the comp package will be delayed.

DawsMan

Haji_Saab said:

DawsMan said:

ItsDamien said:

DawsMan said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

Amusing that they used averages to determine this compensation.


Which kind of average? Did you average the number of users who did this prior to the fix and post fix? Because how do you equate tens of thousands of people before, to the potential hundreds of thousands who did it after?

What type of average? Did you use mode, mean or median averages to determine that this joke compensation? Because each of those would have had VASTLY different outcomes.

Why would they average people who did the Fight post-fix? It doesn't apply to this bug.

Because Miike stated, the average difference between those who did it bugged and those who didn't equated to the compensation. Which means they looked at some form of difference between the bugged fight and the non bugged fight. It wasn't the average of the people affected that they decided this on.

Come on man.

Yes, I had a brain freeze. I clued in with my last comment.
However, the idea isn't to compensate everything that was used. It was to average the extra used for that bug, so I can see what he's saying.

Yes but WHAT type of Average. A mean average is different from a mode average which is different from a median average. Because it seems to me they chose the lowest average and called it a day.

mean. Not even kabam would use the mode and the median would take too long. Why would it be anything other than mean. They don't need to try and screw us when there are tons of revives being spent on both sides of the bug.

I'd rather they took longer and actually compensated fairly instead of taking the quick and dirty option. It would at least make their data argument seem meaningful instead of just saying it to save face.

Averages are widely used. I doubt a program could do everything they would have to do to figure out each individuals potential revive compensation. Thousands of fights probably had to be looked over by a human.

10 revives .. based on my own experience plus the experiences of my alliance mates and friends across other alliances. 10 would have been reasonable.

Cold data doesn’t give you any insight without perspective of actual player experience.

They aren't in alliances or play the game. I'm not saying what they gave was right but when you have averages the lowest of lows and highest of highs really flatten things out.

TyEdge

DawsMan said:

ItsDamien said:

DawsMan said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

Amusing that they used averages to determine this compensation.


Which kind of average? Did you average the number of users who did this prior to the fix and post fix? Because how do you equate tens of thousands of people before, to the potential hundreds of thousands who did it after?

What type of average? Did you use mode, mean or median averages to determine that this joke compensation? Because each of those would have had VASTLY different outcomes.

Why would they average people who did the Fight post-fix? It doesn't apply to this bug.

Because Miike stated, the average difference between those who did it bugged and those who didn't equated to the compensation. Which means they looked at some form of difference between the bugged fight and the non bugged fight. It wasn't the average of the people affected that they decided this on.

Come on man.

Yes, I had a brain freeze. I clued in with my last comment.
However, the idea isn't to compensate everything that was used. It was to average the extra used for that bug, so I can see what he's saying.

Yes but WHAT type of Average. A mean average is different from a mode average which is different from a median average. Because it seems to me they chose the lowest average and called it a day.

mean. Not even kabam would use the mode and the median would take too long. Why would it be anything other than mean. They don't need to try and screw us when there are tons of revives being spent on both sides of the bug.

I'd rather they took longer and actually compensated fairly instead of taking the quick and dirty option. It would at least make their data argument seem meaningful instead of just saying it to save face.

Averages are widely used. I doubt a program could do everything they would have to do to figure out each individuals potential revive compensation. Thousands of fights probably had to be looked over by a human.

This comment is not a jab at you at all, because I found your post informative.

Here’s why using averages is incredibly dumb - you’re accepting as a baseline that half the users will be undercompensated. How is THAT a common sense solution to a problem?

Put everyone on a curve. If it follows a normal distribution, then compensate everyone at 2 standard deviations above the mean. 97.5% of players get fair (or possibly bonus) compensation and the appalling duffers in the bottom 2.5% get close enough. Even 1 standard dev would hit 84% of players.

Here’s the problem I see with the data set, though. Players rushing in early were the highest skill players best equipped to tackle the content, and likely to go 6/6 on objectives with full exploration. That type of player minimizes the impact of the big, while the people who stroll in after the fix may just intend to do 1-3 paths.

StevieManWonder

Kabam Miike said:

Thank you all for the feedback, and I'm sorry that this Comp package isn't what you were expecting.

Context: The Comp Package went out to all players that started the quest before the Bug was fixed, and is based on the difference between resources we saw Players using before and after the bug was fixed. I see a lot of players saying that they used a bunch of revives, but players that played the fights after the Bug was fixed (roughly 6 hours after launch) also still used a lot of resources. The difference on average was what we based the package on.

This is NOT compensation for the ongoing control issues we've been experiencing.

I've also let the team know about the feedback here. Obviously, there are lots going on right now, and we're looking at many things, but I can make the sentiment known. No Promises that will go anywhere though.

Bruh I spent 30 revives (including ones I had to buy with units) and I could only get him down to 54%. Between the dexing bug, the parrying bug, and the token of competence bug, that fight was the most expensive fight I’ve done in about a year (barring LoL VP with 4 star Star-Lord).
And you’re telling me that you guys had the data sitting in front of you telling you how much each person used and decided, nah, we’re just gonna send out three revives instead of sending out what they actually used.
Stuff like this is part of the reason why my interest in the game is dying.

Ghostspider231

I did two paths bugged why didn’t I get 6 revives?

ThēMandalorian

You're joking... Right?

DawsMan

TyEdge said:

DawsMan said:

ItsDamien said:

DawsMan said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

GroundedWisdom said:

ItsDamien said:

Amusing that they used averages to determine this compensation.


Which kind of average? Did you average the number of users who did this prior to the fix and post fix? Because how do you equate tens of thousands of people before, to the potential hundreds of thousands who did it after?

What type of average? Did you use mode, mean or median averages to determine that this joke compensation? Because each of those would have had VASTLY different outcomes.

Why would they average people who did the Fight post-fix? It doesn't apply to this bug.

Because Miike stated, the average difference between those who did it bugged and those who didn't equated to the compensation. Which means they looked at some form of difference between the bugged fight and the non bugged fight. It wasn't the average of the people affected that they decided this on.

Come on man.

Yes, I had a brain freeze. I clued in with my last comment.
However, the idea isn't to compensate everything that was used. It was to average the extra used for that bug, so I can see what he's saying.

Yes but WHAT type of Average. A mean average is different from a mode average which is different from a median average. Because it seems to me they chose the lowest average and called it a day.

mean. Not even kabam would use the mode and the median would take too long. Why would it be anything other than mean. They don't need to try and screw us when there are tons of revives being spent on both sides of the bug.

I'd rather they took longer and actually compensated fairly instead of taking the quick and dirty option. It would at least make their data argument seem meaningful instead of just saying it to save face.

Averages are widely used. I doubt a program could do everything they would have to do to figure out each individuals potential revive compensation. Thousands of fights probably had to be looked over by a human.

This comment is not a jab at you at all, because I found your post informative.

Here’s why using averages is incredibly dumb - you’re accepting as a baseline that half the users will be undercompensated. How is THAT a common sense solution to a problem?

Put everyone on a curve. If it follows a normal distribution, then compensate everyone at 2 standard deviations above the mean. 97.5% of players get fair (or possibly bonus) compensation and the appalling duffers in the bottom 2.5% get close enough. Even 1 standard dev would hit 84% of players.

Here’s the problem I see with the data set, though. Players rushing in early were the highest skill players best equipped to tackle the content, and likely to go 6/6 on objectives with full exploration. That type of player minimizes the impact of the big, while the people who stroll in after the fix may just intend to do 1-3 paths.

Good point. I do agree we need some phatter compensation

DawsMan

relentless said:

Lol it's quite funny that you all demand compensation but however kabam stated that the parry bug and dex bug was not fully fixed and to state that kabam also stated do NOT do long hard content as you might have to use revives or and potions. So in turn its actually the players fault for this. Yes it sucks because the content should be fixed but kabam did warn people

Yeah they can warn you but they put out a limited time event while parry and dex issues are running rampant. If I were to not do the content, i'm just missing out on a whole bunch of 6*shards and t5cc. As well, there was an awful lot of issues with the fight that made it very hard for people to get it down. They spent a lot of revives there when normally they wouldn't've.

Dawnbringer_1

relentless said:

@Dawnbringer_1 the irony of your statement is just that. Sure kabam shouldn't have released it while their is a bug but they did and you still chose to do it. The rewards for SOP were more than generous so it's just a bunch of beggers asking for free stuff

Nothing you said so far has made sense. If they didn’t want us to do it then why did they release it? I can’t wait to hear your answer to this.

Dawnbringer_1

relentless said:

Did you even read my comment I said they shouldn't have released it

I’m still waiting on the point you are trying to make, you said yet I still did it as if I didn’t suppose to, we are talking about the horrible compensation we received in return for bugged content. What point are you trying to make to justify kabam’s slap in the face to the players that experienced this bug?

Jgx

I used over 30 revives and then just gave up b/c he wasn’t even halfway down. Thanks for the insult Kabam. I won’t be doing any content like this again. Burned through over 1,000 units and you give me 3 revives? FU.

Syndicated

Each lost Token was a Revive Kabam

3 Revives are incorrect.

Nowan01

If this is gonna be the compensation then at least extend the event duration to let people grind for themselves to try to finish the quest lol.
I mean, it's obviously not ideal, but come on.
I personally been grinding these past days and encountered with yet another bug when farming revives, which was the quest auto-dropping me out of the quest and leaving me with nothing. Energy and time wasted.

DawsMan

relentless said:

Did you even read my comment I said they shouldn't have released it

Ok so one thing you said made sense. Yes sop rewards were fantastic. Doesn't mean we should be left in the mud due to a bug out of our control and swiping rewards from under our fingers.

Hordydordy

@Kabam Miike
What does “did the fight” mean? Completed the fight? I was 15 revives, hundreds of potions, and 600 units (in revives) into it when I backed out. I’m concerned that those that backed out of the fight probably weren’t added into the averaged total because they didn’t beat him.

StevieManWonder

relentless said:

Lol it's quite funny that you all demand compensation but however kabam stated that the parry bug and dex bug was not fully fixed and to state that kabam also stated do NOT do long hard content as you might have to use revives or and potions. So in turn its actually the players fault for this. Yes it sucks because the content should be fixed but kabam did warn people

To be fair, this is limited time content and they aren't going to extend the duration of SoP, so it's not like we can just wait for them to fix it.

StevieManWonder

Skiddy212 said:

All quiet now. Whatever, the silence speaks volumes.

Dude, the workday is over for them

Scopeotoe987

I used 38 revives on the grandmaster. 30 of those in the first 6 hours. 3 revives is not enough

Emeira23

I agree with everyone here, especially on the adjectives used, that this is the most pathetic, insulting and ridiculous compensation package ever given! @Kabam Miike , you just can’t compare the average of the first 6 hours… you know who are the majority of people that did this in the first 6 hours? Professional streamers such as karate mike, seatin, bero man and KT1! Most of us are NOT on this level of skill and spent WAY MORE!

Besides, I find it hard to believe that even with that the average was just three revives more, based on the amounting harsh feedback you’re receiving on this thread! I personally spent 400 units on a first try, gave up, then tried again and spent over 2000 more! I’m really bad against the GM, but instead of pinning that on my bad playing skills, Kabam needs to understand that this bug is proportionally worse on people that don’t do well on a specific fight.

Finally, understand this: it’s YOUR screw up! You don’t count pennies when you screw up your community, even though it was an understandable accident… you err on the generous side, knowing that the players were harmed by your bug!

I think this game is amazing, but when I think about the treatment given by the company to the community (with the exception of rockstars like you that deal with a lot of negativity with a constantly helpful attitude), I wish marvel had chosen another company to represent them.

Thanks!

benshb

That "data" you see that players are using many resources after the "bug fix". Is because the parry and dex are still pretty janky. And sure, that's the other issue going on, but then again how can you calculate the difference when an other bug is affecting the fight (like 2 out of 5 sp1 you get clipped [on average], and I literally had an intercept- which should have been mine, but the game lagged in the exact second we would clash and he came out victorious.)