**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
Game Down Aug. 9 [Merged Threads]
This discussion has been closed.
Comments
down for me as well.
yes, down... again.
#plzfixyourserverskabam
GDPR: it doesn’t break this because they aren’t giving away any private details, all they are doing is announcing a made up, non-personal ingame name. If the name is personal then the player themself is at fault as they are told not to make personal names. Other games announce cheaters, Mcoc is the only game I know that is so hellbent on protecting cheaters identity and causing undue trouble for the honest players of the alliance. Future fight, as an example, publishes lists of players who are banned fairly often I believe.
Detection methods: it’s a pretty silly statement to claim announcing who is caught would ruin their detection methods. Let’s say Player A pilots for player B. A few weeks later, the leader gets a mail saying their points have been docked, someone in the alliance piloted. The leader would talk in the line chat and ask who did it. Player A and B both stay quiet but they know they are the ones who did it. They know nothing about kabam’s detection methods.
Now let’s go back, but change kabam’s privacy policy. Leader gets a message saying “Player A and Player B have been caught piloting” (or perhaps it would just be Player B, since his was the account). Regardless, the leader knows it was player B so he is kicked. How on earth would Player A or Player B, or anyone for that matter, know any more about kabam’s detection methods?
Announcing a name, cannot give any information about their detection methods. Don’t believe me? Look at what happens with modding. This is the same situation except the user gets banned and doesn’t log in, essentially, they have been outed, their name was announced.
The player mods, is caught, and is banned. The leader sees that their rating was reduced and wonders who it was. 3 days later, a member still hasn’t logged in. They know it was that guy. So now, because kabam’s privacy policy doesn’t protect modders who get banned, do you really think that anybody involved in the situation knows any more about kabam’s detection methods?
I’ve seen GW post this a lot and it’s always bothered me, but here is my correction to the flawed logic.
@Kabam Miike please see this post and do something. contest is down.... grandmaster will be very angry on you if this goes on
#FixYourDamnServers