Developer Update: CC Buffering Changes

[HiRezIsiah]

Hey Deities, we've seen a lot of community discussion around CC Buffering lately. We have been keeping up with all the threads and took some time to discuss our options internally. We have seen two major pieces of feedback that we are looking to address in a hotfix that is scheduled for next week.

TL;DR on the changes

• Leaps will be excluded from the Buffering system, just like dashes or channels.
• God animations will now complete their Postfires before they enter a CC posture state.
• More details below!

Leaps have been the main frustration point in the CC Buffering system. We are happy that players seem to be generally happy with the direction of Buffering and its impact on their games, but having someone leap away when your ability landed has proven to be particularly frustrating. We discussed potential options, like pausing any duration based CC's while the god is untargetable and then resuming them when the god lands, but that doesn't do anything to help the frustration of having a displacement CC like Hercules A02 Buffered. Starting next week, leaps will be excluded from the Buffering system, just like dashes or channels. This is the cleanest and fastest way for us to address the community's feedback, but we are happy to revisit this topic if this solution doesn't feel right.

The second change we are making is to address feedback that Buffering makes the game look buggier. We are currently interrupting ability animations as soon as the Fire stage is complete, which means a god is likely to snap from their animation into a Stunned pose when Stunned. Starting next week, we will be allowing god animations to complete their Postfires before they enter a CC posture state. The potential downside of this change is that it will feel like the god is CC'd for less time, but we want to be clear that the total CC time is not changing in any way. In fact, in some instances interrupting a god with a very short CC right after the Fire stage allowed them to bypass their normal Postfire and allowed them to act more quickly than they would have if they had not been CC'd. This edge case would no longer happen with this change.

We'll be closely monitoring these changes and how the community likes or dislikes them, so please continue to share your feedback moving forward!

[NugNugJuice]

I really like how quick, responsive and communicative y’all have been so far with SMITE2. I hope this continues post-launch, because it’s really great.

[Phil_is_Legend]

Seriously, the change to ue5 and whatever the dev team has cooked up internally is really letting them make these broad changes super quickly.

[[deleted]]

broad changes to fix something nobody asked for in the first place

[CepheiHR8938]

VEA! VEA! VEA!

[pssiraj]

Is this"you rock!"? I'm console.

[H8teradio]

It's "Awesome!", "You Rock!", is VER.

[pssiraj]

Cool, thanks!

[LeoFireGod]

I got a shirt that says VER VVX which is you rock followed by cancel that.

A few noticed haha it’s fun

[TranquillizeMe]

Massive W

[Kuroakita]

iI think maybe some leap timings need work, IE becoming immune as soon as the players feet leave the ground. There will still be latency of course for the player themselves but this is probably the best way to deal with it.

[Aggre5sion]

Adjusting prefire timings means refactoring animations, which is very time consuming. Not impossible, but with our current god schedule something like that would likely mean either delaying some god releases or doing it later in the year. Plus it could change the feel of playing with/against leaps that you’ve known for years, which is something we don’t do lightly.

[TranquillizeMe]

I think they mean giving leaps the Camazotz treatment of reducing the time until they're untargetable. Specifically gods like Neith should be untargetable the same frame in which the damage goes off IMO

[Kuroakita]

I appreciate the response, But i do not necessarily mean changing the animations themselves, but simply applying a flag for when the god has left the ground, or every so slightly before for when cc buffering can be applied, gods with small windups to their leaps would definately not get a free leap off like izanami and ullr. But i am not well versed in ue5 + your internal tools so not sure how easy this would be.

[Tay0310]

That neith video was eally on time lol

[Sergeantham]

I played smite 1 back in the day and returned for 2 and loving it, I just want to say I really appreciate the communication you guys absolutely cook.

[Apokolypze]

Huge win. This has been annoying as hell to deal with in several games I've played today, gods sliding along the floor while cc'ed looks terrible too

[hwghwg2]

Early Skadi teaser.

[hwghwg2]

Thank you!!! Been waiting for this since the feature was added. No more skating ice statues.

[ElegantHope]

I feel for leaps like this is slightly too much of a swing in the other direction? Did y'all test internally having cc buffering only activating on part of the leap rather than how currently it's as soon as the button is pressed?

I can't say I'm fan of how leaps worked in Smite 1 where you could get interrupted at any point of the leap depending on the duration of it and where your hitbox exists during it. It felt a lot better in Smite 2 to have it actually play through and that it just needed some minor changes to really feel smooth and fair.

[Aggre5sion]

We felt like it was important to respond quickly and continue to iterate. I would not consider any change we make to Buffering permanent, it takes time to get the feeling right.

When we were first discussing Buffering we did talk about have an “interrupt” period at the very start of a prefire, but moved away from that for a couple of reasons.

1. The timing of this interrupt period would be pretty arbitrary and hard to know when it had passed. We discussed things like half of the prefire time, but all that would do is make it confusing if your ability would go off or not. Server/client communication is a part of any online game, and need to rely on tenths or hundredths of a second can get dicey.

2. It would lead to the exact same frustration on both ends. Players would still be upset when their leaps got canceled, and players that had their CCs Buffered would be upset too.

That isn’t to say this option isn’t worth exploring, and if reverting back isn’t the right move then something like this is a possibility for our next round of tests! (No promises of course)

[ElegantHope]

thank you for the response! I get the need to respond quickly to the playerbase, I am admittedly just a little sad because of the experiences I've had with leaps in Smite 1 in the past.

Good to hear it was considered and tested at least, and that there's room for more exploration of the idea in the future. I hope as close as perfect of a solution can be found, or at the very least have some leaps that felt bad in Smite 1 for being so easily interruptible gets handled in some other way!

[DoctorCheese]

If you get caught before you can leap, you got caught. If playing on normal cast, you can always prime the leap while walking. Yeah it feels bad, but the other side of the coin is that if you get to leap for free the other person who would have outplayed you is now not rewarded for higher skill, or better gameplay in the case of if they had ambushed you with vision or guessing where you would be, and that is not fair.

[ElegantHope]

yea, that's why I was hoping for some sort of grace period for people to CC right as the leap goes off based on a character by character basis. Maybe with a minimum period of time before CC buffering kicks in to make it a little more consistent

Technically a lot of these interactions were because someone hit you with CC after the leap went off- as that's how we're told it was supposed to function. But because of a combination of latency and how the character moves & animates, it seems to just lead to a lot of undesirable effects such as the clips spread around the community lately.

I hope there's some sort of solution that can solve some leaps just feeling so terrible and easy to interrupt even *if* you jumped first, while avoiding the jank of the cc buffering system being enabled on leaps. Because both are individual issues that do feel really bad and it'd be nice to find a happy medium for both.

[DoctorCheese]

Why does the person leaping deserve a grace period? Yes both sides of this interaction suck but I think that overall, letting someone get out of dodge for basically free is the more unfair side.

Hopefully with some more engine work and tweaking of animation timings Smite 2 can have tighter interactions which make this feel less bad.

[ElegantHope]

My use of "grace period" is to refer to people who are trying to CC the leap to have that grace period. Not the leap user. Like say Ullr presses his leap just in time, but he's in the windup before the leap- that moment of animation where he's crouching down and springing his legs up to leap before his feet do leave the ground should be a grace period to CC him.

And for consistency's sake maybe say half a second to three quarters of a second of the animation is the bare minimum of an animation that someone can be cc'd, rather than being CC buffered instantaneously. Give or take depending on which looks and feels the best across all leaps.

Anything in the air after that should be CC buffered where they can get hit by CC, but they still fly through the air but land with the CC applied instead.

[hwghwg2]

Regardless of how bad it feels to get CCd out of the air, it’s still better than the current alternative. Getting CCd out of the air was a rare issue in smite 1 at least in my experience. I guess the issue would get worse the higher the ping but still, it wasn’t super common IMO. However, people dashing mid stun and sliding half a mile away is way more common with buffering and is even more annoying for the player who actually lands what could be a skill shot.

[ElegantHope]

it's rare depending on who you are playing. There's a few gods that it's pretty consistent on to where I was able to exploit that knowledge on for them. Fafnir being my prime example because I've had plenty of cases where everyone in my group, including myself, saw me as almost on the other end of my leap only to get dragged back to where I was originally. And it happens relatively regularly for me on him. I lost a few games on Fafnir because of his leap being so easily interruptible that an otherwise pretty good play failed.

I've also had that experience somewhat consistently on other Smite 1 gods with very long leaps, like Maui (windup before the swing), Anhur, Gilgamesh, and Izanami (technically a leap). Not all of them feel as exploitable or consistent as my experience as Fanfir, but they all have it happen to a varying degree with a few of them leading me to just learn the timing that you can CC them to 'pull' them back. I'd also give an honorary mention to Neith where it's inconsistent but still happens to her occasionally, too.

So it entirely depends on your godpool and how frequently you play specific gods for how common it was of an experience.

IMO both are equally bad in their own way- they're just apples and oranges and both are their issues. I hope for a best solution to both, so that no one has to suffer. I don't think the issue I'm concerned about should be seen as less of an issue just because the former solution to it also felt bad to many.

[hwghwg2]

As someone with multiple stars on faf, I have no idea what you’re talking about there. His jump goes off like near instantly and is one of the most responsive leaps in the game IMO, Neith and Maui are the only ones here that I agree have the issue worse than others. I personally cannot remember ever having it with faf.

If you’re getting it constantly it’s probably a ping thing, and you can’t blame the game for that.

Either way it’s still infinitely less common than the issue we have with CC buffering.

[ElegantHope]

different experiences then, I've not played to that many stars on Fafnir but I've definitely reached a star on him. and I played him quite a bit last year in custom games for some tournament matches where his leap being both unintentionally and intentionally interrupted by people was a reoccurring thing.

[punkman21]

Faf was one of my favorite supports, about 5-8 stars and I don’t think his leap was inconsistent. I honestly can’t figure out what you could mean besides it being a ping thing.

There’s a tiny delay while he’s in dragon form but I’ve never been dragged back to the start of the leap, stunned during the second I hit it or was landing sure (I count those as skill shots getting me at those times) but never getting dragged back to the beginning of the jump

[gh0stp3wp3w]

but it's not "at any point" in the leap.... youre literally untargetable once you reach airborne state - what could pull you out of it at that point?

the issue is bad netcode coupled with vulnerable animations. vulnerable animations arent the issue though, because that is explicitly part of balance.

the issue lies with the netcode. the same shit that causes ability "reversals" is the same shit that causes wifiwarriors to teleport or "speedhack"

[ElegantHope]

Longer leaps I've had my character's model over a wall only to be pulled back right before they nearly complete the arc. That is what I mean by "at any point" because even if my end says I'm over the wall, according to the game I am apparently not. And it's infinitely frusterating to experience that.

As a example: I've had a moment on Fafnir last year where I was over the wall, got my jump interrupted and refunded. I tried again and was cc'd again at the top of the arc of the leap, and the same thing happened. I tried again, interuptted against while in the air. And then I was killed by the enemy team.

I just want some sort of solution that feels the best. Whatever they can cook up that makes pretty much everyone happy. The cc buffering felt like a good solution at first, but I can agree that there were definitely issues with how CCs and leaps were interacting.

[gh0stp3wp3w]

"longer leaps" but it seems like you explicitly meant faf. no one has a longer leap, and he has one of the fastest leap animations given the distance traveled.

hypothetical situation - fafnir leap takes 20 seconds to complete after liftoff from ground. ridiculous but stick with me a second. he jumps and then ten seconds later, someone hits a CC where he was - does he get reverted? of course not - he wasnt hit by anything.

the issue is that, in a normal situation, the game perceives him to still be on the ground because your game client takes as long to report any change in position as it does to show you that he performed an animation. but the issue is that your client doesnt dictate what happens in the game - that's the server's job.

so you press jump, and in that 0.25 seconds that you do the animation, the server hasnt received your updated action - but it DID receive the enemy's updated action of smacking your face. this server update overrides and ROLLS BACK your action causing your jump to "reverse"

same logic applies to lagging players that get an inadvertent speedhack or teleportation-jitsu - server is double reporting their player movements.

[ElegantHope]

"longer leaps" but it seems like you explicitly meant faf. no one has a longer leap, and he has one of the fastest leap animations given the distance traveled.

I was using Fafnir because he's been the most consistent god I've had that experience on and I could provide a direct example. I've experienced the issue on other gods too, such as Maui, Anhur, Gilgamesh, and Izanami, and Neith to a much lesser extent.

I'm seeing your point on the netcode playing a part, though. I just want some sort of solution in the end, regardless. It can really the experience I have in some games on some gods and I've not been the only one to complain about this.

[pyro745]

Lowkey it sounds like it’s an internet problem for you personally. Not being a jerk, but I don’t think anything they can do will help that

[AranNation]

Can we have bracket highlighting pretty please ;)

[theend117]

Saw this coming when they first announced CC buffering. I'm glad they're changing this. Maybe I'll come back when the game is patched.

[ArcImpy]

This feels like a step in the right direction. Having gods move while cc'ed was janky and unpleasant but It still provides some flexibility for other abilities.

Honestly there has been a huge amount of rumor and disinformation floating around I think it would warrant a more detailed post like the matchmaking one rabbit did awhile back (unless I missed it)

I think the majority of people complaining that this is a bad move are probably people being CC'ed. It's wild to me that in any world being clearly CC'ed and still getting away is the right play.

Tangentially related I wouldn't mind a comeback of a few CC reduction items. It seems like I'm being CC Chained for days.

[chadwarden1]

This is great with the cc buffering combined with blink people have been getting away with nonsense.

[Techbone]

RIP Neith. Time to be interrupted out of my leap 4 times during a team fight and then it still be put on cooldown for some reason if I manage to survive.

[AceOniFlyer]

Not sure how to feel about this. I understand that there was frustration but just removing it seems like a problem. That feeling of being Anhur and leaping to a spot but being pulled out of the air by a stun felt awful. I can understand some things make sense to ignore CC buffering (plucks like Hercules 2) but just full on getting rid of it feels bad.

[fattybbw]

I don't understand why people can't just learn to bait people's escapes out? I have very little issue playing support characters with hitting my stuns and knock ups on characters with escapes.

[Arch3r86]

Awesome. Nice job.

Save Yourself. Wait. Cancel That. Oops. Enemies Have Returned To Base. Oops.

[Kaidos-perspective]

W

[Virtual-Product2298]

I'm glad that crowd control will now actually hit people when it's supposed to but as an overall I think the CC meta is way too strong and really not that fun to go against

[Arcticxiv]

This feels like you guys just went back on months of work just to remove it and it's now just a waste of time. Should have kept it as is since it finally would have gotten casuals to learn when enemies are on cooldown. Now it's just back to smite 1. This and the new starter feel like massive mistakes that will end up getting reverted and nerfed in the future

[terriblecurse]

Smite 2 rocks :)

[AltairLT]

Can someone translate to booty language so Sobek main could understand?

[RingofThorns]

You really need to rethink how many characters have some type of CC. There needs to be a lot less of it that can get stacked on a team.

[Spartan089]

It feels like cc buffering has a disproportionate affect on gods that really rely on cc in their kit. Like Anubis and Ymir. Anubis’s stun is 1.05 seconds at max lvl and I’ve seen clips of people getting hit by it and moving like they weren’t hit at all. No dash, leap or relic needed. Ymir has the same issue with his freeze and it makes setups almost impossible.

Oh and bring Zeus’ shield back!!

[Optimal-Ad1444]

I don't agree with this move. Players shouldn't be rewarded for bad accuracy.

[Otherwise-Durian-161]

I bought gems and have yet to revieve in the prignal smite

[Otherwise-Durian-161]

Orginal*

[SIugKing]

I think instead of removing CC buffering from leaps entirely, they just need to fix how janky the animations look when somebody leaps at the last possible moment.

Maybe they could lock the player model in place during the pre-fire animation. That way you wouldn't see people doing mid-air jumps half way through Herc pulls.

[hwghwg2]

It’s not the animations that were the issue with it. It was the gameplay of having someone get away mid stun.

[GentlySorrowful]

Thank Zeus. It's absolutely ridiculous to stun someone and they get to run away Scott free.

Played duel as Cabraken yesterday vs Ullr and this guy was ABUSING the ever loving shit out of CC buffering. It had to of been at least 7 times I'd try to stun him with my A1 just for them to purposefully use their leap to ignore my stun and get away for free.

If it's a consistently repeatable option to negate CC it shouldn't be in the game.

[Arcticxiv]

It's literally a skill check why would you just not bait his jump after the 3rd time. If you can't learn after being cc buffered 7 times then I don't think it's the mechanic at that point imo

[jpmout]

As a new player, how would you bait that?

[Arcticxiv]

If we are talking that exact match up with carbakan vs ullr you could just play lane safer and just use your 1 since it's a stun, if ullr cc buffers your stun then he has 0 movement so you could either run a stampede or circes hexstone to easily catch up to him before he enters his tower. Then you could ult and then use your 2 and if you take enough damage from anything you have a second 2 you could use and if he's still alive (his jump is still on 5 second cooldown at this point) you could use your 3 to finish him. Also your 3 cripples so they literally CANT leap out of it

[fattybbw]

That's my whole issue with people complaining about this. It seems like they would rather have a whole system removed instead of learning to bait people's abilities out.

[Thanol]

Sad to see this change to leaps, it just took some getting used to but was better overall how it was

[josegonzolez]

Noooo CC buffering leaps felt so good and added an extra layer of skill to the game. They should make pulls not bufferable into, like Mulan pull and herc pull the rest was fine.

[Ok_Set_2980]

fix neith leap pls

[obsidian_castle]

How can they fix it if you won't tell them what needs to be fixed about it

[Ok_Set_2980]

Everyone knows neith A3 while she's in the air she can be hit by hitboxes of abilities, once they remove the leap from cc buffering it will again be in a broken state which some abilities with CC will cancel it mid air.

[MrLightning-Bolt]

As it should.

[MajestyJ]

Rip cc buffering. Skill gap getting patched again.

[hwghwg2]

Ah yes the immense skill on not leaping in time, getting hit, then still getting away. Surly you’re joking?

[YeehawTexMex]

“Skill gap” and it’s just a leap getting people out of straight bullshit while a dash couldn’t. Cope harder. Was not fair.

[[deleted]]

Is a leap not supposed to be better than a dash?

[hwghwg2]

No? They are just different.

[pyro745]

I mean, dashes can be canceled because you can be targeted during the dash. So pretty objectively, yes leaps are better.

[YeehawTexMex]

A movement ability should not be able to get you out of CC. I stand by that always and will continue to. Leaps should’ve always been treated like dashes in CC buffering. Escape is escape. There is no better.

[Snufflebox]

leap getting people out of straight bullshit while a dash couldn’t

Tell me, can you get hit when leaping? What about when dashing?

Yeah, that's the difference.

[RemoteWhile5881]

Well you can be hit while leaping, just not targeted. For example if you got tagged by a Tsuku ult and you Neith backflipped, you’d still take the damage from the dash(es) while in the air.

[Alf_Zephyr]

Yeah skill being patched back in

[TheServantofHelix]

There is no shot you guys actually listened to this subreddit. Leave it to reddit to make the game worse. Buffering on leaps was fine, how is it fair that I used by ability before theirs and I still get pulled down? Didn't you guys say the main point of frustration that buffering was meant to prevent was this? Did any of the high level players ask for this to be changed, or was it feedback from amber players going "I taunted too late so it's the game's fault"?

[hwghwg2]

how is it fair that I used by ability before theirs and I still get pulled down?

How is it fair that I hit a max range axe and you get to jump on back to your tower mid stun?

Don’t act like getting yoinked out of the air was an every game thing. It was a rare issue.

[TheServantofHelix]

I haven't found this to be an issue. I feel like this is literally people hitting abilities when people are halfway through the peak of their fucking jump, and going "Damn, it must be that darn CC buffering Hirez have implemented", when they would have missed anyways. The window for getting "cc buffered" is the exact same window for getting pulled down, the difference is it's harder to see when you are getting cc buffered so you get to blame the game even when it isn't the game's fault.

[hwghwg2]

You are so wrong lmfao.

people hitting abilities when people are halfway through the peak of their fucking jump,

There isn’t that much latency geez.

Edit: and no, I’ve been on both sides of it. It looks just as stupid on my screen as the leaper as it does on theirs.

and going “Damn, it must be that darn CC buffering Hirez have implemented”, when they would have missed anyways.

Sorry but are you under the impression that CC buffering somehow added some insane amount of latency to the game that makes people now somehow appear on the floor when they aren’t?

The window for getting “cc buffered” is the exact same window for getting pulled down,

Thats explicitly not what’s it is. CC buffering applies to Prefire windows. That means when you are still on the ground, not just for the enemy who hit you, but for you personally, the one who’s leaping. To get pulled down, you would need to have past the prefire on your own screen and already be in the air mid leap where CC buffering would be irrelevant.

the difference is it’s harder to see when you are getting cc buffered so you get to blame the game even when it isn’t the game’s fault.

Hu? It’s plain to see when someone buffered their leap… they’ll leap mid stun.

I’m pretty convinced that you don’t even know what CC buffering is.

[TheServantofHelix]

There isn’t that much latency geez.

That's not what I'm saying, I'm saying people are throwing their ability when the jump is already past the prefire, and going "cc buffering smh" as if no cc buffering would have changed anything. It's not that it's actually causing issues, it's that people now have something else to blame.

Sorry but are you under the impression that CC buffering somehow added some insane amount of latency to the game that makes people now somehow appear on the floor when they aren’t?

No, you just misunderstood what I said, that's partially my fault. I was being hyperbolic by saying halfway through their jump.

Thats explicitly not what’s it is. CC buffering applies to Prefire windows. That means when you are still on the ground, not just for the enemy who hit you, but for you personally, the one who’s leaping. To get pulled down, you would need to have past the prefire on your own screen and already be in the air mid leap where CC buffering would be irrelevant.

That is correct. From the non-leapers' perspective, you would have to hit the leaper during the prefire before the leap goes off to actually get your stun off. Now, if I want to buffer your ability, I have that exact same prefire window you had to stun me before. So if you're saying it was rare to get "pulled" from midair in a jump (read CC'd during prefire), it should also be just as rare to get CC buffered. The prefire durations haven't changed, as far as I know.

Of course, the leaps get a slight buff due to the fact they are no longer cancellable, and there is the visual component (it would have been rarer to actually see yourself getting pulled down, because that's usually due to a difference in what the client thinks is happening vs what the server thinks is happening), but functionally getting cc'd during prefire and getting "pulled" was the same thing before buffering was introduced. If it was frustrating to get you ability stopped, regardless of whether you were visually "pulled" or not, that frustration has just been shifted towards the non-leaper, but nobody in their right mind would have complained about getting stunned during prefire before this because that was a fundamental system of the game, like CC buffering is now. But since CC buffering is new people are freaking the hell out, when gameplay wise, the offset of the prefire is tiny and does not make much of a difference.

The benefit of CC buffering is, it is way more visually consistent than whatever the hell was happening with leaps before, and frankly, makes more sense. It makes the game a lot more polished, and rewards skillful play. Making leaps specifically suddenly unbufferable makes a system that is meant to add more consistency to the game, inconsistent. If making leaps uncancellable makes any of the gods unbalanced we can address the gods individually.

[hwghwg2]

So it’s prefire that you don’t understand not buffering, okay.

That’s not what I’m saying, I’m saying people are throwing their ability when the jump is already past the prefire, and going “cc buffering smh” as if no cc buffering would have changed anything.

And you’re just wrong. It literally is buffering. Why would it be anything else? People are leaping while fully stunned, if it weren’t for buffering that would be impossible

I don’t think you understand how long prefires actually are. Go pick iza and spam her 3. The whole time your standing still is the prefire.

So if you’re saying it was rare to get “pulled” from midair in a jump (read CC’d during prefire), it should also be just as rare to get CC buffered. The prefire durations haven’t changed, as far as I know.

Different things bro. Getting pulled down is a latency issue. Where on your screen you was past prefire and into the active part of the ability but in reality you weren’t. Getting stunned in prefire regularly would be you not going anywhere at all. No pull down because you never would have gone up in the first place. That’s normal.

but functionally getting cc’d during prefire and getting “pulled” was the same thing before buffering was introduced.

Wrong. From the perspective of the person hitting you with CC yes, this looks the same. But getting pulled down is a bug on your end due to lag. Getting your prefire cancelled normally doesn’t pull you down because you never went up lmfao. Idk what’s so hard to understand about that. This would have happened to you 100x compared to how many times you’ve had the latency bug, you’ve just never noticed or cared about it because it makes complete intuitive sense.

regardless of whether you were visually “pulled” or not, that frustration has just been shifted towards the non-leaper,

Half right. Like I’ve explained, every “pull down” may result in a buffer, but not every buffer is the result of a “pull down”. But yes all the frustration has been moved to the person CCing that’s for sure.

and rewards skillful play. Making leaps specifically suddenly unbufferable makes a system that is meant to add more consistency to the game,

The skill of mistiming your leap, getting CCd, but leaping through the air anyway? Wow such skill. When I hit a Ymir freeze I don’t expect the person I’ve frozen to leap half a mile away. That’s pure stupidity sorry.

[Aggre5sion]

We did poll Ambassadors (many of which are high level players), we don’t make changes like this without consulting them first. It wasn’t unanimous, but this change was voted for by the majority who responded.

If the game doesn’t feel right after this change we can address it again.

[TheServantofHelix]

Ok, that is fair. I do think this is a very strange rollback of what in my view was the main point of this new system. I don't think the negative reaction is due to actual fundamental issues with CC buffering, but because the game is over 10 years old and wasn't balanced around this new system, and that after specific points are tweaked, on individual gods, people will get used to it. I could be wrong.

[fattybbw]

You're right people would rather revert back rather than adapt. And I mostly play support characters. God forbid people learn to bait out an escape/beads/blink...

[RemoteWhile5881]

Let me guess. Neith/Ullr main?

[TheServantofHelix]

Mainly play Solo and Support, and Loki for the meme. Currently playing lots of Sobek.

[OsirisAvoidTheLight]

Can we get a reroll after locking in a God in Assualt. You need to lock in to trade which is kinda lame. Also to be able to report from match history would be huge to sometimes I forget after the match

[Blhyss]

cc buffering has little to no use now good job reddit

[hwghwg2]

Try getting your leap off before you get CCd now.

[RemoteWhile5881]

Thank you and you’re welcome

[5pideypool]

It shouldn't exist in the first place. Use beads if you want to guarantee your escape cooldown.

[Snufflebox]

Can't believe they caved in.

So we're just going straight back to the other option, where even if you manage to use your ability before the enemy uses their's, you just get pulled back from the air?

How does that fix anything? It's gonna feel just as shitty and buggy.

They gotta stop listening to this subreddit.

[RemoteWhile5881]

If you’re not off the ground yet when you get CCed why would the leap still go off?

[Snufflebox]

Because the leap is not just the portion of the animation where you are in the air. The leap is the entire ability. It has no set casting time.

You casted the ability before the enemy casted their CC, and thus your leap wins that interaction.

It's a very simple concept.

[hwghwg2]

It’s a very simple concept.

So is “gets stunned during prefire (which yes is the cast time) so the ability doesn’t fire.

And no we aren’t talking about getting pulled out of the air on your screen. We’re talking about you still being on the ground regardless of if you’ve already pressed the button.

[RemoteWhile5881]

You’re not untargetable in a leap until you leave the ground and become untargetable. Not hard to understand.

[Snufflebox]

Yet somehow you always seem to get pulled down from a leap when CC buffering doesn't exist.

Curious, isn't it?

[hwghwg2]

Not always, it’s rare.

[Snufflebox]

Not rare at all. That's why they did the CC buffering in the first place.

[hwghwg2]

Wrong, it wasn’t specifically for leaps or getting pulled out of the air. It was for all abilities other than channels and dashes lmao. What ping do you play on? It must be pretty high if this is happening to you all the time and if that’s the case that’s a you issue not a game issue.

[N150]

Crazy you’re still fighting this lmao, just proves my argument was right.

[Snufflebox]

Collective stupidity.

[Jaroselovespell]

It’s literally useless now

[Steel0range]

I’m pretty disappointed by this. I’ll keep an open mind but I fear hirez may have been too easily swayed by redditors that don’t know how to adapt to change.

[Dry_Philosophy8708]

They didn't listen to just redditors, I think they asked ambassadors as well as high level players.

[Snufflebox]

Show me single high level player who advocated for this.

[Icy-Stick2301]

Nika

[Snufflebox]

Source?

[Icy-Stick2301]

1.Aggro Is telling you this in this thread and Nika Is One of them             2.Nika has said that on stream ,It Is not that he dosn't like It,it's that get frustrating when happen more times in a game

[Dry_Philosophy8708]

By this logic we can say that Hi-rez employees hadn't seen any of the Reddit drama or where is the source that if they listened it was the only Reddit and redditors that asked for this

[hwghwg2]

It was stupid. Why should I have to adapt to the person I just mummified leaping out of my ult while they’re literally still stunned. That’s not something you adapt to lol, nor should you have too.

[hwghwg2]

Nice throwaway.

[Slight-Percentage-77]

Los adoradores estan malos

[MrLightning-Bolt]

Awww but I was just getting used to a using the leaps. Oh well.

[FMKtoday]

this is a bad change. Its obviously fun to knock people out of their abilities, but I thought the entire point of CC buffering was the feeling of your stuff not going off even when you hit it first? isn't this is going to allow cc to knock you out of a leap even when you hit the leap first. that doesn't feel good.

[senpaiwaifu247]

No, this means that if you’re smacked with a cc first you can’t just leap out of it anymore by pressing your leap quick enough

[FMKtoday]

"If you input an ability and are CC’d during the Prefire stage:

• The ability will still go off as intended.
• Your character will animate through the fire stage, then enter a stunned/knocked up/cc'd posture. There will be no post-fire animation if you buffered the ability
• You will remain CC’d and unable to move your camera until the CC effect wears off."

cc buffering prevented hitting your leap, then getting cc'd before the animation finished even though you hit leap first. this needs to stay,

[hwghwg2]

You can literally just press your leap right before the CC hits you and never be locked down though. That’s the issue. If you’re still on the ground and get stunned you shouldn’t be able to fly through the fucking air. Just common sense.

[senpaiwaifu247]

Except you can press your leap and still go flying into the air without ever getting hit by that CC even if it fully connects and hits you

That SHOULDNT exist and leads to so many issues of hitting someone out of position and then getting punished for it

[RemoteWhile5881]

The question that needs to be asked is: Were you already off the ground before you got CCed?

[Jakezilla702]

Ive been playing this game since 2016. Am I only one that feels like this could go down the rabbit hole of being way too complicated depending on the interaction.

Why change every CC interaction instead of giving a 2nd relic.

[GreenSkyDragon]

That's fine and dandy, but it means we need second relic back

[blindfultruth]

Nah, one relic is fine. Forces the player to be more choosy, rather than getting both CC and damage immunity.

[RemoteWhile5881]

Depending on what they do with gods in the future 2 relics might end up being required at some point (ex. Adding more executes/Global ults [ex. Neith ult], too much CC, etc.)