1.0.0
Compatibility
Changes
sChatManager turns off chat completely and blocks commands by blacklist. There are no permission nodes and no bypass logic — the block applies to everyone equally.
Features
- Disable player chat server-wide with one config flag
- Block commands by blacklist, or block every command at once
- Customizable response messages, single-line or multi-line
&color codes, plus&#RRGGBBhex colors on 1.16+- Empty message means the action is blocked silently
Compatibility
One jar for 1.8 through 26.2, Spigot and Paper alike.
Chat is intercepted through Paper's AsyncChatEvent where it exists and through
AsyncPlayerChatEvent everywhere else — the plugin picks at startup and logs the choice.
Nothing version-specific is a hard dependency, so no separate builds are needed.
Java requirements are whatever your server version already needs: Java 8 for 1.8, Java 25 for 26.2.
Setup
- Put
sChatManager-1.0.0.jarintoplugins - Start the server once to generate `plugins/sChatManager/con
- Edit it and run
/schatmanager reload
chat:
enabled: false
message: "&cЧат на сервере отключён."
commands:
block-all: false
blacklist:
- "msg"
- "tell"
message: "&cЭта команда заблокирована."
Blacklist entries ignore case, a leading / and a namespace prefix, so tell, /tell and
minecraft:tell are the same thing. An entry with a space mat
gamemode creative blocks /gamemode creative Steve but not /gamemode survival.
Notes
/schatmanager reload(aliases/scm,/schat) is availabrs. It is an op check, not a permission.block-all: trueblocks literally every player command, including ones from other plugins such as/spawnor/tpaccept. Only/schatmanagerstays available, otherwise blocking could not be turned off from in-game.
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:vRs2xrUB:AnViUEqM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vRs2xrUB:AnViUEqM"
}

