League of Legends: Wild Rift Dev Tracker

There is not a way to disable this, however 3's second press does not affect the cool down of the ability itself. It is simply there to help with his combo.

Bit of a sneak peak, but in the next major content patch we are adding this combo tech to Alistair's 2>1 / W>Q so that it functions by pressing 2>2 /W>W, and Jayce's ranged form 1>3 / E>Q so that it functions by pressing 1>1 / Q>Q.

Champion-specific settings and toggles are not something we want to do, it ends up being a rabbit hole where before each game you need to adjust your settings or don't feel like you can play a champion until you have tweaked their own specific setup.

There are situations where players might prefer using an existing setting over another with a champion, but we are not happy when something must be used (Looking at you Riven, and Dash in Move Direction: Off).

I understand that shooting the projectile away from your opponent is a bit odd, but we felt it was worth it to avoid situations where tap casting the ability would basically be trolling yourself if the first cast went toward your target. It can still be aimed in situations where you do want to send the first cast forward, though that will likely be less common.

As for the bug you problem up, this isn't something I have seen, but if you have a clip (ideally showing your screen touch position if possible)...

Sorry I didn't get a chance to look into this today, but yes that sounds like a bug, I'll bring this up to our QA team and we can look into it. If you have a clip send it my way, and I'll include it.

Thanks for bringing this up.

There are risks with any change for sure, but we gotta take risks if we wanta make cool things. Adjustments can, and likely will, be made between now and the ship date (assuming we do ship it).

And thank you for your kind words, I'll pass it along to the rest of the team, it always puts a smile on our faces when we get to hear from players, and our work is appreciated.

Sylas is a bit easier for sure, but they have the same core problem, due to them copying abilities. We want to add them both but need to solve those problems first.

I think both junglers try to hit Smite at the same time has plenty of rng in it already. And the same mitigating factors like zoning the enemy apply to both models. Plus the need to land a basic attack, or ability (if we go that route), plus the fact that CC now locks an opponent out of last hitting the objective, introduces more counterplay.

What do you think is more skillful? The Lee Sin who tries to hit Baron with Q, but you body-block the projectile and he dashes to you anyway then Smites Baron, or the one who dashes to you then needs to hit Baron?

Unless you are talking about the skill check of tracking if your jungler has Smite off CD or not. In that case then I'd say yes this does remove some skill, but I don't think it is one we think is a desirable skill check in Wild Rift. By removing the CD we make it so that players are not trapped by starting Baron/Dragon when their team's Smite is on CD.

Thanks! You're gonna make me all warm and fuzzy inside. I'm glad I can shed some light on a bit of behind the scenes game dev. I'm glad you are enjoying the game.

We would still like to add Veigo and Sylas at some point but for the moment he is still a problem child.

I'm glad you are enjoying Zoe, I have had a similar experience with her in Wild Rift, I played her a lot when she came out on PC but I wouldn't say I was particularly good with her. In our internal tests I have felt she is much easier to pick up... Then I lane against Endstep who destroys me and shows that even with her being easier to pick up I still have a ways to go before I can call myself a good Zoe player.

To be clear it's not about damage in the last few seconds to "mark" the objective for Execution. Smite tiggers in the same instant that you deal damage, so timing is still important. Those timing delays and reaction speeds are still a thing. Timing an attack so that it is the one that reduces Baron to Smite's threshold is the same kind of timing as pressing Smite. Ping is still a factor too, but it's impact is minimized because it doesn't come down to a single press, and instead repeated basic attacks and abilities can all secure it.

I don't have a great answer for you in the scenarios you put forward, I'm not sure how it has been set up. I believe it follows the same rules Smite does right now if Baron is at 50 HP and both junglers hit Smite on the same frame (disgregarding ping). Even in the more realistic scenario you brought up, its still the same situation in the end (Both players Smite at the exact same time, who wins?).

What really ends up happening is that you end up trying to rush down the objective by using all your abilities on CD, or you save your big burst to secure it, not too different from live. And the frame-perfect scenario we are talking about isn't going to come up.

But what would you expect/want to happen in this case? Does it go to the team that started the buff? The team with the most gold? The team who has more players with the letter A in their name? Does each team get half the buff? Should it be 50/50 random?

Because we would never ship champions anything if we waited for things to be perfect. That's a larger take on the question, but and we do explore if we can do a champion before we start working on them. Famously Veigo was a champion we started on but ran into unforeseen constraints that forced us to put him in the ice box.

More seriously to your point though, we don't always know what is needed for a champion when we start working on them. Particularly the kinds of things that come from working on a champion and after having played them a bit. Things like Lillia and Zoe's third abilities (E) drawing a line on the mini-map were not things we thought of when we started on the champions, but that we discovered would be good to have through playtesting. Lillia's R showing the number of enemy champions that it would affect didn't show up until very late in her development.

Other times something ends up being easier than we thought, or even more difficult, may...

It sounds like there is some confusion on how it works. This does not remove the timing requirement of Smite, you still need to deal non-DoT damage to the objective (we are experimenting with if this should include ability damage or just basic attacks). If your damage reduces the Large/Epic monster's HP below Smite's threshold it will execute it.

So if you have 2 champions fighting at Baron, and not damaging it, then neither will take the objective. However, if both are fighting Baron, the jungler who secures the objective is the one who brought Baron to the execute threshold. Just like on live the jungler who secures the objective is the one who last hit it.

Another part of this is that Smite doesn't have a cooldown, so this applies to every large/epic monster, and you no longer need to worry about using your Smite during the pre-Baron fight, on RedBuff before the fight, or to secure Baron. Or if you are not the jungler, you don't need to worry about if your jung...