Riot has posted up a reveal for their upcoming Featured Gameplay Modes, something first discussed when a 5 of the same champ vs 5 of another champ mode squeaked onto live.
"Featured Gameplay Modes are about ready to burst onto the League! We have a variety of experimental modes - each with a unique spin on the classic League of Legends formula – that we’re looking to introduce one at a time. We’re limiting the availability of each mode so that you can try out a variety of different game types. After they’re brought down, we’ll check out your feedback as we develop new game modes - there’s always a chance that we’ll bring back the ones you love the most, too.
The first mode we’re introducing is One For All, which consists of two teams of five players all using the same champion. The One For All matchmaking queue will be featured on Summoner’s Rift, but you’ll be able to try the mode out on any League map via custom games. If you’ve ever dreamed of nuking an enemy team with five Final Sparks, chaining together a series of Unstoppable Forces or living forever with back-to-back Chronoshifts, now’s your chance."
"We’re really excited to work with you guys on developing new game modes so let us know what you think."
Continue reading for more info and discussion!
Here's Brackhar with more information:
It's been roughly a month now since we first talked about One For All, our first featured game mode, and in that time our team has been hard at work getting the last few issues resolved. Starting this weekend we'll be testing the game mode on PBE. Given that, I wanted to take some time and give a bit of insight into some of the challenges we've run into getting the feature off the ground. As we promised in the initial discussion, we really want to strive for an open dialog about each of these game modes, and discussions like this will be the first of many steps along that vein.
One For All, at the outset, seemed like a pretty straightforward game mode to develop, but we ran into some unique challenges along the way. As some of you might have seen when One For All was temporarily "available" a few weeks ago, when multiple copies of the same champion are on the same team, their abilities tend to clash in unique ways (like only two Heimerdinger turrets per team, regardless of the number of Heimerdingers on the team). This was due to the way these abilities were coded, so our first road bump was to tidy them up - no big deal. The real challenges we faced came from more nuanced interactions.
A fundamental design principle that we value highly is that of "Intuitiveness" - effectively, when you look at a skill or ability can you easily extract what it will do when used. Big ice bolt that explodes? Probably does some damage and slows. Spell called "Transfusion" that pulls blood from the target? Probably a damaging and healing spell. Making champion abilities intuitive, even when multiple copies get stacked on top of each other, was an important project we wanted to tackle. An example here would be Akali's Twilight Shroud: should it stealth every Akali who enters it? Sure! What about giving them the magic resistance and armor bonus per additional shroud? Maybe not.
Here we decided to break apart each skill to identify their core fantasies. Like Akali's shroud, where the stealth was important while the defensive stats were secondary, we went through every ability in the game to create a roughly balanced experience. In two cases with Teemo and Karthus, however, we ultimately couldn't find a balanceable solution for them in blind pick and had to take more drastic measures. For this particular release, we opted to actually remove them from being selectable champions in the matchmaking queue, although they will be selectable in custom games for those who want to try. Fighting five Teemos was like reenacting World War 1 with landmines everywhere, and fighting five Karthuses (Karthi?) was just getting aced every 160 seconds. So... don't say we didn't warn you!
Another open question was determining how people would select their champion. In a matchmaking queue we needed a solution to help a group of random people come to a seemingly fair resolution. We knew we wanted a banning phase and, since the captain would be responsible there, we first started with having the captain choose the champion for their team. After a few playtests though we saw the captain just choose whatever champion they wanted, regardless of their team's input.
We next explored solutions with voting, hoping it would help drive toward team consensus. This didn't work out much better. In boardgaming there's a style of play called "Kingmaking," where a player stops playing to win and instead works to tip the scales in favor of another player - we saw the same approach adopted here as well. Frequently we'd see four players disagree and each vote for a unique champion, leaving the fifth player with a choice. Either they could vote for their own champion and maybe get it via random choice in a tie-breaker, or they could vote for one of the other champions that, while not their first choice, was still acceptable. The value of voting last quickly caught on, and soon everyone was waiting to last second, hoping to get that kingmaking opportunity. Ultimately the final solution we came to ended up being fairly simple, even though it took a while to reach: a champion would only be selected if it ended with a strict majority of votes instead of simply being "the most."
The final question we faced has more to do with game modes in general than One For All in specific: availability. After a lot of discussion, we came to the realization that if we wanted to deliver fun, unique game modes with a lot of ongoing player engagement, launching them as permanent fixtures whenever we felt confident enough to ship wasn't the best approach. Having a game mode permanently available has a number of costs, the first of which is increased stability and support costs across the entire game. While adding a single game mode has a known impact, the multiplicative effect of multiple game modes living side by side means we'd soon be bogged down by simply maintaining these game modes, unable to work on the next unique thing.
A second consideration is that having a game mode permanently available actually is a big restriction to the type of experiences we can create. If we want the mode to have a healthy player base a year or two years from now, each game mode needs to be designed to remain engaging after thousands of hours of play. Due to the difficulty of that task it means every game mode would take an exceptionally long time to develop, and we wanted to give you guys stuff much faster than that. By intentionally going into this with the expectation that a game mode is temporary, it freed us up drastically, and it really allows us be much more experimental with the game modes we try.
After we cycle out a game mode, we'll go back to the workshop to tinker with it based on player feedback and, in the meantime, we'll deploy a few other game modes we've thought up over the past while. This lets us rotate any number of game modes in and out as we refine them, and it gives us the freedom to even take community votes for a "player's choice" month!
For the release of One For All, the matchmaking queue will be for Summoner's Rift, but you'll be able to play the mode via custom games on any map. Please let us know what you think of this mode and what changes you'd like to see to it when or if it comes back. Have fun with the mode when it is released, and I look forward to talking with you again about the response and what is coming in December!"
When asked what happens when one of these modes cylces out, he commented:
"When a mode is cycled out it gets removed from both the matchmaking queue and from custom games. We're definitely always oipen to bringing the mode back, but if we left it on in custom games we'd still have to pay that support cost which would slow us down a lot."
When asked why put One of All on Summoner's Rift, he commented:
"You'd be surprised actually, the game works really well on SR. It's also really funny to see people figure out how the hell they're supposed to be an effective jungler with Annie or Ashe. You'll of course still be able to play on HA via the custom game flow if you want."
As for disabling some champions in these featured modes, he commented:
"Well, we've only disabled them in the matchmaking queue - you can still play them in custom games. We did that mostly because Teemo and KArthus are pretty... extreme experiences to play against, and while that's fine in the context of a custom game where you know what you're getting into, it's pretty painful to randomly stumble onto them when you're not expecting it in a matchmaking queue."
When asked what he means by "support costs", he defined them as:
"Nah, you misunderstood what I meant by support costs. What I mean is that with each additional game mode it greatly increases the QA cost and dev time for any change. Especially as our game modes get crazier and crazier the overhead of testing to make sure that a specific skill change or scripting alteration doesn't break a character in every game mode gets higher. Balance is an important concern, but it's actually secondary to the overhead of just making sure things still work."
As for bringing back old modes once they cycle, he commented:
"Bringing a game mode back isn't that high a cost, as long as we don't plan to have multiple game modes accessible within the same patch cycle. Once we get further down the pipe I definitely want to leverage community voting to help us determine what to bring back.
Your game mode also sounds pretty cute. I could see that being fun as a simple SR variant."
Brackhar also commented on the "leak" of One for All mode on to live a while back and how that influenced the direction of the mode:
"Truth be told, before the leak happened we were only planning to support SR for the game mode, and it's the popularity of the mode on HA that pushed us to get the mode working on all of our maps in custom games. I'll be looking at the feedback from you guys pretty closely once the mode is out to see if HA would have been the better choice or not; there's nothing saying we couldn't do the queue on that map next time the mode comes up if that ends up being true.
The point of these modes is to be a bit experimental. Sometimes we may make the wrong choices along the way, but we want to iterate with you guys to get to the right place. That's why we'll keep doing big blog-like posts like this for each of the game modes."
As for the time frame on these modes, he commented:
"Yeap. We wanted to give you guys new game modes on a fairly regular cadence."