Cooldown on Jabs

Not gonna lie most of my kills are from me slash surfing when I get the chance. It's the strongest possible attack of knight combat because it involves velocity and slashes. It's not the hardest thing to do except when dodging jabs, but you certainly have a point that the combat isn't very intuitive. It is still slightly better than mindlessly clicking though. And I don't think anyone can argue that new players use a lot of thought when jabbing, they jab because it's the only thing they know how to do.

 

When you jab a shield, it should always stun and for long enough to counter jab. Jabs that do connect should actually stun and not turn slashes into jabs. Increase the risk and increase the rewards and you get an attack that is effective when used right, less effective when not used correctly.

 

The jabbing with the upward angled shield is a bit wonky. I was shielding at an angle and his jabs went right through my shield. Is that something that can be fixed?

 

Latency, High ping nigaz will slip through (such as me auss vs ace @ChargingLocket @Tynite )

@TheDirtySwine Im sorry but you can't stop latency so the speed you can jab can be countered by taking Speed and smacking that right mouse button like ur scratching at ur skin for bugs

 

Don't you dare ever use the words 'Ace' and tag ChargingLocket and Myself again. Don't have time for this shenanigans.

 

Any good game is easy and fun for noobs and hard for pros, or players that dedicate to it. Nerfing the jab spam will encourage new players to start using slash. But i dont see the problem of jabspam, just use right click

 

thats what geti says
thing is it won't work

 

tl;dr holding LMB is moar skillz than pressing LMB

once again johny98 beats the mythical hero of KAG, Brad, age 18 dancing on that high ground while spamming 5 and 2. CAN THE EVIL JOHNY BE STOPPED

 

That's not the only problem. If you're sheilding, he'll get stun for a little while. You need to jab back very quickly and that's way harder when you're lagging, while jabspamming is easier when you're lagging. Plus the enemy will keep jabspamming so you also need to sheild again properly, and if you're a bit lagging, again, it's really, really, really terrible. In a closed environnement it's even worse since you don't have enough space to retreat quickly for preparing a slash.
Being against 2 "regular" enemies is easy if you're good, being against 2 jabspamming enemies is hard as heck even if you're good.

ftfy

 

Only time I ever have an issue with jab spamming is in enclosed spaces (e.g. you both fell in a pit). When in a pit, you can't back away and slash, all you can do is shield and wait for the stun. Usually when they get stunned though, and I jab them, they still get a jab in. Meaning we both lose 1 heart, and sometimes I end up losing 2 somehow because the shield doesn't go back up in time. So basically, jab spam is still effective even with the stun.

However, that might just mean I have absolutely horrible timing with my jabs in those situations.

 

To punish a jab spamer you need to be very quick, you have to predict when hes gonna stun himself.
Also dont worry your not terrible, its hard thing to do.
My advice is after the punishing jab dont shield again but keep jabing

 

This is why you should rework the majority of the code to allow it to run on 60fps.
But probably the biggest reason is that I would play the game again, and you practically can't say no to that.

 

Eh, no. Now most games are running at 20-40 ticks per second. 60 would be insane, and you'd get slower framerate. Plus to have such a performance gain this would require threading and massive rewrites and the current KAG engine does not allow that.

 

1/10 for understanding of tickrates and framerate. (laughed at 60 tickrate being insane)
1/10 for understanding of a joke

F- see me after class

 

I perfectly know what those are. Allowing the game to use 60 fps while keeping the same tickrate would have no change on that, and higher tickrate will just make the game go slower on lower pcs since it would need more ticks to process = more cpu power = less for rendering.

aw