**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Comments
As I mentioned in the other thread earlier, you have to punish alliances and not just individual accounts because limiting punishment to only the cheating account is exploitable.
Correct. They could have a Patsy. Also, all Members receive "stolen" Rewards.
If you’re going to punish alliances for their unknowing complicity in cheating, then you need to provide them with the necessary information with which to root out the cheaters. Otherwise, by not allowing alliances to take action against the cheaters, Kabam themselves are complicit in allowing the guilty parties to reoffend... as members of the same alliances that they penalized!
Because you benefited from an unfair advantage.
My stance on that should be well known by now, but I've stated repeatedly that this policy should be changed on multiple grounds. But that is irrelevant to the specific topic I was replying to, which was the suggestion that you could only punish the one member of the alliance through penalties or bans, while leaving the rest of the alliance completely unaffected. You cannot do that, whether the notification policy changes or not, because that is exploitable. Allowing an exploit of that nature is tantamount to doing nothing at all.
Can someone who has knowledge of the situation clarify the timeline:
1) t5 basic shard sale
2) roughly 90 minutes later delay to matchmaking
which one was next war search or bans......
In other words did alliances have an opportunity (after t5 shard sale of course) to adjust their rosters for any banned players before searching wars.....
to tie in OPs question..... if bans occurred after war searches hit..... they are going to be hit even more as collateral damage