Cassiopeia LoL Script Settings: Twin Fang, Blast, Gaze

Quick verdict: Cass needs the script to hold Twin Fang at a human rhythm, land Q prediction at max range, and fire R the instant a dash starts. Set the values below and you'll see the difference in one game.

Cassiopeia is one of the few champions where a lol script changes your damage output more than your positioning. She's a DPS mage with a 0.75 s attack windup on autos, but her real damage comes from spamming Twin Fang between Q and W. The script's job is to keep that E rhythm tight without looking like a machine. Get the pacing wrong and you either lose DPS or get flagged. Get it right and you out-trade every mid laner in the game.

This guide covers the three settings that matter most on Cass: Twin Fang spam pacing, Noxious Blast prediction, and auto Petrifying Gaze against engages. I'll give you exact values, explain why they work, and show you how to adjust them for your ping and elo.

Why Cassiopeia Needs Different Script Settings

Most mages want the script to land one combo and back off. Cass wants sustained E casts. Her Twin Fang has a 0.75 s cooldown that drops to 0.375 s on poisoned targets, and with enough ability haste you're looking at an E every 0.3 s in late fights. That's faster than most human players can click accurately, which is exactly where a well-tuned script shines.

The trap is over-tuning. Set the E delay too low and you're casting faster than the cooldown allows, which just wastes inputs and looks robotic. Set it too high and you lose the DPS race against a Zed or a Sylas who's already on top of you.

In our testing, the sweet spot sits between 90 and 110 ms between E casts. That's fast enough to feel oppressive, slow enough to pass the eye test in a replay. Ping matters here: if you're on 40 ms, run 90. If you're on 80 ms, run 110. The script should add roughly your ping to the delay automatically, but check the setting.

Twin Fang Spam Pacing: The Core Setting

Twin Fang is your damage. Everything else on Cass exists to enable it. The script needs to know when to hold E and when to fire it, and that comes down to three sub-settings.

E Cast Delay

Set this to 90-110 ms as above. But also enable the 'respect cooldown' option if your script has it. That prevents the script from queueing an E before the cooldown is up, which is the main cause of the 'stuttering Cass' look that gets you reported.

E Priority Target

Cass should always E the closest poisoned target unless a kill is available elsewhere. Set target selector to 'lowest effective HP' with a range of 700 units. That's her E range. Anything beyond that is wasted input.

E on Minions

Turn this off in Combo mode. You don't want the script E-ing a caster minion while the enemy mid laner is free-hitting you. Keep it on for Lane Clear mode only.

Here's the scenario that separates good Cass scripts from bad ones. You're against a Viktor. He walks up to Q you. Your script should instantly Q him (more on that below), then E twice before he can walk out of range. With a 100 ms E delay, you get both Es off in the window where a human would maybe get one. That's the entire trade.

If you're new to scripting and want to understand how the orbwalker handles this kind of sustained casting, our orbwalking guide breaks down the mechanics.

Noxious Blast Prediction: Landing Q at Max Range

Noxious Blast is a skillshot with a 0.25 s cast time and a 0.4 s delay before it lands. That's 0.65 s of travel time at max range. Most players aim where the target is, not where they'll be. The script fixes that, but only if you set the prediction correctly.

• Prediction lead: 0.15 s (add 0.05 s per 100 ms of ping above 50)
• Hitbox buffer: 55 px (accounts for Cass's Q radius of 75)
• Prioritise movement: enabled (predicts based on current velocity)
• Prioritise dashes: enabled (catches Ezreal E, Zed W, etc.)
• Max range: 850 units (Q range is 850, don't over-extend)

The 0.15 s lead is the number I'd start with. It's aggressive enough to hit a strafing ADC but not so aggressive that you're Q-ing behind people who are walking toward you. In Diamond+ lobbies, players change direction more often, so drop to 0.12 s. In Gold and below, bump it to 0.18 s because people walk in straight lines.

The hitbox buffer is where most people go wrong. Setting it to 0 means you miss anything that's moving sideways. Setting it to 80+ means you're Q-ing the air next to them. 55 px is the sweet spot for Cass because her Q has a 75 radius, so a 55 px buffer still keeps the centre of the circle on the target.

One more thing: enable 'Q on poisoned targets only' in Combo mode. There's no point re-Q-ing someone who already has the debuff. That's wasted mana and a wasted cast time.

Against a Yasuo, this matters more than anywhere else. He'll try to Wind Wall your Q. If the script predicts his dash behind you, you can Q the spot he's dashing to and hit him before the wall goes up. That's a free E reset and usually a kill.

Auto Petrifying Gaze Against Engages

Petrifying Gaze is a 0.5 s cast time ultimate with a cone. Hit someone facing you and they're stunned for 2 s. Hit someone facing away and they're slowed. The script's auto-R feature is the most valuable setting on Cass, and also the most dangerous if you get it wrong.

Set the trigger to 'enemy champion dashing toward you within 550 units'. That catches Malphite R, Zac E, Jarvan EQ, and every other engage tool in the game. The 550 unit range gives you enough time to cast R before they land, but not so much that you're R-ing people who are just walking at you.

• Auto R: enabled
• Trigger: dash or hard CC toward you
• Range: 550 units
• Facing check: enabled (only R if target is facing you)
• Cast delay: 0 ms (fire immediately when trigger hits)
• Humanizer on R: disabled (this is a reaction, not a spam)

The facing check is critical. Without it, the script will R people who are running away and you'll get a slow instead of a stun. With it, you only R when the target is actually looking at you, which is when you want the stun anyway.

Here's the classic scenario. You're Cass mid, enemy Lee Sin is ganking from river. He wards, you see the animation, he flashes and kicks. Your script's auto-R fires the moment he starts the dash. He lands, gets stunned, and you E him twice before he can move. That's a kill you don't get without the script.

If you're running a full League of Legends script like Cado, the auto-R feature is already tuned for Cass. You just need to enable it and set the range. The rest is handled by the champion module.

Orbwalker and Combo Mode for Cass

Cass isn't an auto-attack champion in the traditional sense. Her autos are for last-hitting and applying the poison from Q. The orbwalker should be set to Combo mode with E as the primary spell and Q as secondary. W (Miasma) should be manual, because the slow field is too situational for the script to place well.

Set your orbwalker to 'kite back' when enemies are within 400 units. Cass has no escapes, so staying at max E range (700) is how you survive. The script should automatically move you backward between casts. That's the difference between a Cass who dies to every dive and one who 1v2s.

For lane clear, turn on 'E on minions' and set the orbwalker to Lane Clear mode. Cass clears waves fast with Q and E, and the script will do it without you thinking about it. Just watch your mana.

If you're struggling with the orbwalker settings in general, our mechanics improvement guide covers the fundamentals.

Humanizer and Safety Settings

Cass is a champion who casts a lot. That's a lot of inputs to humanize. Set your humanizer to 35-55 ms randomisation on E casts and 8-12% miss chance on Q. That means one in ten Qs will be slightly off, which is exactly what a human Cass looks like.

Don't turn off the humanizer on E. I know it feels good to have perfect Twin Fang spam, but it's also the most obvious tell in a replay. A Cass who never misses an E is a Cass who gets reported. The 35-55 ms variance keeps you under the radar.

Evade should be enabled for skillshots only. Cass can't dodge autos, and trying to dodge them will pull you out of position. Set dodge radius to 180 px, which is enough to sidestep a Xerath Q but not so much that you're running into melee range.

For a deeper look at how to set up your script without drawing attention, check our safety and humanizer guide.

Role-Specific Adjustments: Mid vs Top

Cass is primarily a mid laner, but she sees play top into melee matchups. The settings differ slightly.

Mid: keep Q prediction at 0.15 s, E delay at 100 ms, auto-R on. You're against mages and assassins who dash at you. The auto-R is your lifeline.

Top: drop Q prediction to 0.12 s because melee champions walk at you in straight lines. E delay can go to 90 ms because you're often in extended trades. Auto-R still on, but set the range to 450 units because top laners engage from closer.

If you're playing Cass in other roles (don't), just use the mid settings.

Common Mistakes with Cassiopeia Script Settings

• Setting E delay below 80 ms: you cast faster than the cooldown, wasting inputs and looking robotic.
• Turning off Q prediction: you miss every moving target and lose the poison for E.
• Auto-R without facing check: you R people running away and get a slow instead of a stun.
• Max humanizer: your Cass looks like a bot in replays, which is the fastest way to get flagged.
• Ignoring ping: if your E delay doesn't account for ping, you'll stutter in game.

Most of these come down to over-tuning. The best Cass scripts feel slightly imperfect. That's the point.

Getting Started with Cassiopeia Scripting

Load into a practice tool first. Set your E delay to 100 ms, Q prediction to 0.15 s, and auto-R on. Hit the training dummy for five minutes and watch the replay. If your E casts look like a metronome, bump the humanizer up. If they look sloppy, tighten the delay.

Then take it into a normal game. Play three games and adjust one setting at a time. By game three, you'll have a Cass that feels like you on a good day, every day.

Cado's Cassiopeia module ships with these values as defaults, so you can start there and tweak. The lol script handles the Twin Fang pacing and Q prediction out of the box. You just need to set your ping offset and humanizer level.

FAQ

What is the best E delay for Cassiopeia in a lol script?

90-110 ms depending on ping. Add roughly your ping in ms to 90 for the base value. Lower than 80 ms wastes inputs because the cooldown isn't ready.

Should I enable auto Petrifying Gaze?

Yes, but only with the facing check enabled and a 550 unit range. That way you stun engages without R-ing people who are running away.

How do I stop my Cass from looking like a bot?

Set humanizer to 35-55 ms randomisation on E and 8-12% miss chance on Q. Never turn off the humanizer on E, it's the most obvious tell.

Does Cassiopeia script work in top lane?

Yes, but lower Q prediction to 0.12 s and auto-R range to 450 units. Melee top laners engage from closer and walk in straighter lines.