+1 to adding autoblock (yes I just created an account due to Bannerlord's lack of autoblock)
He did. He is referring to people who apparently used cheats/trainers/exploits to use autoblock in multiplayer matches which should have been manual only. The autoblock behavior was built into the game client and assholes apparently figured out how to turn it on when and where it should not have been allowed. This is the only reasonable explanation I have heard as to why autoblock may have been removed entirely.Then read at least the thread title. Jesus...
Yes, assuming they wanted to fix the underlying issues with their game code which would have allowed this in the first place or build sophisticated cheat detection. But TW is not Electronic Arts, and they probably didn't have the time, resources, or inclination to do so.I'm sure we can have both autoblock in singleplayer and a way to stop exploits.
He did. He is referring to people who apparently used cheats/trainers/exploits to use autoblock in multiplayer matches which should have been manual only. The autoblock behavior was built into the game client and assholes apparently figured out how to turn it on when and where it should not have been allowed. This is the only reasonable explanation I have heard as to why autoblock may have been removed entirely.
Still, after Fifteen ****ing years and hundreds of dollars, Taleworlds should have the courtesy to spare me (and us) a one sentence explanation.
Yes, best guess is they're throwing the baby out with the bathwater to deal with a multiplayer exploit which targets issues with how they implemented auto block in the first place.so because people break laws we should not have them. Roger that.
Even the suggestion of using a sword and shield is no good for me - I block until I can time a swing so I don't get hit myself, but they block 80% of those hits, and eventually just break my shield. This just should not be this difficult!! (especially playing on the easiest settings!!)
My understanding is that the auto block feature was entirely client driven. There was no option to turn it on in game, but by modifying game files and/or memory editing you could force the game to allow you to do it anyway. And the server, which was hosting the game, had no way to determine that you were using it.I just don't see how they couldn't have had it in the SP by itself, and make it so it wasn't present in the list of options for MP. Surely it wouldn't have been too much a hassle to have removed the option from the settings menu in MP in the first place, and have the anticheating system make sure no one could enable it? Then again, I'm not privy to the details of how such software functions, but still.
The thing is we shouldn't have to hide behind a shield. Autoblock is the default way to play Warband, this is a feature that should of been in at launch. It shouldn't take hours to get a basic grip of the combat. Telling people to just "keep at it" just excuses the Devs for making a bad design decision.Keep at it. I'm sitting behind my shield too. With the new chained attacks and smart positioning i'm able to land more hits.
So make it server-authorative instead of client-authorative. Problem solved without having to screw with the single-player experience.Autoblock in multiplayer where it shouldn't be using a trainer to activate the autoblock code was super common in warband. Good riddance.
95% of warband multiplayer players used shields and thus basically had autoblock.