People have completed this and gotten the rewards because they read it as they had to be included in the team. So with this statement people have spent items and units to do it with a 3 star team including the cyclopses to get rewards. Some daring not to open the rewards out of fear of a ban for something that wasn't their fault.
Clearly says with both here. Not only both, misleading players into misinterpreting the challenge and are now very worried about something they didn't know about
i do hope they get some sort of reprcussions. I did it as intended and failed. Spent nigh about 2 hours even reaching the collector. Wouldnt be fair for those who sailed through with 3* cgr tigra ghost when im slogging along with a **** champ that does barely enough damage.
So then Lagacy should have a repercussion for using the cosmic boon boost during his 6.3 legend run, while it was bugged?
It's a lose lose situation, so many people have done it with other champs now, that to cut everyone else off is unfair, but to leave it how it was went against the challenge. The only real solution, which I'll get downvoted into oblivion for, is fine who did it illegitimately, reimburse their items spent and revoke their rewards, make them do it again.
There is absolut 0 reason to do that challenge if you have content to do.
But there are endgame players that enjoy these ridiculous challenges.
And there are also a lot ppl that enjoy watching streamers do that challenge.
== noone is hurt and the rest enjoys aspects of it.
Btw if you even come close to tackle this challenge bc every content is 100% then do the canadian ST lol challenge first.
Better rewards and prob less expensive to do that
Unless you did it with Aegon or the like while it was bugged.
So you say don't do the challenge if you have done it already? That should be common sense
More so referring to the fact people are going to have to grind and chore their way through a decenfly Tough map, and a pretty horrible boss for any 3* with an absolutely abysmal 3* at that. When other people got to chose whichever champs benefitted them More, I bet their Aegons tore collector a new one by time they got there.
It's a lose lose situation, so many people have done it with other champs now, that to cut everyone else off is unfair, but to leave it how it was went against the challenge. The only real solution, which I'll get downvoted into oblivion for, is fine who did it illegitimately, reimburse their items spent and revoke their rewards, make them do it again.
That sounds like the most logical solution. Cause just fixing the bug now and not doing anything about it will make people upset, but at the same time, these people shouldn't be banned(even tho it CLEARLY says use 3 star Cyclops or lower) as it's on Kabam's side. Or even change it to where any 3 star can be used(even tho it says Miike's revenge). Either way, all of these solutions will make someone upset. Kabam seriously needs some bug testers for events. I already had to make a habit of not playing a new event upon release, and wait a few hours, as I know something about it is bugged. This situation is no different.
It says 3 star or below. So you can run a full 5 of them 3* and below if you want
Are you sure about this? That was my interpretation of the challenge's description too, but it would be nice to have some confirmation from kabam anyway.
Comments
There is absolut 0 reason to do that challenge if you have content to do.
But there are endgame players that enjoy these ridiculous challenges.
And there are also a lot ppl that enjoy watching streamers do that challenge.
== noone is hurt and the rest enjoys aspects of it.
Btw if you even come close to tackle this challenge bc every content is 100% then do the canadian ST lol challenge first.
Better rewards and prob less expensive to do that
Or even change it to where any 3 star can be used(even tho it says Miike's revenge).
Either way, all of these solutions will make someone upset.
Kabam seriously needs some bug testers for events. I already had to make a habit of not playing a new event upon release, and wait a few hours, as I know something about it is bugged.
This situation is no different.