All versions
1.3.2
Release
FunTime Auto Event 1.3.24 days ago 21
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
Added
- Automatic death markers with coordinates, arrival detection within 10 blocks, and persistent death history.
- Optional automatic tracking of the newest death marker.
- A single tracked marker per profile with a highlighted border and configurable absolute scale.
- Configurable dimming for non-tracked markers while a target is being tracked.
- Per-server and per-world marker profiles, manual profile switching, and one-click return to automatic profile selection.
- Marker search by name, coordinates, and dimension.
- Filters for active, disabled, death, manual, and event markers.
- Timestamps and dimension names in death-marker history.
- Full English (
en_us) and Russian (ru_ru) localization for menus, settings, statuses, profiles, events, errors, and chat actions.
Changed
- Tracked-marker size is now absolute instead of being multiplied by the normal marker scale.
- Expanded the history details column so timestamps and dimension names remain visible.
- Combined tracked and latest-death states into one clear status.
- Improved profile labels and automatic context reset when switching servers or worlds.
- Renamed the history cleanup action to clarify that only old disabled death markers are removed.
Fixed
- Search hint no longer overlaps typed text; it now uses a real placeholder.
- Older death markers are disabled and retained instead of being deleted.
- Reaching a death marker correctly disables it and clears tracking.
- Manual profile selection no longer persists after changing server or world.
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:oVRdJlul:dUCjjXGM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oVRdJlul:dUCjjXGM"
}

