Tags
Creators
Details
0.3.3
Compatibility
Changes
[0.3.3] - 2026-03-23
⚠️ Configuration Update Required ⚠️
To take advantage of the new STATIC and SLASH_ONLY Linking Modes, as well as customize Slash Command cooldown limits, please backup and delete your current plugins/JanusMCD/account-linking.yml so the server generates a fresh configuration file containing the newly implemented variables!
Added
- Linking Modes (
STATIC&SLASH_ONLY): Extensively overhauled linking controls.STATICmode explicitly requires linking codes to be posted in a configuredlink-channel-id.SLASH_ONLYmode fully removes chat processing for codes, moving all linked verification exclusively into Slash Commands. - Link Slash Commands: Implemented user-facing commands
/link register <code>and/link drop <IGN>. Standard users can execute these without Administrative permissions. - Discord Drop Rate-Limiting & Auto-Complete: The
/link dropcommand filters available accounts intelligently through Auto-Complete, exclusively proposing the Discord User's linked IGNs. Also added a 7-day configurable cooldown logic to unlinking. - Strict Data Wipe: When players execute
/link drop, their.datPlayer files, statistics, and advancements are forcefully deleted from the world/playerdata/ server payload to inhibit unlinked alting. - Secure Unlinking: The /link drop command now strictly validates that the user actually owns the account they are trying to drop, even if they manually type the name.
- Webhook Queueing Engine: Fully replaced custom HTTP webhooks with
club.minnced.discord-webhooks. It natively queues operations and respects Discord API rate limits, solving out-of-order chat messages and severe CPU/Thread hogs during player bursts. - Strict IP Validation: Added a strict mismatch detector. If a player attempts to join with a trusted session but their IP address has changed, their trusted session is wiped and they are forced to fully re-authenticate to prevent hijacking.
- Guild Security Isolation & Audit: Refactored unauthorized guild enforcement into a dedicated
GuildSecurityListener. This centralizes the "allowed-guilds" logic and introduces an automated hourly "safety net" audit to ensure the bot never remains in unauthorized servers.
Fixed
- World Restoration: Fixed an issue where players were not correctly returned to their previous dimensions (Nether/End) after logging out. Location preservation is now correctly saved during
PlayerQuitEventrather than being prematurely consumed on join. - Early-Login IP Detection: Implemented an early IP Cache in
LoginProtectionListenerto prevent edge-case kicks when a player's network address returns null during initial handshakes. - Event Deprecation Warning: Bypassed Paper's
PlayerSpawnLocationEventdeprecation warning by utilizing manualEventExecutorregistration. This removes console spam while retaining necessary access to thePlayerobject during spawn enforcement.
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:DiFknrRi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kyiSeeUV:DiFknrRi"
}

