Tags
Creators
Details
3.1
Compatibility
Changes
π Login-System v3.1 - The Ultimate Enterprise Authentication & Web Administration Suite
We are excited to announce Login-System v3.1, featuring unified web administration, seamless integration with Claim-System, direct item drop callbacks (zero inventory wipes), enhanced cross-platform compatibility, and robust security upgrades!
β¨ What's New in v3.1:
π Native Event Callbacks & Safe Inventory Protection
- No More Inventory Wiping/Hiding: Replaced the legacy inventory backup/clear mechanism with direct, native item drop callbacks (
ItemTossEvent/ Mixin event cancellation). - Zero Risk of Item Loss: Player inventories remain completely intact in memory without risk of desync, ghost items, or loss during unexpected server crashes or disconnects.
- Drop & Toss Interception: Unauthenticated players cannot drop, throw, or transfer items before logging in.
π Unified Web Administration Dashboard
- Interactive 2D World Map: Seamlessly connects with Claim-System to display land claims, coordinates, and player territories on the exact same port without any conflicts.
- Remote Player Management: Inspect live player inventories, reset passwords, kick, ban, unban, and mute directly from your web browser.
- Auto IP Detection & Console Banner: Prints a prominent, framed ASCII banner in the server console on launch with your public dashboard link:
======================================================================== π SERVER ADMIN WEB DASHBOARD IS ONLINE! π ======================================================================== π Open Dashboard : http://<your-ip>:<port> π Web Password : admin βοΈ Server Port : 20037 π‘οΈ Mod Features : Login Security + Claims & 2D World Map (Unified) ========================================================================
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:S4Tu3Hn2:DP99egtl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:S4Tu3Hn2:DP99egtl"
}

