Tags
Creators
Details
0.3.0
Compatibility
Changes
JanusMCD v0.3.0 - The "Panopticon" Update
I been hard at work behind the scenes, and this update brings a massive leap in server intelligence and security. Here's what's new:
New Feature: The Panopticon
This feature requires TartarusPunishments and an upcoming release called "Jupiter Administration"
Trust Scores: Instantly see a player's reliability rating (0-100) based on their history. This is an active calculation over time. Activity Graphs: View a visual sparkline of their login activity over the last 30 days. No more guessing if they're active! Forensics: Check their last known IP, verify if they're using a VPN, and see potential alt accounts. Command: simply run /investigate <player>
Deep Ecosystem Integration
Janus now talks directly to other plugins for a seamless experience:
Jupiter Administration: View live renders of player inventories, armor, and ender chests directly in Discord! You can even browse their NBT data or check quarantined items.
Tartarus Punishments: Access a player's full criminal record and staff notes instantly. Need to take action? Ban, Kick, Mute, or Freeze them with a single click of a button.
Rock-Solid Stability
Sync-Lock Protocol (VELOCITY): Prevents "split-brain" issues by locking player actions until data is fully synced across servers.
Paper & Folia Support: Added native support for modern chat rendering, ensuring your chat looks crisp and clean on the latest server software.
Security Upgrades
Resolved an issue where filling in console.channel.role.id did not release control to users with said role. This didnt cause a security issue as this was fail-closed, it blocked everything in the console. Security preserved.
Optional dependencies
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:kyiSeeUV:ZkdQUWdi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kyiSeeUV:ZkdQUWdi"
}

