RiotRayYonggi

RiotRayYonggi



01 May

Comment

Please note the Corki midscope is still in active development and you’ll see changes hit PBE frequently. We are still working to ensure he’s a viable bot laner with a niche in the roster, while using the new item adjustments similar to other caster marksmen.


30 Apr

Comment

Originally posted by NonTokenisableFungi

Cut Down my beloved, what is happening to you

It's similar tuning to Coup De Grace but applies at full HP. This means that it's more likely to trigger in a variety of places, whether that is lane poke, burst from high HP (AOE Mages, Karthus, GP), and siege poke (Xerath, Zoe). If we don't consider Coup De Grace weak, then this likely shouldn't be either.

That's my analysis at least, but we have time to tune it if this ends up untrue.


04 Apr

Comment

Originally posted by DT2X

hopefully with double the players (and double the bans) we won’t face as many degenerate duos like leona/kassadin/singed/alistar/tryndamere + yuumi avoiding you until the zone kills you. stuff like that ruined the game mode for me

We intend to address stalling as well with this version.


24 Mar

Comment

Originally posted by RiotRayYonggi

We typically just allow Sylas to be OP with new spells and don’t stop designing because of him. It would be really lame for 1 designer to ship a champ that restricts every designer after them.

As for the Samira Sylas thing, my understanding is that Sylas does not get Samira passive, which prevents him from casting R. This is definitely not ideal from the player perspective, but would require us to either move passive logic into R (which means Viego can’t stack it) or special case Sylas, which may be more cost than value.

I’ll make a note for next week to see how difficult it is to just let him ult without condition with Samira R, and whether that’s something we’d want.

Comment

Originally posted by Eternal663

Was there ever an abillity you thought "It's perfect on the champion we want to make but would be too broken (as in wouldn't function properly or would be way to powerfull) on Sylas". Did releasing him or any other champions made you ever go back on something just because it would be too good/bad on them.

Also Ps. Please explain why is Samira ult still disfunctional on Sylas. He can't gain an S rank to use it, nor it has any passive effect on him. If he ever steals Samira ult he is forced to wait untill it expires (thankfully it does). It caught me off guard once in Aram where i thought imma steal 'Inferno Trigger', go in and deal some AoE dmg but ended up Inting and having to wait like 3 fights just to be able to ult again.

At least it was broken like 2 patches ago when i played it, didn't check since

We typically just allow Sylas to be OP with new spells and don’t stop designing because of him. It would be really lame for 1 designer to ship a champ that restricts every designer after them.

As for the Samira Sylas thing, my understanding is that Sylas does not get Samira passive, which prevents him from casting R. This is definitely not ideal from the player perspective, but would require us to either move passive logic into R (which means Viego can’t stack it) or special case Sylas, which may be more cost than value.

Comment

Originally posted by helloimapickle

i am SO curious to know what the hell caused that viego-zyra bug lol, I'm sure everything was very funny until someone had to fix it

just as a question, when testing new champions is it still expected to test them with viego, sylas, renata etc. or is it just expected to work out of the box?

This was all a bit before I started learning to read/write champion code myself, but my understanding of the cause was:

Most champions had spells/passives/etc that only had to check for “themselves” to trigger logic. So when it was Viego running their logic instead, it would not know what to do.

So in Zyras case, it would spawn a plant, then check “Zyras” passive cooldown before sending another one. Because there was no “Zyra” passive to check, it would just fire off another plant, and repeat until Viego left her body or until some other bug stopped it.

As for the final question, Viego/Sylas/Renata etc all caused us to have new “standards” for how to properly script to not run into the common bugs with them. So new champs should follow these standards and just work, but regardless, our QA teams would test to make sure it works anyway.

Comment

You are correct in that Viego and Sylas were both nightmares. Once we “locked” the general mechanics of the ult/kit stealing, we had to play test with the (very slowly growing) list of champions that wouldn’t break the game when interacting. This meant a LOT of playing simple stuff like Jinx until we slowly bug fixed every single interaction.

Did mean some funny moments when a champ labeled “functional but probably bugged somehow” in our champion tracker was played and would break the game somehow. For example, Viego possessing Zyra spawned about 6 thousand plants all around the map in around 5 seconds due to a bug with her passive.

Seeing how that development went, it’s a miracle we untangled all the spaghetti to where they function reasonably as expected on live now.


11 Mar

Comment

Finally some good f*cking discussion


22 Feb

Comment

Thanks I'll pass this along today


15 Feb

Comment

Originally posted by TwMDa

When is the reworked Skarner gonna hit PBE

Never ever


10 Feb


02 Feb

Comment

Originally posted by LeVentNoir

Allow blue trinket from level 1.

There's no reason to not allow it unless you think people should be exposed to danger to place wards, and if that's true, then why is there a range on sightstone and yellow trinket anyway? Give both 150 range, melee amounts.

It's absurd in games where you know someone is in a bush, but can't even approach to fight them of it because of the power of a surprise hook.

Think a blitz or Leo camping a botlane bush.

If you don't have vision reveal or strong untargeted damage, you simply can't go within 800 units of the bush without risking an all in.

That's really it, insisting that low mobility champions be acceptable targets for getting jumped and preventing any way of playing well that negates it.

One of the issues with blue trinkets level 1 is that they would be used to find the jungler 95% of the time, which is not gameplay we would find to be positive for the game.

Comment

Originally posted by RiotRayYonggi

Neeko can likely viably be played in all 5 roles.

Brand too now that I think about it.

Comment

Neeko can likely viably be played in all 5 roles.

Comment

Interesting idea but has a decent amount of effects we’d have to account for, such as warding over certain walls into bushes from safety. For example, you would be able to trivially place wards across jungle areas during invades, or from one end of a bot lane bush to the other bush, avoiding melee supports trying to get an engage.

Not saying we wouldn’t investigate something like this, but it’s a version of increased safety and vision creation we would need to carefully consider is not more damage than gain.


30 Jan

Comment

Yes it should. It's easier said than done though. I tried doing this myself (without engineering support) and it was very involved and required adjusting every champion in the game one by one as there's nothing in tooltips that marks them as a heal or shield specifically, it's just text. It's a noted request, just needs the right moment to be worth the effort.


27 Jan

Comment

It deals 100-200 base +20% AP. At around 300 AP this is less than 250 damage, which is significantly short of another 40-50% damage for a burst champion, and is very similar to the average output of many, many other items in one fight. Stormsurge may have shipped pretty overtuned but you may want to observe its average output in a fight on the newer, nerfed version.


19 Jan

Comment

Originally posted by RiotRayYonggi

Yeah we should fix this. It's inaccurate after we had a different version (that spawned more statues) that ended up not being viable for large-scale. I'll make sure the team is aware.

It's set to be fixed for 14.3, sorry about that.

Comment

Yeah we should fix this. It's inaccurate after we had a different version (that spawned more statues) that ended up not being viable for large-scale. I'll make sure the team is aware.


10 Jan

Comment

Looks great! Well done