EMERGENCY MAINTENANCE
There was an issue with an offer that sent out a surplus of Tier 7 Basic Catalysts.
While the Game Team investigates a way to remedy this issue, we will be putting the Game into Emergency Maintanance.
We do not currently have an estimate on how long this will take, however, we will let you know as soon as we know anything.
Thank you for your patience.
There was an issue with an offer that sent out a surplus of Tier 7 Basic Catalysts.
While the Game Team investigates a way to remedy this issue, we will be putting the Game into Emergency Maintanance.
We do not currently have an estimate on how long this will take, however, we will let you know as soon as we know anything.
Thank you for your patience.
How many docks does it take for players to stop modding in AW Seasons?
This discussion has been closed.
Comments
ANYONE who cheats should be banned. PERMABANNED
Maybe then people will stop risking it. For anything. Arena mod. Banned. Done
They give out bans for X hours, and that is that. Then the next offense, X more hours, and so on.
Pretty much means that they don't want to or can't enforce the TOS, in fear that they were wrong.
Remember not to long ago they were throwing out bans for Quake players that were winning matches, yet, had 0 hits. Then they had to give them compensation for wrongly flagging them as cheaters.
For the docking in AW, they even REFUSE to tell what player(s) did it, so that any legit leaders & officers have no clue on who to kick, until they see someone that hasn't logged in for a few days. How does ANY of that make any sense?
I do think that these guys that cheat, that jump from alliance to alliance, and all the arena bots (that are STILL GOING ON TODAY) need to be permabanned, no question about it, but, they need to be correct, flag their accounts and monitor EVERYTHING they do, the battles and so on, and then take that data and run a simulation to see if the numbers match up, if not, nuke their account.
If he suddenly agreed with all of you would kabam immediately align their cheating policy with literally the rest of the entire world? No, they wouldn’t. So who cares
To the point, cheating is cheating, whether it is through modding a mobile game or modding a football to gain an advantage. Unless you can provide evidence showing that a cheating ally is using mods to affect their AWD, you cannot say with 100% confidence that the ally 'playing fairly' would have won.
As for giving the win, which we know kabam will not do, what would, in your mind, be a fair compromise? Restoration of war rating lost to the cheating ally? The 50k bonus, sans multiplier?
The only unearned win is the win achieved through cheating. 2 teams play each other. One team gets the 50k win bonus with multiplier for winning. If the team that got that win bonus cheated then the other team gets the bonus. They’re not getting all the winner rewards so it’s not “full awarding” of anything. It’s just maintaining the integrity of leaderboard for these toxic AW seasons.
Otherwise the scores and placings on the leaderboard are compromised due to one alliance cheating, and the victimized alliance is unfairly penalized in the season standings.
If no team gets a win bonus then there is no winner. If there’s no winner then it’s not a contest. Marvel friendly exhibition where nobody wins of champions.
The only thing that affects the integrity of the leaderboard, is the presence of a cheating ally. To maintain integrity, they need to be disqualified from war participation, and removed from the leaderboard altogether. Any other adjustment would be 'correcting' for one by hurting others.
No thank you.
Stopping the modding by improving the tracking methods kabam uses (much like they did with piloting) is the main issue here. Yet kabam remains silent. A simple comment from kabam committing to improving the tracking methods for catching modding in AW will go a long way (for now, then followed by actions in the near future). Thats all players need to hear right now.
Anyone from kabam care to respond to this??????
Let's also bare in mind that they're likely not at liberty to say anything about situations like this until all their ducks are in a row. Obviously we all want an update sooner than later. I'm right there with all on that. Just the same, I have this feeling something major is coming soon. This feels like the calm before the would be storm for those who've consistently been a thorn in the legitimate playerbase's side.
It does feel like we're at a tipping point and Kabam has to know that. With word that other major app developers are cracking down hard on modding, one would assume Kabam has been formulating a plan for such as well. Trouble is, if it takes too long, the damage control team might be in for a rough ride. All we can do right now is continue to make it known that this is an ever growing problem, and stay the course. Hopefully I'm right that there's already a major plan in motion and the cheater's days are numbered.
It does blow my mind that the common reason/justification for cheating is to 'screw Kabam.' Which has to be the most backwards nonsense I've ever heard. Giving the company whom already have mounting bug issues MORE problems to deal with and in turn distracting them from focusing on fixing them is just dumb. Typically that's why players are upset in the 1st place. So why add to the problem? In the end all they're really doing is screwing those that play fair AND themselves in 1 foolish motion.
Sadly, assumptions on how mods are supposed to work are what allow players to use mods without being caught. These players have cheated together in multiple different alliances for more than 4 seasons. The more they receive temporary bans and continue to use mods, they more they share their experiences of how to continue altering mods used to avoid getting caught again.
This is why players who are aware of how this situation has progressed to this point are pushing for permanent bans. These types of cheaters have accurate knowledge of how Kabam’s mod detection system works from more than half a year of experience learning how to avoid it.