phroxz0n

I can speak for the mage side.

• The intention with these changes is to make builds more differentiated from each other.

• We also didn't want to make the system more difficult to balance (ie. have to ceiling one subclass' access to haste based on another subclass' access to haste).

From the design side, we want to use Haste as both a "progression" axis (makes your champ feel like it's getting stronger relative to the game state) and "choice". The AP Mythics all having Haste are intended to make your champion feel more fluid (you're not meant to choose between haste and no haste on Mythics, but instead a little haste [Ludens] and a lot of haste [Liandrys]).

As much as possible, we wanted to avoid the "one item that fills everything" in the second slot. Cosmic Drive is intended to be the "choice" Haste option, fighting against some of the more burst oriented options like Horizon Focus, Lich Bane, scaling options like Archang...

yeah, if the ally themself is in champion combat, the fix should fix that.

Yeah, sorry for that, the item is still bugged if the user themself is out of combat and they try to renew the buff without damaging an enemy. It should be fixed for 10.24. The original heal instance if the user is out of combat functions correctly, but renewing the buff does not if the user stays out of combat (eg. soraka standing in the back healing, but not damaging anybody) :(

do you have any evidence/replay of this? I cannot reproduce it.

If anyone else runs into this, please DM me the game that it occurred and your summ name/server. TY

EDIT: Figured it out, thanks everyone

I'll take a look at it, thanks

EDIT: Figured it out, thanks everyone

Can you pass me the reproduction steps for this? It should remove the control wards in your inventory but grant the equivalent stacks on the wardstone. If you wouldn't mind checking the replay, that would be great, thanks.

EDIT: Figured it out, thanks everyone

It's mainly there as a gating mechanism to prevent non support Champs from upgrading the item. Functionally, spamming wards in the fountain doesn't actually help your unlock because as others have mentioned, the true gating mechanism for supports is level 13. As a champion with a warding item, you'll almost certainly have placed 20 wards by the time you've hit level 13.

This type of idea is typically quite unsatisfying for the user. Its success case leads to disincentivizing action as the optimized behavior. It might be satisfying on release while enemies are caught off guard by the turnaround, but once people start playing around it, it will end up being quite unsatisfying and have very few use cases.

Support gold gain for quests is slightly faster than in S9. The Support item final upgrade is slightly weaker to compensate. This will allow supports to get into the main item system faster.

Fully upgraded support items should be counted as legendary items. If they're not, it's a bug on our end.

You could be forgiven for thinking OP was talking about the first lux shield that hit 0 people.

lol are you memeing august. No, but if we can get a repro, I'll try and fix it for good.

Do you have a link? I thought I fixed this issue, but I suppose not...

I think a lot of it is spillover from the boards, I'd imagine a lot of those posters are now making threads on reddit instead.

For me, part of it is that I need to be in the thread almost immediately when it goes up. After a thread has been sitting for a while, there's not too much point posting, especially since you have to be extremely careful with what you say. That's mainly because things you say get dredged up again years later or snipped out of context. The other thing is to consider the value that I could add to a conversation. When it's primarily a complaint post, there's usually not much to add outside of "I acknowledge your post and read it".

I can speak a little for Sylas and a little to the general strategy. We generally want as many champions playable for regular play as possible. This includes Sylas. Usually when we're talking about removing a champion for a role, this is with relation to Pro play as it makes then very flex heavy and thus high blind pickability (and raises their presence dramatically). Usually when we're trying to remove a particular champion from a role for regular play, it's called out explicitly in the patch notes.

For Sylas specifically, we wanted him out of jungle for Pro. As it stands, Sylas is very playable for regular players in jungle, but not for Pro and that was basically the intended result. We were prepared to accept Sylas being a suboptimal pick for regular players in Jungle, but it seems like for now, we didn't have to weather that cost.

The main times when we want to remove champions from roles is when their gamepla...

It's in the patch notes and usually mark Yetter should tweet them out. I'll let him know, I know he was busy this morning.

There's an E bugfix that was micropatched in yesterday for his E being longer than what the indicator intended.

Generally speaking, we try to avoid having "UNIQUE Passives" on components (at the primitive stat level; eg. long sword, mana crystal, pickaxe, etc.), mainly due to the complexity that bubbles up into the items that build out of them.