Tags
Creators
Details
1.1.0+paper.26.1.1
Compatibility
Changes
ByteBans 1.1.0 beta adds IP bans and mutes, warnings, staff notes, history lookup, and player freeze/unfreeze commands. New installations use SQLite by default; existing MySQL configurations and punishment records remain supported through a schema migration. Console-only permanent history deletion remains available, and undo actions retain an audit entry.
Optional Discord webhook notifications and a token-protected local admin page are disabled by default. Enabling the webhook sends moderation details, potentially including IP addresses, to the Discord endpoint the server administrator configured. The admin page listens on the server's loopback address and supports moderation actions and history search.
The primary release JAR passed all 30 pinned Paper server probes across 15 Minecraft versions and all 28 pinned Purpur probes across 14 versions, from 1.21 through 26.3. The Paper-only 26.1.1 JAR contains the same classes and resources with a distinct manifest marker, and it passed separate exact-JAR online- and offline-mode Paper probes. These servers exercised synthetic Bukkit login, chat and movement events. Real offline-mode TCP clients separately checked login, IP bans, IP mutes, freeze and unfreeze on Paper 1.21, 1.21.4 and 1.21.11 and Purpur 1.21 and 1.21.11. The optional admin page passed HTTP and SQLite checks on Paper 1.21.4 and Purpur 26.2. The synthetic online-mode runs did not include an authenticated Minecraft account. Purpur has no build for 26.1.1, so that version is listed for Paper only; Bukkit and Spigot remain unverified for this release. Paper builds for 1.21.5, 1.21.9, 26.1.1 and 26.3 are experimental.
Provenance: substantial code in this update and these release notes are AI-generated. Modrinth's AI-generated code and text disclosures must be applied before upload. This beta is unlisted unless the project owner provides a truthful human review establishing eligibility for public listing.
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:ysEBBeJv:yDNstXxC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ysEBBeJv:yDNstXxC"
}
