How Crit RNG Could Be Removed

Woodakoodashooda·Jan 17, 2020·1 votes·569 views

Not an original idea, mind you. One taken from the Fallout franchise to be honest, but here goes.

Champions who build crit gain a crit meter. The crit meter fills by 1 per auto attack for every 1 percent crit chance bought. Any auto attack that brings the meter to 100 consumes it and is a guaranteed critical strike.

At or above 100 crit chance, every auto attack becomes a guaranteed critical strike as per usual. Points, however, do not carry over. Meaning, even if your crit chance is something like 40, three hits equals 100, not 100 and then 20 towards your next critical strike.

Edited

Instead of waiting for the meter to fill for an auto to become a crit, any auto that fills the meter is a crit and consumes the meter automatically.

5 Comments

Posui GartJan 17, 20201 votes

Is there even a problem with crits?
This change makes it mandatory for an ADC to "prepare" a crit before the fight. Its not fun for the ADC, not fun for enemies, not a skill expression, but everyone just has to do it
How will >=50% crit chance work, like 75%? I hit first aa, get 75/100, next aa makes it 100/100, 3rd one crits and resets it to 0? So an adc with 75% crit chance will crit every 3rd attack? Thats not 75% at all, thats 33%

WoonStruckJan 17, 20201 votes

This change makes it mandatory for an ADC to "prepare" a crit before the fight. Its not fun for the ADC, not fun for enemies, not a skill expression, but everyone just has to do it

Auto attacks are such a low investment move that it wouldnt be a problem at all. It'd be an issue during laning more than teamfights. Every ADC trading like Caitlyn with her passive.

How will >=50% crit chance work, like 75%? I hit first aa, get 75/100, next aa makes it 100/100, 3rd one crits and resets it to 0? So an adc with 75% crit chance will crit every 3rd attack? Thats not 75% at all, thats 33%

Its a rather inelegant way of solving how static adc itemization can be, since theres no point in going past 50% crit unless you're going all the way to 100%.

Pretty sure autos that would place you at or above 100 would result in the crit, not the auto attack after unless the goal is to basically cap crit at an effective 50%, which honestly isn't a bad thing if itemization as a whole in the game were revised, which it needs to be anyway.

Posui GartJan 17, 20201 votes

Every ADC trading like Caitlyn with her passive.

Except that right now its Caitlyn-only feature, but with those changes everyone will be forced to play with this. Caitlyn herself will have some more problems with trying to sync her passive and crits, which will be extremely annoying for both Caitlyn players(a lot of bush plays with jungle camps before every fight) and enemies(Caitlyn's 1st AA is a crit headshot and there is nothing you can do with that)

Its a rather inelegant way of solving how static adc itemization can be, since theres no point in going past 50% crit unless you're going all the way to 100%.

Well, thats the point really. There are other ways to solve the problem of crit rng winning/losing early fights without fucking up the itemisation. Example: -crits with <50% chance got their crit chance doubled but crits are 150% instead of 100% Or -crits now deal 50% of their damage as a 2 second dot, each crit has independent instance of dot Or just straight "X% chance to crit is replaced with +X% autoattack damage" But I don't really see the problem with crits working as they work now

WoodakoodashoodaJan 17, 20201 votes

Players have complained about the RNG surrounding ciritcal strikes for a while. Since season 1 if I am not mistaken as a result of Tryndamere and his passive.

It would not be mandatory to prepare a crit for a fight, but it would give creative control over how to manage critical strikes. Like how Jhin's passive works in which he auto attacks three times for an empowered attack against champions. Or how Caitlyn prepares her empowered attacks by attacking from brushes.

As for your last concern, I realized an error in my suggestion and corrected it with a quick edit.