Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
All versions
2.7.3-Legacy
Release
AnarchyExploitFixes 2.7.3 (Legacy)last year 95
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
Platforms
Paper
Purpur
Required content
Any compatible version
Changes
- Added Version support up until 1.21.4 (#247)
- Added patch for the 1.20.6-1.21 book dupe
- Added patch for a new exploit that allows sending huge messages, creating lag on some servers
- Fix functionality for some packet modules
- Fix AntiBedTrap not working properly (#244)
- Added ability to hook into luckperms to fix #237
- Reworked
preventsions.prevent-opped-playersto a more configurablepreventions.illegal-permissions - Reworked
preventions.prevent-non-survival-playersto a more configurablereventions.illegal-gamemode - Added more configurability to all
regional-activitymodules. You can now configure custom type limits per module - Reworked legacy module
disable-fishinto a more genericlag-preventions.disable-entity-spawnsfor both plugin types. - Reworked all modules accessing chunks to check if a chunk is out of bounds to fix the "plugin is getting faraway chunk issue"
- Reworked
chunk-limits.exp-bottle-limitintochunk-limits.projectile-limitsince its a projectile issue and could reappear - Improved functionality of all modules handling illegal items. (Fixes having to drop something multiple times until aef removed ALL illegal enchants. It now cleans it entirely on the first interaction if handling is set to ACTION or STRICT. Also fixes items getting stuck if players try to drop them with specific plugin settings.)
- Improved plugin enable logic and added more specific logging messages so users are more pushed into using the correct plugin jar
- Plugin now only saves default translations if the lang folder does not exist. This means you can delete language files you do not want without them reappearing on reload.
- Reworked config to always include the enable: true/false option for a module. This will cause warnings on config update but should be fine after a reload.
More fixed issues in this release: #248 #243
Reminder to always backup your configs before you update!
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:pILEwgSo:aT2xedhL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pILEwgSo:aT2xedhL"
}
