R0gueFool

The Short answer, is that it makes room for new items.

Each item we add makes navigating the shop more complex. If we have 50 AP items, that is a lot of scrolling to find the one you are looking for.

We don't feel that having 2 magic vamp items is healthy for the game, in a world where Gunblade wasn't bad, seeing Akali with Gunblade and Riftmaker is a lot of healing for any champion.

As for Gunblade itself, we have wanted to remove it for a while. It has never been worth buying because its gameplay isn't particularly healthy either, easy burst+slow isn't great. Even if it was healthy, its duel AD+AP also gave it a VERY small champion pool.

We wanted to release it at the same time as, or before Gwen. But we have been wanting to remove Gunblade for a while, and replace it with Riftmaker.

I'm not telling ChartNew3237, I'm telling whoever else reads this that isn't ChartNew3237, but Yuumi is a popular champion in both PC and Wild Rift, regardless of elo ranges, and I think regions.

No worries, we are always looking to improve the game's controls. We don't want the controls to be a barrier for players.

So changing the target lock setting to a "can target" setting.

We will not be making a setting that only means you can only hit X.

This is actually something we recently tested internally and it creates situations where you can just spam your ability and as soon as an enemy champion moves into range you hit them. This removes all aiming/timing and instead pushes things too close to being automated.

The obvious example here is to imagine if Janna's 2 could only hit champions, she would just be able to mash 2 and as soon as you got in range you would get hit. This is the same in the example of Draven's basic attacks. We feel players learning their attack ranges is a valuable skill test, though you can circumvent this "accidentally hit minion" with a target lock.

It is also not the case that if a target is 0.0001 units out of range you will target something else. I don't have the exact ranges, but I just tested with Draven's basic attack and for him t...

I could add some words to Nasus's kit if that addresses your concern. You might have noticed that I can be long-winded.

Really though we consider a bunch of factors when releasing champions. Themes, playstyle, popularity, diversity of the class, diversity of their play position.

You might say Gwen is unnecessary, but I say she is an AP Baronlaner, with a killer theme.

You might say Yone is unnecessary, but I say he is a very popular champion with an appealing theme and flashy playstyle.

Warwick and Vex are both great (I worked on them both, I'm glad you are excited for them), and they touch on many important traits too. But not every champion is going to appeal to you, I would much rather ship champions that some people love and decide to main, and others hate and ban, than champions everyone feels ok about.

It is very unlikely we add per button settings. Settings already have a low usage rate, and each setting we add makes settings as a whole more difficult to navigate/set up. I do think there is a world where we expand or change the current target lock settings (All, No Minions/Monsters, No target Lock) though.

I am curious for anyone reading this, particularly those that use No Minions/Monsters. This option allows you to "select" Minions/Monsters by attempting to target lock on a Minion/Monster, but they are not a valid target. This means you can't lock onto them, so what the system does is it lets you "select" the target, briefly focusing onto them. This basically means that your next attack will hit that target.

Do you use this "select"? Or is it a problem? Did you even know it functioned this way?

Thanks for the detailed feedback and video. This relates to the 2nd point "ability range + X amount" It looks like that X amount might be a little too far.

We want to make sure that you don't accidentally target someone you didn't intend to, such as if Ezreal flashed away, and you wanted to chase him. We could run into issues where he blinked right before you hit attack and you would instead "waste" your Q on Leona, or worse a minion. Though I agree the X range might be a little too far, at least for melee champions.

That is already live, it isn't perfectly "target is out of range, pretend like you are not target locked". Instead, it is "target is out of range + X distance" We did this because we still feel aiming, and learning ability ranges are important skill tests. There are also points where a target might be just out of range and you expect them to take a step forward, or want to zone them.

I generally just leave them in aw and wordless from my 1337 skillz, it helps a lot when I end up misplaying later, but to each their own.

I'm not sure I understand what you mean by "add an option that allows me to use the standard attack targeting options (for auto attack only) while the locked target is out of attack range?" Can you elaborate for me?

Assuming your target is still reasonably within range you'll stay locked on them. There are 2 things that come to mind here and I want to make sure I understand.

1) When the target vanishes from sight so you are not still locked on them. But coming back into sight re-locks on them.

2) When the target is out of range of your abilities + some amount, but still visible, your abilities will behave as if you were not target locked. This was done to help with the accidental target lock problem.

I assume you are talking about target lock settings. And this has been a big topic for controls, we are always looking to improve things and the accidental target lock problem does come up.

I just looked at Akali in my game, and I wasn't seeing this issue, and I don't know of a setting that would cause this. If you have a clip of you trying, and your settings we can look at it. It's possible, there is some sort of bug causing this that I am unaware of.

If a new ability requires new controls than well look at it. But we are unlikely to change existing ability controls unless there is a new standardization we like, and we are very unlikely to change something away from the standard. In Leona's case that would make it different from other similar abilities.

The work...it never ends.

It isn't something we currently have planned, and I don't expect us to change (see how I avoid saying never so this can't be used against me at some far out date if/when things change, very smart I know).

It isn't something we have talked about in a while, but when I did speak with a member of our team who worked on Vainglory, they said it isn't worth supporting those controls. It ends up being incredibly restrictive to design and massively increases workload (meaning slower champion releases).

It also leads to an unideal situation where you are blocking your own vision by needing to cover the screen with your hand. This is why all buttons are at the edge of your screen, with only the emote wheel (not required to play, and shouldn't be used in combat) being in the center of the screen.

We also run the risk of one controls setup being strictly better on a particular champion (forcing players to swap between them), and we would much rather support a great b...

She has been a fine jungler, we are actually adding her to the jungle role list next patch.

I think there is some confusion here, the first Elder Dragon will always spawn at the same time, and despawn the elemental dragon if there is one present. This works like Baron and Rift Herald.

Off hand I don't remember, it is either 1 or 3.

Another fun fact for those thinking this is the perfect Hullbreaker mode. We are making a change to Hullbreaking on Howling Abyss (ARAM and 1v1), we are removing its passive and it now instead grants Armor and MR to replace the split push focused ability.

2 kills or first tower, yes you can recall. We even built an amazing new champion select alternative type thing that I could not be more impressed with.

Before champion selection even starts you ban some champions then pick your champion, skin, and loadout before finding a match. This means that you can be ready to go and effectively skip all that to get straight into the action.

We choose not to have the minion win condition here. It leads to interactive stalling wins that no one was happy with. Minions are also not tracked on the score board and it felt like a bad idea to force players to learn some new rule and to track a new part of the Scoreboard/UI. The intent here is to have quick games to practice champions and prove your 1v1 skills.

Instead the 100 minion win condition is replaced with a flaming circle at, I think I remember, 8:30 minutes. That pushes people to interact, though the circle's size still leaves a bit of room so you aren't just hugging each other.