1.0.1-Release
Compatibility
Required content
Changes
SimpleGens v1.0.1-Release
This is an incremental patch and feature update for SimpleGens that squashes critical scheduler runtime loops, fixes unparsed administrative GUI text fields, and introduces explicit quality-of-life interactive features.
🛠️ Changelog
🚀 Added
- Chat Session Cancel Escape Trigger: Introduced a native uppercase
CANCELtracking string hook insidePlayerInputManager.java. Typing it cleanly kills active background data-listening loops, prints a localized cancel notice, and returns the operator safely back to the generator configuration dashboard. - Automatic Time Unit Simplification: Added an integrated time formatter that dynamically converts raw tick labels inside GUI menus into readable whole-number formats (
100tparses to5s,2400tparses to2m) if they divide perfectly, preventing visual string clutter. - Full-Inventory Safeguard Interception: Registered an inventory threshold validation rule in
SimpleGensBlockBreakListener.java. When active, players with full storage arrays are blocked from mining static generator lines to protect item drops from despawn vulnerabilities.
🐛 Fixed
- Scheduler Double-Loop Interval Execution: Resolved a critical logical flaw inside
SimpleGensRegenTask.javathat forced block restoration loops to process at exactly half-speed (stretching a 5-second interval into a 10-second wait). Tasks are now firmly synchronized to precise server tick metrics. - Nested Hover Lore Tag Rendering: Upgraded slot 14 (Broadcast modifier) inside
GeneratorConfigGUI.javato handle nested MiniMessage styling data using modernPlaceholder.parsed()strings. Color nodes (like<gold><bold>) now render full visual previews inside mouse-hover windows. - Global Variable Matrix Reconciliation: Repaired loose placeholder references (
<broadcast_status>vsstatus) insideGeneratorIndexGUI.java, successfully restoring the dynamic visual live tracking labels. - YAML Scanner Escape Violations: Patched double-backslash layout tracking strings inside
messages.ymlto satisfy SnakeYAML processing boundaries and eliminate console parser failures on server boot.
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:Z13aXEmQ:ckvciZPu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z13aXEmQ:ckvciZPu"
}

