Tags
Creators
Details
1.7.0
Compatibility
Changes
ChangelogBook v1.7.0 - Critical Bug Fix Update
⚡ Major Stability Update - 11 Bug Fixes ⚡
What's New in v1.7.0?
Version 1.7.0 is a major stability update fixing 11 bugs including 3 critical issues that could cause data loss and server lag. This update is highly recommended for all users.
Critical Bug Fixes
-
Data Loss Prevention Entries are now saved to database before memory cache, eliminating data loss during database failures. No more lost changelog entries when MySQL connection drops!
-
DoS Protection Added content length validation (3-5000 characters) to prevent oversized entries and server lag. Protects against players spamming massive changelog entries that could crash your server.
-
Database Garbage Collection Soft-deleted entries are automatically pruned after 30 days, preventing infinite database growth. Your database will stay clean and performant over time.
⚡ Performance & Stability Improvements
90% faster display numbers - Implemented caching system for entry numbering Thread-safe operations - Fixed ConcurrentModificationException during /changelog reload Resource leak fixed - Discord webhook connections now properly close Configurable connection pool - HikariCP pool size is now configurable (default increased from 5 to 10)
✨ Quality of Life Improvements
Better error messages - Clear feedback when content validation fails Discord webhook validation - Invalid URLs are detected before sending Reload-friendly config - Update checker interval refreshes without restart
⚙️ New Configuration Options
All new options have sensible defaults - no manual configuration required!
Code (Text): limits: max-content-length: 5000 min-content-length: 3
database: prune-deleted-after-days: 30 prune-on-startup: true
mysql: pool: maximum-size: 10 minimum-idle: 2 connection-timeout: 10000 idle-timeout: 600000 max-lifetime: 1800000 Performance Comparison
Display Number Calculation: O(n log n) per call → O(1) cached lookup (~90% faster) Database Growth: Infinite → Capped by auto-prune (Sustainable) Connection Pool: 5 fixed → 10 configurable (Better scalability) Memory Leaks: Yes (Discord) → No (100% resolved)
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:vVggUfVj:2Sfjm3Fb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vVggUfVj:2Sfjm3Fb"
}

