Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last month
All versions
2.2.0
Release
Better WebConsole 2.2.06 months ago 17
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Added simplified production-ready
config.ymlwith clearer names and comments. - Added
commands.blockedto block risky commands from the web console and aliases. - Added
commands.aliaseswhile keeping legacyaliasescompatibility. - Added command aliases:
/bwconsole,/betterconsole. - Added management subcommands:
/bwc setpassword <user> <new-password>/bwc logoutall <user>
- Added extra subcommand aliases:
useradd,createuser,deluser,deleteuser,users,passwd,password,killsessions. - Added JUnit tests for config parsing, safe fallback values and blocked commands.
- Added competitor audit and roadmap notes in
docs/competitor-audit.md.
Changed
- Removed default destructive
restartweb alias from the generated config. - Moved aliases under
commands.aliasesfor a clearer config structure. - Invalidating user sessions now happens when removing a user or changing their password.
/bwc statusnow shows alias and blocked-command counts./bwc reloadmessage now clearly states which settings still need a server restart.- API reads the latest plugin config after reload for aliases, logging and cookie settings.
- Maven compiler annotation processing is disabled to avoid noisy JDK warnings.
Security
- Web command blocking now applies both to direct commands and alias-expanded commands.
- Alias chains are limited to 10 commands.
- Kick/ban web actions validate player names and sanitize reasons.
logging.audit-log: falsenow disables all audit writes consistently.- Optional
security.secure-cookiesadds theSecurecookie flag for HTTPS deployments.
Fixed
- Fixed broken encoding text in source/config/docs touched by this update.
- Fixed stale API config snapshot after
/bwc reload. - Fixed sessions remaining active after password change or user removal.
Full Changelog: https://github.com/AREKKUZZERA/better-web-console/compare/2.0.0...2.2.0
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:khtebxzn:AqLYqgbE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:khtebxzn:AqLYqgbE"
}

