All versions
1.0.0
Release
NexbyteWeb 1.0.04 months ago 49
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Folia
Paper
Purpur
Changes
1.0.0 — Initial Release
First public release of NexbyteWeb — a live localhost web panel for Minecraft server management.
Dashboard
- Real-time TPS, MSPT, RAM, and CPU monitoring
- TPS and RAM history sparkline charts
- Performance warnings for low TPS and high RAM usage
- Online player chips with ping and gamemode
- Server info: Minecraft version, platform, Java version (21–25), uptime, web port
- MOTD, plugin list, world list, and recent console logs
- Automatic
server-icon.pnglogo in panel header - WebSocket live updates (no page refresh)
Player Management
- Searchable online player list with modern card UI
- Player detail panel: health, hunger, ping, gamemode, location, IP (configurable)
- Custom inventory viewer: armor, hotbar, main inventory, off-hand
- Item durability bars, enchantments, and bundled 1.21.x textures
- Interactive 3D skin preview
- Ender chest viewer
- Quick actions: heal, feed, kill, kick, gamemode change
Server Actions
- Whitelist add/remove
- Weather control (rain / clear)
- Time control (day / night)
- Action log with timestamps
Platform Support
- Paper, Purpur, Folia, Spigot, and Bukkit
- Minecraft 1.21.x
- Java 21, 22, 23, 24, and 25 (auto-detected)
- Folia region-safe schedulers
Optional Plugin Integrations
- AuthMe — registration status, last login, IP
- LuckPerms — groups and permissions
- SetHome / HomePlugin — player homes
- Essentials — homes and ban history
- GrimAC — violation levels per check
Configuration
- Full
config.ymlwith toggles for every feature and action - Configurable web port with auto port-finding
- Localhost-only binding (
127.0.0.1) by default - Turkish and English UI language toggle
Install
- Drop
NexbyteWeb-1.0.0.jarintoplugins/ - Start the server
- Open
http://127.0.0.1:8765in your browser
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:v4Fw9DZl:PzkD9R6c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v4Fw9DZl:PzkD9R6c"
}

