I should note that neuro can be geared against using svpar. In fact, the Sleep spell also falls into a roughly similar category, except is that you can take certain precautions such as not being in an area with a possible summon trap room, having high svspell. The sleep user also needs to approach visibly and attempt to get the first spell off before the victim attacks.

Bash is harder: enlarge/reduce won't stop a skilled basher with a consider target macro. Personally (despite the number of people claiming giant warriors are weak) I think giant bash is still competitive because it is overpowered vs those few combos vulnerable to it (to a degree that there's a good chance that victim cannot do anything, regardless of skill, to survive, once the first bash goes down). It means basically that I will never again play any combos vulnerable to perma-bash.

I've posted a log of being perma-lagged by Krunk over 15 rounds of combat as a prepped/decked Defiance-wielding Fortitude-having 2h elf paladin with 100% evasion and Evasive edge. 15 rounds of perma-lag is a bit much.

If coding were not a constraint I think a good balancing mechanism is to have a counter that increments each time a "perma-lag-possible" move is made, e.g. trip/cheapshot, throw/wind-knocking-GC, big neuro, bash > 2 rounds. Past a certain count, it will be impossible to get a perma-lagging version of the skill landing.

So you might, as a giant basher, be able to count on 6 (for example) consecutive rounds of bash lag, but no more than that. So to get your kill, you have to get your opponent low enough and then unleash the 6-round lag + flurry for the win. To compensate, the chance of a > 2 round bash could go up for the first time the basher uses it.