ВЕРСИИ (389)

Add support for MC 26.3

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Fix config commands not working

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Upgrade to CyanLib 2.1.0-beta.1

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Initial release of the mod rewritten in Kotlin, to make my life easier when developing in the future > As a note for people like me who hate generative AI, no generative AI was used to port the code. > This rewrite was done by first using IntelliJ IDEA's translate on copy (basically when you copy Java code inside a > Kotlin file it translates it automatically). Then, I changed manually the types and code where it was necessary > (many places sadly), to make sure the behavior stayed the same. > And lastly, I used Kotlin's constructs where possible to optimize and make the code more readable

Add support for MC 26.2

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

Update to CyanLib 1.1.1, as it fixes a bug preventing the movement detection from working

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

- Fix bug where the dimensions nether and end were not named properly, resulting in an error when teleporting to them after upgrading a world from or to 26.x - Update to CyanLib 1.1.0

Add support for MC 26.1.2

Add support for MC 26.1.1

- Bump ModMenu version, as it fixes a bug - Add support for MC 26.1

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

Bump ModMenu version, as it fixes a bug

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- When typing the `home-trust` command, already trusted players names will no longer be suggested - Improved error handling (multiple places just threw errors instead of handling them, resulting in a crash whenever the error happened) - Fix some potential concurrency issues

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Update to the latest CyanLib version, which fixes potential concurency issues - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

- Add support for MC 1.21.11 - Update dependencies versions

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.10

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.9

Add support for MC 1.21.8

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.7

Add support for MC 1.21.6

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

- Backport to `1.19.2` and `1.19.3` - Add support for `1.20`, `1.20.3` and `1.20.5` (you should use `1.20.1`, `1.20.4` and `1.20.6` respectively instead but if for whatever reason you cannot, there you go) - `fabric.mod.json` now specifies the minimum required version for `fabric-api` for version that support multiple MC versions (ex: `1.20-1.20.1` will set the minimum `fabric-api` version to `1.20` instead of `1.20.1`) - 🚧 This version is marked as `beta`, there may be some bugs due some refactoring that I did (which I tested, but I may have missed a bug or two)

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Update to CyanLib 1.0.6

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Add the possibility to set a cooldown before players teleport

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix home files duplicating when they belong to a bedrock player that joined via Geyser

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix build issues + Use CyanLib 1.0.5

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Fix `tpInCombat` option being inverted

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

Add the possibility to disable teleportation when in combat. This can be tweaked with the following options: - `tpInCombat`: `true` or `false` - `combatTimeoutSeconds`: the duration in seconds of combat mode after taking or doing damage

- Put dependencies in `fabric.mod.json` so that when one is missing, the fabric loader writes a clear message of what is missing instead of just a ClassNotFoundException - Bump versions - Add missing translations

- Put dependencies in `fabric.mod.json` so that when one is missing, the fabric loader writes a clear message of what is missing instead of just a ClassNotFoundException - Bump versions - Add missing translations

- Put dependencies in `fabric.mod.json` so that when one is missing, the fabric loader writes a clear message of what is missing instead of just a ClassNotFoundException - Bump versions - Add missing translations