I had laglocked many paladins as a barb zerk. The only I failed to laglock actually was Pali's. It is not as hard as you think. Just don't do it with a staff. Gotta be dual wielding offensive weapons and enlarging.
Attrition game
And L-A' date=' it is much better to kick dirt at the start of the tick, instead of close to the end
[/quote']
You wouldn't believe how long it took to train myself to wait 2 rounds (which was consistantly where I'd input the command) so the tick would go before I dirt kicked
L-A
Nameless, Jibber, I am not talking about "the length of a battle till the pally dies". Ofcourse, if you engage a pally at awful all you need is one successful bash and it's a laglock.
I was talking more about reliability of bash and that almost every third bash will miss, i.e. there is a 30% chance for your bash to miss. Ofcourse, this is a variable that is highly dependable on plethora of stats such as luck, defense, dex and so on. And don't get me wrong, I am not complaining or something, this is just a mere observation from the day which I decided to make a FG warrior and try to bashlock pallies, mislead by post like:
I lag locked an elf paladin from beginning to end of fight' date=' truly decked to hell, and in Knight, with a Warmaster Fire Giant. And the player was notable, too. So yes, it can be done.[/quote']
Statements like this one makes it look to the new and inexperienced player that it is easy as hell to bashlock a pally, even one that is "notable and decked as hell", when this is not the case. Yes, it can be done now and then, but for this laglocked pally, how many pallies have escaped at pretty hurt due to a missed bash? If it the answer is no less two (usually much more), then my logic is correct yes?
Err huh? You can bash lock a pally from full health to dead, just as easy as they can flee from the bashes and disappear. There is no "this is easier than this.". I was an FG Barbarian V Warrior, used absolutely not WM skills, and was pretty okay equipped. The person I killed was Festy's Paladin in Knight, where he immediately deleted because I bash locked him.
I've done it to other Paladins too. I'm not trying to mislead anyone here -- not even newbs. But newbs should be aware that yes, it CAN be done with enough persistence, patience, and quick thinking.
(and yes, the paladin was fully buffed.)
yes' date=' it CAN be done.[/quote']
Just as necro killing a BLM is possible as well
Just as necro killing a BLM is possible as well
If you laglocked a decked paladin with more than three bashes without a fail you are very lucky, even if you are at huge size. Bodyslam is stronger than bash, but I don't think the difference should be that big.
I would say the average bash rate of a Giant vs a normal sized opponent is of about 80%. With ~70% to a Paladin. Add enlarge pill that work better for the basher than the bashed, as he is the one who decides when to pop and bash and you can see why lag locks happen.
It's not that hard for a Fire Warrior to bash a Paladin 4 times in a row, leading to 8-10 rounds of lag. Add a spear and a dualed whip and you will not be touching the warrior while he eats you up with meele and arrows.
shrugs My paladins never get bashlocked to death. You people must be doing something wrong.
Yeah, mounted paladins with a decent AC are very hard to bashlock. Of course it can be done, but that would be the exception and less reliant on the basher's skill as much as the paladin's skill. They have very good melee defense too. Toss in magic strike and you have some good reasons to try another tactic.
Statements like this one makes it look to the new and inexperienced player that it is easy as hell to bashlock a pally, even one that is "notable and decked as hell", when this is not the case. Yes, it can be done now and then, but for this laglocked pally, how many pallies have escaped at pretty hurt due to a missed bash? If it the answer is no less two (usually much more), then my logic is correct yes?
Out of the 5-8 pallies i fought as my zerk, I failed to laglock 2 Deykar, and Pali. That is from full health to dead at their pit. Orodreth (festy) even caught me pants down and landed a disint charge AFTER I had just been in a fight and I laglocked him. Sure pallies escape at pretty hurt, but that happens all the time. For killing a pally I prefer laglocks, or invokers. Those two tactics are best equipped to deal with a pally IMHO. People can disagree, but I will disagree right back. I have played a rather successful pally, and the only thing I ever died to at pinn was a Traven army (**** you mindflayer 
) the reason? Bashlock. the mobs themselves did less than scary damage, but being lagged by 3 titans in one round wth an necro acid blasting me was the problem. so being on the giving, and recieving end, pallies are easiest to take out with a laglock
pallies are easy cheese for a good shaman.
mass hyst
blind
blasp
The key is surviving while eroding those saves.
pallies are easy cheese for a good shaman.
mass hyst
blind
blasp
The key is surviving while eroding those saves.
Any pally who is not getting too excited is gonna flee the MOMENT hysteria lands period lol. No matter what my class I will NEVER fight with hysteria on me unless I have 0 choice.
I still say I will take 50/50 hit dam zerk over a shaman for pally killing
Any pally who is not getting too excited is gonna flee the MOMENT hysteria lands period lol. No matter what my class I will NEVER fight with hysteria on me unless I have 0 choice.
I still say I will take 50/50 hit dam zerk over a shaman for pally killing
I never fought your pally then on my shamns
mass hyst is the most overlooked debuff in the game
If you recall in our voker vs shaman entrance to nexus fight, you landed hysteria and I was GONE. I will NEVER fight with that mal on me ever.
ditto. Mass Hysteria is a killer.
Mass hysteria, overlooked? Those people need a slapping.
Hysteria used to screw me completely on my slith warriors, Loucheran had stuff all saves, but bundles of Hit dam. The avatar I then made had a bit of a mix, and fared ALOT better against shamans. Loucheran I just had to plain outdamage and chase them down I'd end up thoroughly spelled and have to go heal them.
Oh Philantees, Oppressant often uses mass hysteria, which doesn't bother me too much, I just continue to fight (and even capped them after it landing) as they have nothing that can do long term damage to me, and nothing that can lag me. So there is very little risk. On a normal character, mass hysteria means its time to leave 
honestly, with my shaman I find that melee's just ignore the hysteria an keep on trucking. Some would flee, but mostly they would try and fight through it from my experience.
my vamp never had to fight any shamans really, undead should have an easy time with the class tbh.
half blm is a bad day for most shamans I would imagine. A savant shamn of mine had the hardest time with WM half blm's. They just output to much damage to quickly.
If you recall in our voker vs shaman entrance to nexus fight, you landed hysteria and I was GONE. I will NEVER fight with that mal on me ever
mass hyst does nothing against a caster other than reduce their parries which against a shaman isnt much to parry. Or so I thought.
Out of the 5-8 pallies i fought as my zerk' date=' I failed to laglock 2 Deykar, and Pali.[/quote']
Considering how many times we fought, I feel fairly confident in saying that your failure to laglock me was due to me prepping/equipping slightly differently than the other paladins you fought rather than just luck.
Yeah, I may have ran into your elf pali once....several key skills to blackjacking mastered and failed to blackjack you six times in a row....:confused: