Tags
Creators
Details
1.3.0
Compatibility
Changes
We are proud to present a major security and performance update! In version v1.3.0, we focused on deep internal optimization and switching to industry-standard cryptographic protection for player data.
⚠️version 1.3.0 is incompatible with 1.2.1⚠️
🛠️ What has been improved and added:
- 🔐 SHA-256 Password Encryption: Passwords are no longer stored in plain text. Upon registration, the mod generates an irreversible cryptographic hash. Even if the
users.jsonstorage file is somehow compromised, it is mathematically impossible for attackers to decrypt or recover the actual player passwords. - ⚡ Ryzen-Tier Performance Optimization: Completely redesigned the inner workings of the
PlayerTickEvent. The system no longer strains the server with continuous potion effect applications or teleportation packet spam. All state checks and updates are now smartly distributed across ticks, significantly lowering CPU overhead. - 📦 Smart Item Anti-Pickup: Implemented a robust workaround for the newly overhauled NeoForge 1.21.1 event bus API. Unauthenticated players will no longer accidentally clutter the ground or trigger inventory bugs; items around them are now temporarily frozen at the entity level.
- 🐛 Stability Fixes: Fixed false-positive IDE resources warnings (
Levelresource leaks) and optimized background data handling to ensure 100% server uptime and zero-lag performance under high player loads.
The project was developed by the O.S. TEAM. Thank you to all our testers for your ongoing support and operational bug reports!
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:gFNOFF0t:FeOrIUls"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gFNOFF0t:FeOrIUls"
}

