Tags
Creators
Details
2.0.1
Compatibility
Changes
SunshineCommandGuard 2.0.1
Privacy fix for the Live Web Editor. Recommended for everyone who uses /cmdguard editor.
Fixed
/cmdguard editorno longer uploads secrets. Yourpro-keyandmonitoring.discord.webhook-urlare blanked beforeconfig.ymlis sent to the web editor./cmdguard applyputs your local values back, so applying a web config never wipes them. A value you type into the web editor still wins./cmdguard editorrefuses to upload aconfig.ymlthat is not valid YAML and tells you to fix it first, instead of sending the raw file.- Commands from your server now show up in the web editor. Before, the editor could fall back to its demo command list.
If you ran /cmdguard editor on 2.0.0 with a Discord webhook configured, create a new webhook in Discord and replace the old URL.
This release also contains everything from 2.0.0:
2.0.0
Migration, integrations, a Live Web Command Editor, and execution-level argument filtering.
Upgrade notes
- Argument rules now block execution.
argsrules previously filtered only tab-completion; starting in 2.0.0, the first argument of an allowed command is checked when it runs as well. Review yourargssections and test with/cmdguard test <player> <command> <arg>before upgrading a live server. - API:
BlockReasonhas a new constant,ARGUMENT_RULE. - Existing
config.ymlfiles continue to work without changes.
Added
- Live Web Command Editor (
/cmdguard editor&/cmdguard apply <code>): uploads your server's registered commands and currentconfig.ymlto https://sunshine-mc.net/en/cmdguard/ so you can allow, hide, or block commands per group in your browser and apply them live with automatic backup (includes a 3-day free trial per server, then unlocked with apro-key; manual YAML export is always free). /cmdguard import commandwhitelistreadsplugins/CommandWhitelist/config.ymland writes a reviewableconfig.imported.yml: groups, commands, and blocked sub-commands asargsdeny rules, plus the LuckPerms commands to grant each group.config.ymlis never touched.- Discord alerts for blocked attempts via webhook (
monitoring.discord): per-player cooldown, per-minute cap, rate-limit (HTTP 429) back-off, mentions disabled, and anonly-reconnaissancemode that posts only/plugins,/version, and namespaced probes. The webhook URL is never written to the log. - PlaceholderAPI placeholders:
%cmdguard_group%,%cmdguard_visible%,%cmdguard_filter%. They read cached data only, so they are safe on asynchronous scoreboards. - Folia support (
folia-supported: true). Per-player work runs on the player's own scheduler on Folia; behavior on Paper is unchanged. /cmdguard test <player> <command> [args...]shows whether the argument rule allows the first argument.
Fixed
- Security:
argsdeny/allow rules are enforced on execution, including namespaced forms (/minecraft:gamemode creative) and/execute ... runpayloads.
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:8VJdBwMc:wgdbqbOK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8VJdBwMc:wgdbqbOK"
}

