1.1.0
Compatibility
Changes
Changelog
All notable changes to Slash Report (BungeeCord / Velocity Port) are documented in this file.
[1.1.0] — 2026-08-10
v1.1.0 release. Initial BungeeCord/Waterfall/Velocity proxy port of ReportPlugin. Provides network-wide report aggregation, proxy commands, cross-server staff alerts, and Discord bot integration.
Added
Proxy Platform & Architecture
ReportProxyPlugin— Main entrypoint extendingnet.md_5.bungee.api.plugin.Plugin.bungee.yml— BungeeCord plugin descriptor file.- Velocity proxy support via BungeeCord compatibility layer (
bungeecord-plugin-compat = trueinvelocity.toml).
Plugin Messaging & Cross-Server Pipeline
ReportMessageListener— Intercepts forwarded report packets (reportplugin:report) on theBungeeCordchannel sent by backend Paper servers.reportplugin:notifysubchannel broadcast — Pushes staff notifications to all backend Paper servers so online staff members see alerts regardless of which server they are connected to.- Origin server tracking (
origin_server) stored in DB and displayed in commands and Discord embeds.
Discord Bot Integration
- JDA 6.5.0 bot running on the proxy that posts a rich embed for every new report across the network.
- Interactive Claim and Resolve buttons restricted to a configured Discord staff role.
- In-place embed updates when report status changes (claimed → resolved).
- Server field in Discord embed showing which backend server originated the report.
Data Layer
- MySQL support (
MysqlReportRepository) — Recommended primary storage for multi-server proxy deployments. - SQLite support (
SqliteReportRepository) — Single-node proxy storage option with WAL mode enabled. ReportRepositoryinterface for clean storage abstraction.origin_servercolumn added to schema for server traceability.
Configuration (config.yml)
- Discord bot credentials section (
bot-token,channel-id,staff-role-id). - Customisable report reasons list (drives tab-completion).
- Configurable
cooldown-secondsandduplicate-window-seconds. - Storage configuration section (
type: mysql | sqlite) with full MySQL parameters. - Localizable
messagessection for all player-facing strings with color-code support (&-style codes).
Permissions
| Node | Default | Description |
|---|---|---|
report.report |
true |
File reports |
report.staff |
op |
View/manage reports + receive alerts |
report.immune |
false |
Cannot be reported |
Roadmap (Planned — Not Yet Released)
The following features are tracked for future versions:
| Feature | Target Version |
|---|---|
Velocity-native plugin API (com.velocitypowered.api) without BungeeCord compat |
v1.3.0 |
| RedisBungee integration for multi-proxy synchronization | v1.3.0 |
Discord-side slash commands (/reports in Discord) |
v1.4.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:k6OrOvgc:jkjIDus5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k6OrOvgc:jkjIDus5"
}

