1.0.0
Compatibility
Changes
ReportCheckView
A powerful moderation system for Minecraft Paper 1.20+ servers, allowing players to report rule-breakers and staff to handle cases efficiently.
Features
🎯 Core Features
- Easy Report Submission - Players can report rule-breakers with a simple command
- Interactive GUIs - User-friendly interfaces for both players and staff
- Category System - Organize reports by violation type (Cheating, Griefing, Chat, etc.)
- Smart Cooldowns - Prevent report spam with configurable cooldowns
- Multi-Language Support - Fully customizable messages in any language
👮 Staff Tools
- Comprehensive Report Management - View, filter, and manage all reports
- Real-time Notifications - Get notified instantly when new reports are submitted
- Report Assignment - Claim reports or auto-assign to available staff
- Action Tracking - Full history of all actions taken on reports
- Quick Actions - Accept, reject, or close reports with one click
🤖 Automation
- Auto-moderation - Automatically take action based on report thresholds
- Smart Notifications - Multiple notification types (chat, title, sound, action bar)
- Auto-close - Automatically close old inactive reports
- Statistics Tracking - Track report trends and staff performance
💾 Storage
- Dual Database Support - Choose between SQLite (default) or MySQL
- Efficient Caching - Fast access to active reports
- Auto-save - Periodic automatic saving
Installation
- Download the latest
ReportCheckView.jarfrom the releases page - Place the JAR file in your server's
pluginsfolder - Restart your server
- Configure the plugin in
plugins/ReportCheckView/config.yml - Customize messages in
plugins/ReportCheckView/messages_en.yml
Commands
Player Commands
| Command | Description | Permission |
|---|---|---|
/report <player> [reason] |
Report a player | reportcheckview.report |
Staff Commands
| Command | Description | Permission |
|---|---|---|
/reportcheck [id] |
Open report management GUI | reportcheckview.staff |
/cases <player> |
View all reports for a player | reportcheckview.staff |
/reportstats |
View report statistics | reportcheckview.staff |
Admin Commands
| Command | Description | Permission |
|---|---|---|
/reportadmin reload |
Reload configuration | reportcheckview.admin |
Permissions
| Permission | Description | Default |
|---|---|---|
reportcheckview.report |
Allow submitting reports | true |
reportcheckview.staff |
Access to staff tools | op |
reportcheckview.notify |
Receive report notifications | op |
reportcheckview.admin |
Administrative access | op |
reportcheckview.bypass |
Bypass cooldowns and limits | op |
Configuration
The plugin is highly configurable. Here are some key settings:
Report Settings
reports:
cooldown: 60 # Cooldown between reports (seconds)
max-active-reports: 3 # Maximum active reports per player
require-reason: true # Require a reason when reporting
min-reason-length: 10 # Minimum reason length
auto-close-days: 7 # Auto-close after X days
Notification Settings
notifications:
sound-enabled: true # Play sound for staff
chat-enabled: true # Send chat messages
title-enabled: true # Show title notifications
notify-reporter: true # Notify reporter when action is taken
Automation Settings
automation:
enabled: true
thresholds:
3:
- "notify:&cPlayer %player% has 3 reports!"
5:
- "command:tempban %player% 1h Multiple reports"
Usage Guide
For Players
-
Reporting a Player
/report PlayerName- Select a category from the GUI
- Choose or provide a reason
- Submit the report
-
What Happens Next
- Your report is sent to online staff members
- Staff will investigate and take appropriate action
- You'll be notified if action is taken (if enabled)
For Staff
-
Viewing Reports
/reportcheck- Opens the report management GUI
- Filter by status (Pending, In Progress, Resolved)
- Click any report to view details
-
Handling a Report
- Click on a report to open details
- Claim - Assign the report to yourself
- Accept - Mark as valid and take action
- Reject - Mark as invalid
- Teleport - Teleport to the reported player
- Close - Close without action
-
Viewing Player History
/cases PlayerName- Shows all reports for a specific player
- Useful for identifying repeat offenders
Database Setup
SQLite (Default)
No setup required! The plugin will automatically create a database file.
MySQL (Optional)
- Edit
config.yml:storage: type: MYSQL mysql: host: localhost port: 3306 database: reportcheckview username: your_username password: your_password - Reload the plugin:
/reportadmin reload
Customization
Adding Custom Categories
Edit config.yml:
reports:
categories:
- Cheating/Hacking
- Griefing
- Your Custom Category
Customizing Messages
Edit messages_en.yml to change any message in the plugin. You can also create new language files (e.g., messages_nl.yml for Dutch).
Building from Source
Requirements:
- Java 17 or higher
- Maven
Build steps:
git clone https://github.com/yourusername/ReportCheckView.git
cd ReportCheckView
mvn clean package
The compiled JAR will be in the target folder.
Support
- Issues: Report bugs on our GitHub Issues
- Discord: Join our support server (link)
- Wiki: Check our Wiki for detailed guides
License
This project is licensed under the MIT License - see the LICENSE file for details.
Credits
- Author: Samuele_NL
- Website: https://samuele.nl
Screenshots
Player Report GUI
Players can easily report rule-breakers with an intuitive category selection interface.
Staff Management Interface
Staff members have access to a comprehensive report management system with filtering and quick actions.
Real-time Notifications
Staff receive instant notifications when new reports are submitted, with clickable messages to view details.
Made with ❤️ for the Minecraft community
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:GiAIwpaN:sfI0m4ks"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GiAIwpaN:sfI0m4ks"
}

