Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last month
All versions
2.4.8
Release
Better WebConsole 2.4.84 months ago 19
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Added a fallback
/api/statspolling path in the web UI so dashboard data can recover when WebSocket stats are delayed or unavailable. - Added tests for absolute session lifetime expiry behavior.
- Persistent TPS/RAM/CPU/player history storage in
server-stats-history.tsv. - New authenticated endpoint:
GET /api/stats/history. - Dashboard range selector for
1h,6h,24h, andall. - Offline player roster, offline profile lookup, and last-seen display.
- LuckPerms rank/prefix display via soft dependency.
- Config options for stats history retention, API max points, and write interval.
Changed
- Added an absolute web session lifetime limit in addition to the idle timeout.
- Added
security.session-max-lifetime-minutestoconfig.ymland README examples. - Set the session cookie
Max-Agefrom the absolute session lifetime so browser cookies and server-side sliding sessions stay consistent. - Matched unknown-user dummy bcrypt verification cost to real password hashes.
- Updated
/bwc reloadmessaging and docs to mention that session max lifetime changes require a server restart. - Dashboard charts now render persisted/downsampled history.
- Player models support online/offline state, rank metadata, and activity counters.
- Paper
26.1grouped artifact renamed from26.1.Xto26.X. - Project version bumped to
2.4.8.
Fixed
- Restored normal login form submit behavior for browser autofill, password managers and automation.
- Cleared the password field after a successful web login.
- Warned server owners when the web panel listens on all interfaces without secure cookies or an IP whitelist.
- Ensured loaded persisted sessions are rejected when they exceed the absolute lifetime, even if their idle timeout has not expired.
Full Changelog: https://github.com/AREKKUZZERA/better-web-console/compare/2.4.6...2.4.8
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:BId5sjfn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:khtebxzn:BId5sjfn"
}

