Tags
Creators
Details
1.7.1
Compatibility
Changes
Stability & Performance Update Changelog v1.7.2 - Stability Performance Update
[Added] │➜ Database Auto-Repair: Now performs VACUUM and REINDEX on startup to fix fragmented data. │➜ WAL Mode: Enabled Write-Ahead Logging for non-blocking database operations. │➜ Negative-ID Shifting: New logic for filter removal that prevents Primary Key collisions on high-latency disks.
[Fixed] │➜ Slot Realignment: Fixed the bug where filters wouldn't shift correctly in production environments. │➜ Database Locks: Resolved "SQLite Database is locked" errors during high-traffic farm periods. │➜ Zombie Filters: Automatic cleanup of ISF filters with 0 amount that stayed visible in the GUI.
[Improved] │➜ Disk I/O: Set synchronous mode to NORMAL for better performance on shared hosting. │➜ Data Integrity: Enhanced rollback safety for all slot-shifting transactions.
Note: A full server restart is recommended to apply these database optimizations.
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:PHDjYBWd:7JfdnLYB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PHDjYBWd:7JfdnLYB"
}

