ВЕРСИИ (52)

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Bug Fixes - Fixed jittering when riding into walls (e.g. with a horse) due to client-side hitboxes still being deflated for client authoritive entities

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added full support for 26.3 - New jar! Mojang rewrote the interpolation code again! - Added `applyVelocityForInterpolated` setting - If disabled, entities with interpolation will not have velocity applied client-side - Enabled by default, though it may cause jittering for interpolated entities in 26.3. - Added a partial fix for [MC-311974](https://mojira.dev/MC-311974) - In technical detail, the `updateInterval() + 1`, `advance()` movement and `currentStepTicks = 1.0F -> 0.0F` fixes have been implemented - The rest of the issues with the new stepped interpolation handler remain as Anti-Smooth simply just resorts to the old linear interpolation handler for entities that have update packets sent every tick. ## Changes - Reworked the `unaffectedEntities` setting - The default value is now an empty list - The former default value of this setting is now a hardcoded list - This new list can be disabled with the `disableDefaultUnaffectedEntities` setting - The `applyVelocity` setting now only applies when the affected mob is not being interpolated ## Bug Fixes - Fixed interpolation steps in 1.21.5+ always being set to 1 regardless of settings - Fixed interpolation conditions being really messy

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Additions - Added support for 26.3 Snapshot 7 ## Bug Fixes - Fixed incompatibility with Moonrise - Fixed far away entities being jittery due to client-side velocity being erroneously applied to them

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Added every type of minecart and boat to the default list of unaffected entities

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

## Changes - Velocity no longer gets applied to leashed mobs in 1.21.6+ - This is due to mobs falling down and rubber banding whenever they are meant to be stationary - Resolves [#2](https://codeberg.org/BlueStaggo/anti-smooth/issues/2), though admittedly the solution isn't very glamorous - Added minecarts to the default list of unaffected entities ## Fixes - Fixed mobs clipping through walls by shrinking their hitboxes client-side during solid collision detection (Resolves [#1](https://codeberg.org/BlueStaggo/anti-smooth/issues/1))

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

# Fixes - Fixed support for Fabric 1.21.9-1.21.11 - Fixed support for NeoForge 1.21.11

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

This is the 2.0.0 release and it is called this way because there are a few breaking changes for the config! ## Additions - Added an "applyVelocity" option that makes velocity get applied client side. Set to true by default. - Added an "unaffectedEntites" option in the config which forcibly enables interpolation and disables client-side velocity for some entities. By default, "minecraft:item" is included. - Added an "interpolation" setting that controls whether interpolation is applied or otherwise entity position update packets are sent every tick: - "disabled": Interpolation is always disabled - "multiplayerOnly": Interpolation is only enabled on multiplayer - "enabled": Interpolation always enabled - The "minInterpolationDist" setting bypasses this as entities will still be interpolated when they are out of range. Set this to zero to disable this behavior. ## Changes - Renamed "checkDistance" to "minInterpolationDist". - The codebase now uses Modstitch and Stonecutter (this means no more Git branch spaghetti). - As a result, the repository has been moved to https://codeberg.org/BlueStaggo/anti-smooth. ## Fixes - 26.2 is now supported ## Removals - Removed the "instantKnockback" setting as it has been superseded by the "applyVelocity" setting. - In actual fact, I did this because I didn't want to make another set of jars for 26.2. :P

Initial release

Initial release

Initial release

Initial release

Initial release

Initial release