The Problems with Caseloads KBSync (DONT JUST DOWNVOTE LEAVE A REASON) • CCNet

The Problems with Caseloads KBSync (DONT JUST DOWNVOTE LEAVE A REASON) Back

Nxva 5 months ago

Alright, Now I know this is probably going to sound like absolute cope now with the fact that I can take knockback. But here is some actual serious reasons as to why I think kbsync NEEDS to be removed.

1. The fact that low ping has so much advantage over high ping. Low ping players get to be able to disable shield SO easily high ping players its very had to do it unless your extremely skilled and even then.

2. The fact that when not using a shield in just basic sword pvp it looks like reach. When fighting low ping players some of us higher ping players have experienced 4-6 block hits. It isnt fair for us to not be able to hit other players just because of how caseloads kbsync plugin works. (this is an actual issue with the plugin)

3. The KB is SO delayed. I swear if I s tap good enough i can make contt fly and this should not be happening

The fact is, Low ping players have such an advantage over higher ping players especially with shields and I dont believe its fair for us higher ping players too have to deal with these problems as it makes the server not as enjoyable to fight on with a problem that can be fixed by taking out the plugin that we fought with for years and still managed too have fun.

Please dont just downvote. Leave a comment im down to discuss this with people. :D and yeah ik alliance bouta ping everyone to downvote this but yk

Comments

ContDJ 5 months ago

I agree with this honestly, axe spamming doesnt disable shields(for high ms) and its an annoying feature, insane kb and then no shield cooldown it just becomes more worse and unplayable

EGirlMango_ 5 months ago

Going to state all my reasoning on here too(sorry for double sending for the discord homies)

The Shield cope first:
Axes with no efficiency when spam clicked have a much lower chance of breaking a shield.
"Efficiency applied to an axe increases the chance that the axe may stun a shield, with the base chance being 25% and a 5% increase for each level of Efficiency.‌[Java Edition only] This only applies when the player is not sprinting, since sprint attacks already guarantee a shield stun." - Minecraft wiki

If you want consistent shield disables you need to sprint hit, hit with full timing, or cooldown swap with a hit with the full timing. This means a efficiency 5 when spam clicked will only have a 50% chance of disabling when hitting the shield. This isn't noticeable at lower pings as you have more time to hit the shield meaning more of your spam hitting lands. This is why the cooldown trick I was mentioning earlier is so important and why I personally haven't felt any issues disabling shields.

The "Issue with the Plugin":
" It isn't fair for us to not be able to hit other players just because of how caseloads kbsync plugin works. (this is an actual issue with the plugin)" I'm interested to how you found this conclusion since I couldn't find it anywhere online other than this suggestion. It's not even on the issues tab of the plugin itself on github, id assume it would be if it was "an actual issue with the plugin"