Dev
Behavioral Systems July Update

Sharing our next areas of focus for behavioral systems improvements.

DevAuthorRiot Codebear
  • Copied to clipboard

Hey everyone, Cody “Riot Codebear” Germain here to talk to you about our focus on behavioral improvements in League and the thinking and intent that'll inform features coming up through the pipeline.

As we’ve discussed over the past few months, disruptive behavior in League is an area we haven’t made much improvement on in recent years. For our first phase of projects in this renewed push for change, we believe it’s important to tackle the in-game behaviors that directly impact the game outcome. We've defined that as behaviors that have the direct intention of causing a loss or direct intention of reducing the potential for a win, which can span intentional feeding, sabotage or game-based harassment (griefing), and idling or intentionally leaving the match.

Based on player feedback and report data, we believe we'll get the largest impact from meaningful progress on the following two goals for Intentional Feeding and Leaving the Game/Idling in Game:

  • Directly reduce frequency: This one's obvious, but still important to call out.
  • Mitigate harm to affected players: We can't prevent game-ruining behavior from ever happening, so it's important to us that we ensure the damage is minimized for its victims.

OUR APPROACH

As mentioned in previous updates, we're tackling these problems via iterative, solution-driven experiments with measurable results. We want to get our ideas in front of you for testing to find which ones have potential for meaningful, immediate change. If a feature needs years to ramp up before yielding results, it's too slow for us. 

Most recently, we’ve implemented our first experiment with Champ Select Reporting and Muting. The goal for this experiment, as stated previously, is to gather data specifically on behaviors that occur before rolling into a game so we can determine what actionable solutions can be put in place, and where.

During these experiments we’ll be actively measuring outcomes and communicating with you all on where we stand each month.

OUR NEXT ACTIONS

The following three projects will be the next things to come out after Champ Select Reporting and Muting:

  • It’s been some time since we’ve updated the Summoner Code, which is our definition and values around what's expected of League players. We'll more clearly call out situations that are viewed as disruptive, and more clearly indicate the consequences of those actions. Solidifying our commitments and guidelines as a foundation for the League of Legends experience will allow us to more cleanly tie solutions to disruptive situations that occur.
  • We’re developing enhanced automated detection methodology specifically for intentional feeding and idle/afk behaviors to confidently verify when these behaviors have occurred—as close to the occurrence as possible.
  • Though we’re working to directly improve these detection for these behaviors first, we’re also taking stock of the state of other behaviors and mapping out our next steps for improving detection there as well in the future.
  • We’re designing improvements to the actions that occur when we identify AFK behaviors. Those improvements will both consider what enhanced penalty actions mean for the game and assess how we can mitigate the impact an AFK has on you as a player.

THE LONG ROAD AHEAD

We've got a lot of ground to catch up on, but the team is committed to bringing our behavioral systems up to today's standards. We’ll continue to update you on a monthly cadence with changes, how solutions are performing, and where we’re going next. 

Please continue to voice your concerns, and let us know what you think of our experiments as they begin to roll out. 

Signing off.

-Cody



  • Copied to clipboard