League of Legends Dev Tracker

I got a bunch correct in a row by just selecting the team with more tanks until I picked a team with Tahm/Voli/MF that all decided to build full AP.

I'm very curious to see the prediction accuracy of human agents vs a machine learning model.

hi hi i'm not them but we're on it :)

u/dhiwbrvej ty for the post - as folks guessed this was just an oversight, our tutorial mission tests passed because blind pick was still available. Fix will be in ASAP, and we'll be changing the mission text to say that you should play Quickplay!

Well, dodging has gone down quite a bit since the change was shipped, so it did something.

Way back when it was shown, the problem folks in this thread are describing was very real. Back then the cut off for Gold (rewards) was 1500 MMR and since you could lose below 1500 without any protection players would get to 1500 (or pay) and then stop. As I remember, Yegg (the designer who initially worked on the new ranked system with tiers and divisions) was right around 1500 MMR and I believe fell below the mark. They then had to play a game right at the deadline of the S2 ending to get back into Gold (and I mean literally the season ended while they were in this game, me and some other folks were watching live). They said the anxiety to not play and risk falling below was real and that helped fuel the new system.

Yes, and unfortunately sometimes ease of communication is not the only factor in our decision-making. Sometimes we make things that cause more harm than good. Speaking as the designer for the ping wheel, I have ... regrets. I wish I could go back and tell my naive past self that '?' is not the correct icon for MIA. Y'all get so creative with the tools we give you and that extends to expressing your frustration as well, and that was not something we anticipated at that time. When I was designing the system for Wild Rift we chose a different icon and that worked out much better. I think it would be much harder to remove in League, because of how expressive '?' has become and how accustomed players are to using it, but in a new game we could just change it from the start and MIA BM was almost eliminated, while the MIA ping was still very highly used.

I wasn't involved with these changes, but I'm pretty sure they had strong evidence that ult pings were overwhel...

Except trying to mitigate flame in fact does work. No one receives death threats in games without chat in them. The fact that surveys indicate that people feel less flamed when there are fewer specific pings reinforces that. And it's not about tilt. It's about, for example, not wanting to receive death threats while attempting to communicate with players, in or out of game. It's really not that much to ask for.

You can absolutely make a good faith claim that this reduction in toxicity is not worth the cost in good faith communication. But that's a judgment call and not, "it doesn't work." Because it does have an impact, actually.

Aftershock was replaced in 13.22! Wasn't noted in the patch notes (will be noted in .23 alongside Glacial). Thanks for the report :)

To be fair I'm also extremely hard-headed sometimes.

I'm also happy to have unpopular opinions. I think Dynamic Queue's problem was kinda just an extension of the "Elo hell" collective delusion: People believed the ladder didn't matter because they thought everyone just abused group queueing. Anything to convince yourself you're not accurately rated below your goals. My experience as a Flex Queue enjoyer is that players still end up at their appropriate brackets despite the boosters. Somewhat similarly with role-based MM, it was people's fault. People would just say, "Oh, I didn't get main role, I'll just troll." I was excited to get an MMR per-role. I know I'm a worse Mid than Bot. I'd like to be fairly ranked at that role and play games against similarly-skilled mid laners without running an alt account.

Yeah that was a pretty dumb thing to say. I don't want to make it sound like your feedback is being ignored. It's obviously incorrect to imply that typing just 1:1 replaces quick pings as well. My bad on that.

Right now, overall player feedback has indicated that these changes have been good for the social experience as a whole. But as with anything, we intend to always keep our eyes and ears open. It could be there's something that we're missing, it could be that we think it's better back the way it was, even if there were measurable gains in toxicity, it could be that we find a perfect system that re-adds everything that you miss while retaining those gains, or something else entirely is the future for player communication tools.

Certainly we've made mistakes in the past. There have also been things that I personally enjoyed that players overall didn't (Dynamic Queue and role-based matchmaking were both things I personally really liked that didn't pan out). This i...

Well I couldn't get Hexflash to not not-cast itself, so I instead added logic to just unwind the the spell and have you start really channeling Hexflash. You still lose the mana cost and CD from starting your W (because you did that) but now you just transition into Hexflashing instead of starting your W dash. TBH I really didn't get the root cause but this is better than disabling the rune. I still have no idea why Hexflash is not castable but yet tries to start casting anyway. No other spell works like this.

People got better at him.

The buff is removed on death intentionally. The internal tagging allows it to persist, it's told to disable the bouncing behavior and to remove the buff within its scripting, which reads as design intent to me. Maybe it shouldn't, but the current scripting is very much intentional.

Hi, I developed this. I've also just submitted an actual fix for the Hexflash bug, so we'll see if it comes back clean from QA.

Let me give some context on why this rune replacement was in: This bug is not a trivial fix. K'Sante W disables his other abilities and any Summoner Spells that are dashes/teleports. This disables Flash, Teleport, and even Hexflash. Hexflash is grayed out when you are channeling W. It's also disabled while you're actively dashing. I put debug logic onto the very first step of the Hexflash spell, and that debug does not fire. Hexflash does not cast or even begin casting if you press D/F while channeling W. And yet it cancels K'Sante W. This is not "simply" rescripting the logic of Hexflash (it doesn't cast) and it's not a trivial amount of work on K'Sante W (it already properly locks out spells). This bug is a meaningful amount of power and it is also very low impact (the rune has about a 1% pick rate, even in higher MMRs).

Obviously disabli...

*sigh*

*upvotes*

Yes I did

Across the entire match, only two people will be able to take it. So, if someone sees it in the first round but doesn't take it, it will go back into the pool for subsequent rounds.

And thanks for the kind words!

Your "because what are we supposed to do, then?" sums it up pretty well. :) Frankly, I don't know yet how exactly we can make the situation better. It'll take an effort of a bunch of us at Riot to figure something out.

In some cases, I actually don't know what else we can do, besides telling people "we hear you even if you aren't the majority". If we've made a decision that we believe in, and that the folks in question disagree with, then, well... that's kind of all there is to it. :o

Yeah, some sort of response system and/or cadence would be nice. Everyone's busy with Worlds right now, but there's a conversation to be had. Dunno where it will lead, we'll see.

What you are talking about is a system change driven by Riot's expanding eco-system. We are no longer a one-game company, and thus, we need to adjust things to make the backend interactions of different game accounts better.
In what world would data be the driver for this implementation? This isn’t a gameplay change, this has to do with platform engineering.
Look inward to resolve your anger, my friend.