All versions
1.3
Release
TD-Hearts 1.3 - 26.23 days ago 14
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
MOD UPDATE ยป 1.3
๐ข NEW FEATURES
- [ALL] Settings now take effect immediately and save in the background. One dedicated worker handles settings, profiles and configuration reloads.
๐ก CHANGES
- [ALL] Configuration loading accepts only the current format. Older profile metadata, field names and setting aliases are rejected without migration.
- [ALL] Saving a profile does not activate it. Success notifications appear after the operation completes; failures use the existing notification style.
- [ALL] Normal shutdown gives accepted writes up to five seconds to finish. Closing the configuration screen does not cancel them.
๐ PERFORMANCE
- [ALL] File access and JSON processing now run outside interactive GUI actions. Profile lists use data already held in memory instead of scanning folders while rendering.
- [ALL] Automatic saves are queued immediately. Newer values replace pending saves that have not started, while explicit profile operations keep their click order.
- [ALL] Ordinary saves do not reload the mod, reset rendering caches or recreate the screen.
๐ด BUG FIXES
- [1.21.4] Fixed extra, misplaced hearts appearing with shaders. Hearts collected during the shadow pass are discarded before the main entity pass.
- [ALL] Hearts and health bars no longer render during the Iris shadow pass, including deferred drawing commands. Health indicators remain visible normally without casting shadows on the ground.
- [ALL] Configuration files are written completely as UTF-8 temporary files before replacing the previous file. Atomic replacement is used where supported, with a logged fallback on other file systems. Temporary files are cleaned up after successful and failed saves.
- [ALL] Delayed profile restores no longer overwrite settings edited after the restore was requested, even if a setting was changed and then returned to its previous value.
- [ALL] Consecutive profile operations no longer lose earlier changes. Saving also preserves text entered while an earlier operation is still running.
- [ALL] Closed or reopened screens no longer receive outdated notifications. An accepted profile restore still updates the active settings after its screen closes.
- [ALL] Invalid or ambiguous profile names cannot silently overwrite another profile. Built-in profiles and unexpected user files remain protected, and detected symbolic links or redirected directories are rejected.
- [ALL] Failed reloads and profile restores keep the previous active settings. Damaged configuration files are preserved instead of being automatically replaced with defaults.
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:NQGIwvcY:AeFFKJmQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NQGIwvcY:AeFFKJmQ"
}

