Dee Eight, on 28 October 2016 - 08:03 AM, said:
Yes I've said it isn't true because the principal data being relied on were leaderboards events where there was known wholesale cheating going on, by organised & coordinated groups repeatedly dropping together to farm one another, as well as players using new alt accounts to game the matchmaker to put themselves in lower tiers against less experienced players. There were threads upon threads about it at the time the leaderboards happened and it kept on happening with every leaderboard event. PGI apparently paid attention because the latest one for the huntsman, they took the 1000MC and 5 million Cbill rewards away and POOF... all that magically stopped because it was no longer worth the effort just to get a single cockpit item.
Players in the kodiak leaderboard in particular took advantage of the fact that there was no ghost heat being applied to 3 or more Ultra-10s firing together as there was supposed to be, and even if it had been, it was minimal. PGI corrected that error in the coding already, and also dramatically hiked the ghost heat levels as well. They also apparently added a new bit of code that treats a pair and a single ultra-10, fired close enough together to trigger ghost heat, to also count it as if SIX had fired at once if you double-tapped them too close together, with appropriate ghost heat. So instead of 17 heat twice, you get 87 heat.
Thus it is now much harder, to achieve the results in the mech, that were being put up months ago, under different coding, and without the benefit of deliberately cheating/flaunting of the event rules. But yes, by all means, keep relying on old flawed data to prove your theories.
Additionally...for the first kodiak launch leaderboard... the game was experiencing MASSIVE server wide QP disconnects of entire teams / matches. If you knew it was happening, restarted your client and then re-joined the match, you could often an entire enemy team of standing still targets in their drop zones, who could then be farmed for all the scores you needed to vault up the leaderboard. Since it was happening so often, you could sync drop teams together during off hours, have everyone that was going to be farmed execute a disconnect from match (easy to coordinate over TS chat without any record in the match logs), and then blame it on a server error if PGI looks into it. A few folks have brought up WoT tanks that were OP. Funny how they didn't mention the organized cheating using the exact same methods that went on over on that game during leaderboard events. I've seen server issues since then where that still happens occassionally in QP, though not with the every other game frequency it was during may.
I had this match result from one of those mass disconnect errors in solo QP during that May kodiak leaderboard event. Eventually 5 of 24 players in that game did reconnect, and our team which had a couple revivals first ultimately lost, but even though I was in a kodiak, I stood BEHIND the enemy mechs to kill them quicker with less ammo needed to be used because I wasn't gaming the damage scores to pump my match up, and also I wasn't the only one on my team who'd revived and was trying to take the enemy team out quick also (there was a TBR player with me who managed most of the damage into one of them and killing blowed another which is why its 8 killing blows 1 assist and only 7 solo/kmdd). So my leaderboard score for that fluke game was 538. And yet folks were posting leaderboard results on mechs where they did such scores TEN times in one day. If you look at the August Epic Assaults and WotW leaderboards, there's a distinct group of players who posted standout scores well above the curve that others were producing, and they've consistently done that in many leaderboard events with other mechs. But ohhhh noo...it must strictly be the KDK-3 is overpowered... couldn't possibly be cheaters who skew the results.
Oh, the cheaters excuse. Yes, let's denigrate others for naturally doing better than you. That's the best way of proving your point!