@Riot: After you've fixed the Xerath exploit, could you do one more thing?
Could you remove those Xerath games from what's counted as "S+" grade material?
The last thing I need is to be compared to someone who went 115/0/1 with 394 CS at 10 minutes.
Could you remove those Xerath games from what's counted as "S+" grade material?
The last thing I need is to be compared to someone who went 115/0/1 with 394 CS at 10 minutes.
just git gud.
XD
tbh if you don't go 200/0/121 and have 400 cs by the 5 minute mark you should just uninstall. Life.
The last thing I need is to be compared to someone who went 115/0/1 with 394 CS at 10 minutes.
https://img.memesuper.com/aceaa9e624e4cb4090d98dc61a9daf85_9428036-comment-git-gud-meme_480-360.jpeg
It goes on a rolling basis. What Xeraths did now won't be in the system soon in the future, plus the amount of games played on exploit and actually successful are minuscule to the total amount of xerath games, so your S performances shouldn't sway much at all. If you didn't get an S, it's your fault.
It goes on a rolling basis. What Xeraths did now won't be in the system soon in the future, plus the amount of games played on exploit and actually successful are minuscule to the total amount of xerath games, so your S performances shouldn't sway much at all. If you didn't get an S, it's your fault.
Thats.. just no. Thats ignorant on so many levels. While its true they cycle out, it takes months to cycle out and games like that - games where you go, say, 30/3/10 with 300 farm -raise the average for EVERYONE. the system doesnt account for outliers, and outlier games raise the average scores for EVERYONE.
Have they ever said how quickly they "cycle out"?
It wouldn't surprise me if it was every patch or so maximum, as buffs/nerfs in the patch (both directly to the champion and to items/other champions) can have an impact on how well a champion is played.
Do we know the cycle length or are we all assuming we know our own version?
I'd also like to see what you meant by "ignorant on so many levels." That's a discrediting statement, one that's not pertinent to the facts of the conversation, so if you'd like to use that, I want to see the exact, multiple unique levels that I'm ignorant on :).
Don't feed into OP's excuses. He didn't get an S because he didn't earn it. Not because Xerath's bug made getting an S impossible.
Don't feed into OP's excuses. He didn't get an S because he didn't earn it. Not because Xerath's bug made getting an S impossible.
I've got all the S's I need on Xerath until next year when the chests reset. My most recent Xerath game was an ARSR on Monday (the day this whole thing broke out) where I also got an S as well. I really am just pointing out something that should be cleaned up.
For those who would say "pics or it didn't happen":
http://i.imgur.com/eJOnJsL.png?noredirect http://i.imgur.com/txh6wF1.png?noredirect
Well then don't complain when you don't get more. Anyways, point is, no matter your performance, the effects of broken Xerath didn't elevate the status of S or anything.
I don't think you understand statistics. With a champion pick rate of less than 5% and a decent KDA of 4, it wouldn't take many 100 KDA games to seriously throw off the numbers. Each game would count for 10-20 other games played at an above average level.
5% pick rate may not seem like very much, but remember that is 5% of every. single. game. played on the server, and not everyone playing Xerath right now is using the exploit. We are still talking about a huge number of total Xerath games that the exploited games have to be filtered through.
We don't know the algorithm that Riot uses to judge scores. While it compares an exploited game against the current "good" scores and give a grade, there may be systems in place that detects extreme outliers (i.e., KDA over 20x greater than average good) and prevent those outliers from being averaged into the "good" score already.
5% of the playerbase is still massive. This little blip won't be the reason you didn't get an S. Not sure if this is what you're trying to do in your mind, but finding things to blame for lack of an S is not good for you. You didn't get an S because you didn't deserve it, no rudeness intended.
So in terms of who understands statistics, if you take 5% of the last recorded number of active players. being 100 million, you get 5 million. You think this small bit of broken xerath would influence 5 million games or a bit less? And not only was playing broken xerath a requirement, you needed to do well as well. The fact that he wasn't at 100 win rate shows there was success and there was failure.
Again, your lack of S was your fault.
it still raises the average does it not?
I don't think you understand statistics. With a champion pick rate of less than 5% and a decent KDA of 4, it wouldn't take many 100 KDA games to seriously throw off the numbers. Each game would count for 10-20 other games played at an above average level.
As one studying complexity theory at the graduate level, I would have to point out that the situation itself is actually a bit more tricky than it might seem. The "butterfly effect" of the Xerath bug had a trickle-over effect for more than just the Xerath player accounts - the exploiters' other accounts where their IP might have been transferred; their champions; the players involved in those games on the same side as the Xeraths; their opponents; and so on.
It's a huge intertwined mess. The simplistic approach is to get rid of just those games. But then that ignores the ratings affected by the players (I know that a couple of streamers were in games where they were in their Promos when it happened); then there's the IP earned and the possible stuff purchased and transferred to other accounts. I don't envy Riot's decision here - especially given how long the exploit was out there.
[deleted]
There are/were multiple accounts using the scripts...
I kind of hope they don't just so Mastery 7 and 6 Xeraths become one of the rarest sights to see lol
I've already got my Level 7 and chest for this year, but it's still nice to see an S+ once in a while, ya know?
Mastery 7 xeraths will be the new way to wade out the cheaters from everyone else
Indeed, thanks.
adter they fix xerath they should fix the game [slayer-jinx-wink]
https://www.youtube.com/channel/UCU-DdXLcUSfyMosN5yeaWcw this %%%g is ruining ranked
115/0/1 with 394 CS at 10 minutes.
But you HAVE to be that GOOD if you are playing Xerath.. .duh XD
Maybe you should actually play xerath "properly" then kappa.
Besides xerath has always been the go-to champion to script, so i magine its hard already to get S.
it actually isn't in my experience. he has been pretty mediocre for a while now, and he rarely receives attention unless it's related to a bug or exploit like this. His stats are kept consistently pretty low and since I'd assume their system is based on averages, the tiny scripter population increases it, but is too small to make much of a dent.
Don't worry. I have a feeling it's a drop in an ocean.
Im spamming this everywhere. Kassadin needs a visual update. Pls rito
Ohh... so that's why I have been having trouble getting S scores recently. Supposedly 12/2/14 with 314 cs wasn't enough for an S, let alone S+
or.... ban those who abused the bug?
Banned accounts still have match histories, and presumably their scores effect champion mastery as well. Xerath players from here on out shouldn't be forced to have a harder time getting S scores because some players cheated.
They need to fix the mastery system in general... Apparently 3/2/49 as Sona is an A-...... over 15k gold in a 32 minute game. It's so bad.
They need to fix the mastery system in general... Apparently 3/2/49 as Sona is an A-...... over 15k gold in a 32 minute game. It's so bad.
You could have a point there - but then how many wards did that Sona drop? And was it actually in a support position?
When I got my Xerath to M7 it took around a month, and then this happens and people get free S+'s. It's sad