1.2.2
Compatibility
Required content
Changes
Downed Gun Lock v1.2.2
This update improves server-side security and the reliability of team-wipe handling.
Changes
- Added server-side validation to reject unverified effect requests sent by modified clients
- Prevents forged requests such as fake firing effects
- Attachment changes and related screen requests are now rejected server-side while the player is downed
- Fixed an issue that could incorrectly remove give-up restrictions or reset screen states when:
- Multiple teams were being checked for a wipe at the same time
- A player moved between those teams during the process
- Improved internal state management and processing safety
Important
Update both the client and server to v1.2.2.
The network protocol remains compatible with v1.2.1, but updating all clients and servers is recommended to ensure the new server-side security protections are fully enabled.
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:zdd2bL9p:b1yqajMx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zdd2bL9p:b1yqajMx"
}



