ВЕРСИИ (118)

Fixed ScalableLux compatibility.

Fixed only launching specifically on MC 26.1 and not on 26.1.1 or 26.1.2.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

2nd attempt to fix the same bug that the previous release was supposed to fix. At least I tested it this time though.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fixed crash on startup that would sometimes occur when running on neoforge via sinytra connector.

Fix compatibility with Sable. Since Sable only exists for MC 1.21.1, I've only provided a fix for this MC version. For all other MC versions, Vertigo V1.2.1 is still the latest.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Fixed classloading some of Minecraft's classes too early and breaking mods which mixin to them.

Ported to MC 26.1.

Support MC 1.21.11. No code changes were required for this release.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Fix a lot of things exploding catastrophically after players respawn.

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

* Switch to vanilla method of removing block entities when chunk sections unload on the client. Maybe this will fix an issue that shouldn't ever happen to begin with?

Ported to MC 1.21.9 and MC 1.21.10.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Possibly fixed crash that should never happen but could maybe be explained by other mods calling setBlockState() on the wrong thread? * Also added a java argument to debug issues like these: `-Dvertigo.traceWrongThreadForSetBlockState=true` will log a stack trace whenever another mod does this.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

* Fixed race condition when changing dimensions or respawning causing chunks to successfully load initially, but future block updates to fail. * In particular, this bug meant that the player would not be able to interact with blocks until relogging. * Fixed potential issue syncing block updates when there's more than one player nearby on the server.

Support MC 1.21.8.

Support for MC 1.21.7.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Port to MC 1.21.6. * Fix chunks not loading after respawning.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Ported to MC 1.21.5. * For mod developers: Fixed VertigoServerEvents.SECTION_UNLOADED sometimes firing after the unload packet is sent, when its contract clearly states that it should be fired before.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways.

* Fixed crash that could happen when changing dimensions in very specific ways. * Marked 1.20.1 jar as also compatible with 1.20.0.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

* Fixed compatibility with ScalableLux, Valkyrien Skies, and AntiXray. * Marked 1.21.3 version as also being compatible with 1.21.2 (un-tested, use at your own risk). * Ditto for 1.21.1 -> 1.21, 1.20.6 -> 1.20.5, and 1.20.4 -> 1.20.3. For mod developers: * Added a new API method to query whether a player is tracking sections or chunks. * In singleplayer, this always returns true. * In multiplayer, this only returns true if the other side has a version of Vertigo installed which has a compatible packet protocol.

Initial release.

Initial release.

Initial release.

Initial release.

Initial release.

Initial release.

Initial release.