Links
Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 2 weeks ago
All versions
1.2.0+1.21.8
Release
StaffSee - Server Moderation 1.2.0 for 1.21.7–1.21.82 weeks ago 10
Compatibility
Minecraft: Java Edition
1.21.7–1.21.8
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
New
- Bans:
/ban <player> [reason],/tempban <player> <duration> [reason]and/unban <player>. They replace the vanilla/banand/pardon(which now works like/unban), use the normal ban list (sobanned-players.jsonand the vanilla ban screen keep working) and are logged tobans.txt. Offline players can be banned too. /history <player> [page]: one paged list with all warns, mutes, kicks, freezes, bans and reports of a player, newest first. Shows if the player is banned right now./history <player> chests [page]: when ChestSee is installed, shows the player's container activity from the ChestSee logs. Click an entry to open it with/chestsee lookup. ChestSee stays optional.- Discord webhook: set
discordWebhookUrlin the config to get reports in a Discord channel. WithdiscordPunishmentswarns, mutes, kicks, freezes and bans are sent as well. Messages are sent in the background and never ping anyone. /vanish: hides you from the tab list and the world for normal players, with no join/leave messages while vanished. Other staff still see you. Vanished players are also left out of/list, the player count and player list in the server list, and name suggestions in commands. Stays on after relogging and restarts.- Staff chat:
/sc <message>sends a message to staff only,/sctoggles it so normal chat goes to staff. Works while muted. - New permission nodes
staffsee.vanish,staffsee.vanish.seeandstaffsee.staffchat. Without a permission mod they followstaffsee.moderate(OP level 2).
Changes
- The config file is rewritten on start, so new options show up in existing configs. Your values are kept.
Optional dependencies
Any compatible version
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:bR7GxU9W:zOfWur8d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bR7GxU9W:zOfWur8d"
}

