Tags
Creators
Details
1.0.2
Compatibility
Changes
Announcing AntiSpoof v1.0.2: Advanced Client Spoof Detection for Minecraft
I'm excited to present the first official release of AntiSpoof! This powerful Minecraft plugin gives server owners unprecedented control over detecting client modifications used by players.
What Does AntiSpoof Do?
AntiSpoof provides robust tools to detect and respond to client spoofing attempts through:
- Client Brand Analysis: Block/whitelist specific client brands (Fabric, Forge, etc.) and detect suspicious formatting
- Channel Monitoring: Verify vanilla clients and implement channel whitelist/blacklist systems
- Bedrock Integration: Seamless Floodgate API support with fallback to prefix verification
Key Features
- Multiple Detection Methods: Various checks can be enabled/disabled independently
- Configurable Response System: Customize actions for detected spoofing attempts
- Bedrock Player Handling: Special modes for cross-platform compatibility
- Admin Tools: In-game commands to inspect and monitor player clients
- Debug Mode: Detailed logging for troubleshooting false positives
Important Notes
While AntiSpoof enhances security, it's not foolproof. Experienced players can potentially spoof client details to bypass detection (ironic, I know!). By default, the plugin only checks whether a player claiming to use 'vanilla' has registered plugin channels, something impossible on a true vanilla client.
Server Requirements
- Java 21+
- Spigot/Paper 1.20.4+
- PacketEvents 2.7.0 (included in the jar)
Optional dependencies include Floodgate (for Bedrock support), PlaceholderAPI, and ViaVersion/ViaBackwards.
Getting Started
- Download the plugin jar
- Place it in your server's plugins folder
- Restart your server
- Configure via the generated config.yml file
Check out the [GitHub repo] for complete documentation and support!
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:DMd5Nhpw:21vrZSkP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DMd5Nhpw:21vrZSkP"
}

