devtrackers.gg
What if support items grants exp when killing ward
Not a bad idea but generally we want to try to avoid making things even more rule-sy. Especially our systems that are already super rules heavy
What if support items grants exp when killing ward
Not a bad idea but generally we want to try to avoid making things even more rule-sy. Especially our systems that are already super rules heavy
Hmm perhaps a better fix might be for wards to not give experience early in the game. Then you don't have the issue of players getting early level ups whilst still keeping the bonuses for clearing wards as support around the time they would be picking up sweeper anyway. And it keeps any effects from the changes minimal and mostly towards the thing that needs to be changed in the first place. Thoughts?
We floated the idea of splitting the reward (gold/xp) across the entire team but decided against it. Big problem is that the visualization of global gold/xp is poor right now. But also the gameplay of that wasn't as desirable.
Realistically this change is likely here to stay but like I said we are open to other ways to give support back some of what it lost here. For other roles the impact should be near zero
Vandiril is somewhere plotting
We appreciate their efforts even if it sometimes causes us pain
What about the little extra exp supports were getting. It's not a non factor like people would think.
Open to compensation buffs in the future.
Knowing riot it will cause an abusable shop bug that lets someone get full build with a convoluted method in the first 11 minutes.
pls no
I think that’s kind of the point of the change. It sucks to drop a ward for your team level 1 and accidentally f**k over someone’s lane who might not have even seen it happen
It is mostly the point yes
My duo partner did not see them. only me
Found the issue. We check for your summoner level but that check appears to loop every 256 levels. If you are level 256xN + 0 through 10, you will see the arrows. Very much appreciate your help, we'll look to fix in 14.18 or 14.19.
Gonna toss some goodies your way, much appreciated
Interesting. Do you know if anyone else is seeing it or just yourself
Im looking into the issue now
the game ID for my most recent game 5097837369 It happens every game
Interesting. Do you know if anyone else is seeing it or just yourself
• Server: Na
• Type of Bug: In Game Bug
• Description: Lane Indicator shows up even though my account is over level 1000
• Video / Screenshot:
• Steps to reproduce:
• Expected result:
• Observed result:
• Reproduction rate: Happens every game
• System specs:
Can I get a game ID
Not even Yuumi, the best champ design this game has ever seen?
unfortunately not....
Fun tidbit: the AP ratio buff to Command: Attack on Orianna marks the first time that ability has had its damage numbers adjusted since patch V1.0.0.143, which came out in July 2012. It has had tweaks since then, but the damage numbers were untouched for over 12 years.
From my research before I made this change in season 6 she did have a bugfix where the AP Ratio wasn't properly updated (for 5 years she was like that, poor girl). And then the adjustments I made in Season 13 technically altered damage to secondary targets but thats pedantic. Very cool stat thank you
IIRC this is intentional. I thought some Rioter's have said Orianna is bascially a "balance pillar" that they try to touch as little as possible because her numbers are what they want damage to look like on a broad scale.
Usually the lever they pull if they must balance Ori is her ult. Wonder why they finally touched the Q.
Not sure when that was said if ever but there are no champions that we currently view as a "balance pillar". But also wheee Orianna buffs
so yasuo max E 1st meta is back like the good old days?
We are so back
Fixed a bug that caused Miss Fortune's Bullet Time (R) to be redirected if she was hit by Shyvana's Dragon's Descent (R) if MF has a spell shield on her.
What a very specific bug lol. I wonder how the logic on that one worked out!
When Shyvana ults you I think she you to face her direction for some reason. That went through spell shield (probably not just for Miss Fortune). I imagine this fixed was moreso aimed around that specific part of the interaction
Kayn was supposed to be able to jg and top lane. Haven't seen Kayn top in ages.
This reminds me we tested way too much Rell top, but that never worked out once she went live :(
Read moreThis revealing actually only got fixed for Lux E a little while (year or so) ago.
"Targeting" enemy units with
single-target,area,pointblankAOE, orconetargeting type while the enemy team has no vision of you creates a reveal bubble on you at the start of the cast (when the engine-level targeting happens), unless the spell has this turned off with a parameter.The actual "targeting area" for area and cone spells is typically NOT what's actually used by the spell script afterwards; It's just a leftover of a type of targeting that they never fixed to even work with cast times (so before they were each changed to just do this at script level, cone spells like Darius E would "find" their targets on cast start, and then affect them at the end of the cast time - wherever they went).
Anyway, since this whole emerging reveals stuff is super obscure and controlled by spell data that isn't directly maintained or ...
maybe/definitely it's intended
Hadn't considered other languages, that is an interesting thought
All of these types of references ("Yuumi" brings up Moonstone Renewer etc) are directly translated, but often probably won't make much sense in other languages unfortunately.
**Server:*ALL SERVERS EUNE/EUW/NA/OCE ect.*
**Type of Bug:*INGAME*
**Description:*Lulu ult doesn't cc if an enemy dash has been canceled*
**Video / Screenshot:*https://www.youtube.com/watch?v=ekG72pyIQyA\*
**Steps to reproduce:*Cancel a incoming dash with Lulus ultimate*
**Expected result:*Dash is canceled enemy CANT move or cast abilities*
**Observed result:*Dash is canceled but enemy CAN move and cast abilities*
**Reproduction rate:*10/10 works with every dash in the game*
**System specs:*N/A*
Noted on your other post that this is fixed in 14.13