You don't have to reset your configuration, all of the new values default to what the old values were if they don't exist, so it should be completely backward-compatible with old configurations without any problems.
- Added the MaxChunksPerIntervalMult to the X-Ray blocker. Basically, people flying at extremely fast speeds (e.g. flight with speed 10) could cause a lot of lag to the server by loading tons of new chunks. The MaxChunksPerIntervalMult aims to solve the problem by only loading MaxChunksPerIntervalMult chunks per task.
- LowVelocityAllowedSpeed, MidVelocityAllowedSpeed, and HighVelocityAllowedSpeed have been added. These values were originally hard-coded and are the speeds player can move at with a drawn bow. I saw no reason not to allow users to configure them, so, here you go!
- Water should now be compatible with higher speed values (e.g. /speed 10 from essentials).
- Water accounting has been changed to be a bit more strict.
- Fixes a bug where NoSlowdown with sword block wasn't blocked (e.g. in 1.8 when you right click with a sword to block an attack).
- Fixes a potential issue where criticals false positives could occur when the player is standing in water or lava.
- Removed some spam from /anotify.
- Made accounting for webs in AntiKnockback a bit more lenient to avoid false positives around webs.
- Fixes a console error that would occur if a player was damaged and then immediately changed worlds.
- Fixes a bug where the speed task could execute a tick late, causing drag-backs to be more likely (basically the task used to round up to a tick, but it now rounds down to a tick)
- Changed the default X-Ray configuration. It was hiding blocks too slowly, and this aims to solve that.
- Adds a MaxHeightOffGround to the Flight configuration, which defaults to 1.4 and is the maximum height a player can be hovering above the ground. Originally this was hard-coded to 2.0, meaning people could hover 2 blocks above the ground without being dragged back - This also allowed them glide high enough to avoid taking damage from melee mobs.
- SpeedLeniency changed to 0.35 by default, just to help the people who aren't knowledgeable enough to touch a configuration.
Spider checks if players are going upward.
Flight checks if players are in the air for too long.
Should I rename the "Spider" check to "Flight", and the "Flight" check to "Glide"?
Again, just minor bugfixes this time. There are plans for a new killaura check for detecting killauras with lots of mobs (if you hadn't noticed, surrounding yourself with mobs and hitting them means you won't get detected), and also plans to improve the XRay blocker's performance.-
- Fixes a bug where the BreakSpeedIgnore option not always working correctly on certain blocks, causing FastBreak false positives.
- The Speed check has had it's default configuration changed to be more lenient.
- Spider's default maximum height has been changed from 1.30, from 1.25.
- The Speed check now lowers in time as well as from legitimate actions, lowering every LowerAmount per second.
- An AntiAura exploit where hacked clients could cause lag on a server by doing a certain specific action has been patched.
- Tries to fix a really rare crash bug that only a few specific people seem to have had.
I haven't changed the version number mostly because these things should have been fixed last update. Sorry about that!
- Fixes bugs with cobblestone walls. I forgot to add them to my fence list, which could cause false positives and bypasses related to them.
- Attempts to fix bugs in PVP related to players being hit upwards being dragged back by the Spider check.
- Added FlatLeniencyInBlocks to VelocityAccounting to help with the launcing leniency in the Spider check.
There were some problems introduced in the last version with fences, so I took a ton of time on them this time. I have solved the majority of things you can spider up. For example:
- SpeedLeniency changed to 0.15 by default. The old default of 0.10 could cause semi-rare drag-backs in normal gameplay.
- Drag-backs when jumping on fences have been fixed.
- Fixes a bug where players could still successfully spider up fences. If you can still spider up fences, make sure MaxHeightOffGround is at 1.25, even though spidering up fences should still be blocked if MaxHeightOffGround is at 1.45.
- Default MaxHeightOffGround set to 1.25 from the previous default of 1.45.
- The configuration comments have been re-done to be more clear, as well as to add an introduction. Notably, "people" is changed to "players".
- Extra leniency added to the ESP check to attempt to stop mobs flicking away when they get a small amount of cover.
- Added NormalVelocityLeniency and CombatVelocityLeniency to the default config, which allows you to modify the leniency given to velocities. CombatVelocityLeniency is for PVP velocities, and defaults to 2.0. NormalVelocityLeniency is for non-PVP velocities (e.g. launchpads), and defaults to 1.1. Previously, the value was hard-coded to 1.1, however some servers have experienced problems during PVP, hence why I have allowed users to give more leniency.
The fences and the iron bars in the picture could sometimes be spidered upon with the last update, but it won't be possible to do that after this update.
I am aware of some blocks not being accounted for yet. For example I know player heads and carpets:
Can still be spidered upon. I will work on these ASAP but as each block is different, I have to do a surprising amount of work to add compatibility for each block. As stacked iron bars and fences are much more common on popular servers, I decided to work on those first as opposed to working on vague blocks like carpets.
As I say, I've spent a ton of time on this, to make sure it's working as seamlessly as possible.
@EthanTheGamer Has very kindly helped me out with the configuration, as well as discord. I thank him very much for that.
Do you need help? Join our discord server for chance at FREE VIP!