All versions
1.0.2
Release
BetterTimer 1.0.211 months ago 49
Compatibility
Minecraft: Java Edition
1.21.4–1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Changelog - MC Timer Mod
[1.0.2] - 2025-01-09
Fixed
-
Server Compatibility: Timer commands now work correctly on multiplayer servers
- Converted from server commands to client commands
- Commands are now registered on the client side instead of server side
- Fixed crashes when joining servers
-
ModMenu Integration: Fixed UI overlapping issues in config screen
- Synchronized Y-coordinates between init() and render() methods
- Labels now properly align with their corresponding input fields
- Color pickers and presets display correctly without overlapping
Changed
- Environment: Mod is now explicitly marked as client-side only in fabric.mod.json
- Command System: Migrated from
ServerCommandSourcetoFabricClientCommandSource/timer start- Start the timer (client-side)/timer pause- Pause the timer (client-side)/timer reset- Reset the timer (client-side)
Technical Details
- Updated
TimerCommand.javato useClientCommandManagerandClientCommandRegistrationCallback - Command registration moved from
MCTimerModtoMCTimerModClient - Set
"environment": "client"in fabric.mod.json - Fixed ConfigScreen rendering coordinates alignment
[1.0.1] - Previous Version
Features
- Basic timer functionality with HUD display
- Animation effects: None, Rainbow, Pulse
- Color customization for normal and paused states
- ModMenu integration for easy configuration
- Auto-pause on disconnect
- Persistent timer storage
Commands
/timer start- Start the timer/timer pause- Pause the timer/timer reset- Reset the timer
Optional dependencies
Any compatible version
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:QSFpyCfw:Ei20Ok45"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QSFpyCfw:Ei20Ok45"
}

