Red Post Collection: 5/27 Nautilus Hotfixes, Quick Gameplay Thoughts: May 28, & More

Posted on at 11:14 AM by Aznbeat
Today's red post collection includes a small set of Nautilus hotfixes, Riot Scruffy's quick gameplay thoughts for May 28, a look at some tech behind Dr. Mundo from Riot Nyanbun, and more!
Continue reading for more information!

Table of Contents


5/27 Mid-Patch Updates

Check out the details on Nautilus hotfixes for 5/27:
"5/27/2021 Nautilus Bugfixes
Nautilus
  • W - TITAN'S WRATH AP RATIO BUGFIX Fixed Nautilus' W - Titan's Wrath AP ratio to its intended value (40%)
  • E - RIPTIDE SLOW BUGFIX Fixed Nautilus' E - Riptide slow to its intended value (30%)

Quick Gameplay Thoughts: May 28

Here's Riot Scruffy's quick gameplay thoughts for May 18 - "Mobility Reduction and Philosophy."
"Mobility Philosophy 
Mobility is one of the fundamental building blocks of League combat, as both an exciting and necessary tool to keep other players at range, or close in as a melee. There are places where mobility has been crept up, including a few items that have gone beyond the limits of where they should be. I wanted to walk through some of our higher level philosophies around mobility while we’re working on a trimming pass to bring the live game closer to our ideal. 
Great uses of mobility:
  • Mobility paired with weaknesses - lower range, lower damage, lower defenses. This makes the champion with mobility have to use its “fight choosing” power effectively because they won't necessarily win a face to face 1on1 against a less mobile champion.
  • Systemic mobility with a clear opportunity cost - Like the previous, when adding systemic mobility through items or runes it should be a significant tradeoff against the other options that offer more of the other attributes your champion wants.
  • Mobility with constraints - Extreme high mobility can be offered in a healthy way if it comes with situational constraints. Only allowing the mobility pop off through risky, aggressive, or contextual use allows players playing as and against to build strategies before and during fights. Good examples here are Irelia Q vs minions, Tristana W reset and *gasp* Yasuo E. A bad example we removed was Akali's R1 originally being untargeted giving her incredible engage and escape power simultaneously.
  • Very long cooldowns for systemic mobility - By adding extremely long cooldowns, we can actually break class weaknesses with systemic mobility. If the opportunity to go beyond what is normal is a rare and precious action, it adds strategy, excitement, and a way for players to break the normal flow of combat a few times a game. The best and only example here is Flash.
Poor uses of mobility:
  • Systemic mobility that breaks class weakness - Some classes (like Juggernauts) are built with exceptional strengths around their lack of mobility. Offering them too much mobility via runes or items can break both the expectations of players in the game and the intended weaknesses of the class. This doesn’t mean they can never be offered mobility, it just has to be done with extra care. Systemic mobility in particular is an area we pushed too far with the item update and its followup, and our trimming pass will focus on this space.
  • Mobility tuning that creeps beyond the game norms - we have established ranges, movement speeds, dash ranges, and dash speeds across champions and items. It would be a problem if the mobility tools of new champs or items are always just slightly stronger than the mobility tools of existing champs and items because that cheating compounds over time and significantly shifts the average mobility in the game.
  • Too much unconstrained mobility - Both low cooldowns and freedom of targeting can make mobility an overly powerful tool with no good answer for opponents. If a champion can always choose when to be in and out of fights, they never have to take risks or commit to an all in. The closest we get to this is probably a level 16 Kassadin, but in that case he has to survive a disadvantaged early game to reach that level of mobility.
How did we get here? It’s necessary to push and test the limits of the game to find great improvements, but that does mean that sometimes we will go too far and need to pull back. So we’re working on a few changes to trim down on small instances of mobility creep and a few larger ones where we think we pushed too far in terms of breaking class weaknesses. Look for those in a few patches. Thanks again for playing with us."

 

Miscellaneous

"Now that Dr. Mundo has been on PBE for a hot sec, let’s talk tech!  
For his rework I identified two potential bodies of work: 1. “Goes where he pleases” passive and 2. Ult transform 
The passive CC Immunity represented an opportunity to unify the way we approach CC from the game engine perspective. I took the liberty while we were still months out from preprod to do a deep dive on CC and came up w some interesting results
Most times CCs like charm call into raw lua routines that take control of units’ AI state and dictates their behavior. The way CC is applied was confusing for designers as well, since there were a hodgepodge of scripts that had very similar names but did different things.
I began by removing the confusion for designers in Charm’s case—you might remember the weird charm bugs back in July that was my tinkeringšŸ˜… This was proof of concept for other CCs like Taunt and Stun. It also set us up to convert the raw lua into C++ down the line. 
What did all this have to do with Mundo? Going back to his CC immunity, it made knowing how to prevent CC from being applied a lot easier from script, while also setting the foundation for engine-controlled types of CC as well as CC Immunity. 
Another thing I custom made for Mundo passive was the randomness logic for his canister drop—other types of “drop a thing randomly here” didn’t really exist prior or is pseudo random. For example Poppy’s shield is actually just 2 possibilities that’s a coin flip. 
I later had to fix some bugs that had the canister landing in terrain. Which I learned the hard way was why random drop logic wasn’t done earlier. Trying to probe every possibility was computationally expensive and there’s a balance between game feel and mathematic perfection"
  • Riot Sirhaian posted a thread on making PROJECT: Mordekaiser's ult City background:

Other Games


Wild Rift
"Hey again! Mike “RogueFool” Breese here ready to chat about the upcoming Patch 2.3 rune update. In our last post, we mentioned that we were going to be updating Wild Rift’s runes so that each rune has clear strengths and weaknesses."


[Back to Top]

No comments

Post a Comment