1.0.0
Compatibility
Changes
π CommandSpyPlus
A powerful, modern, and secure command monitoring system for staff.
CommandSpyPlus is a lightweight yet advanced plugin designed to give server administrators full visibility over player command usage β without spam, clutter, or performance impact. Built for serious servers, it provides intelligent filtering, clean formatting, and deep customization.
β¨ Features
π§ Smart Command Monitoring
- See commands executed by players in real-time
- Optional filtering (ignore specific commands or players)
- Clean, readable format β no spammy logs
π Permission-Based Access
- Full integration with permission systems like LuckPerms
- Separate permissions for:
- Viewing commands
- Bypassing spy
- Admin controls
βοΈ Fully Customizable
- Edit messages, formats, and colors in language.yml
- Configure behavior in config.yml
- Choose which commands to track or ignore
π§Ή Anti-Spam System
- Prevents flooding staff chat
- Optional cooldown between repeated commands
- Grouping system for repeated actions
π Advanced Filtering
Ignore commands by:
- specific players
- command prefixes (/msg, /login, etc.)
- Whitelist / blacklist support
π Toggle System
- Staff can enable/disable spy mode with a command
- Saved per player (persistent across restarts)
β‘ Lightweight & Optimized
- Minimal performance impact
- Async-safe logging system
- Designed for high-player servers
π§Ύ Commands
/commandspy
β Toggle command spy
/commandspy reload
β Reload configuration
π Permissions
commandspy.use
β Use command spy
commandspy.admin
β Reload config
commandspy.bypass
β Commands wonβt be shown to others
π§© Compatibility
- Supports Paper / Spigot (1.20+ recommended)
- Works perfectly with LuckPerms
- Compatible with most server setups
π Why CommandSpyPlus?
Unlike basic command spy plugins, CommandSpyPlus focuses on:
- clarity over spam
- control over noise
- performance over bloat
Itβs built for real servers β not just simple setups.
β€οΈ Support
If you need help or want to suggest features, feel free to reach out.
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:qKswkjrg:XrWCSYKH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qKswkjrg:XrWCSYKH"
}

