Tags
Creators
Details
2.0.0
Compatibility
Changes
Project Time Master: Reforged â v2.0.0
This release fixes the long-standing issue where only the MK2 watch appeared to work in hand, restores the mod's core mechanic for every tier, and reworks Time Stop to be fully safe for your worlds.
ð Fixed
- MK3âMK8 watches now work in hand, just like MK2. The "on" texture of these watches was wired to an item property that never fires (
projecte:active, a leftover from v1.0). All models now use the mod's ownmodeproperty, so every tier lights up and responds to SHIFT + Right-Click. - In-hand block acceleration is back for all tiers. Holding an active watch (any mode other than OFF) now accelerates crops, furnaces and machines in a 9Ã9Ã9 area around you â the mod's signature mechanic, which had been lost in v1.5. Speed still scales with the watch tier (configurable in
projecttimemasterreforged-common.toml). - The acceleration blacklist actually works now. Due to a filename typo, the blacklist tag was always empty â bedrock, command blocks, portals, etc. are now properly protected from forced ticks, both in hand and on the pedestal.
- Pedestal area corrected to a true 9Ã9Ã9. An off-by-one made it 10Ã10Ã10, not matching the pedestal tooltip.
- Watches no longer stack their effects from inside your inventory. Effects only apply while the watch is in your main or off hand, so carrying multiple watches no longer multiplies time speed. OFF mode is now truly inert.
â±ïž Time Stop rework
- Time Stop no longer touches the
doDaylightCyclegamerule. It now freezes the clock by holding the world time at the moment you activated it. - Dropping, stashing or logging out with a watch in STOP mode simply lets time resume on its own â no more worlds permanently stuck at the same hour.
- Manual
/gamerulechanges by server admins are never overridden by the mod anymore. - â ïž Migration note: if your world got stuck with frozen daylight by an older version, run
/gamerule doDaylightCycle trueonce. New versions will never cause this again.
ð¥ Safety & stability
- Fire and soul fire are blacklisted by default â watches no longer make fire spread hundreds of times faster around you.
- Crash protection: if a block from another mod can't handle forced ticks, the error is now caught and logged (
Failed to accelerate block ...) instead of crashing the server. - The blacklist is a standard block tag (
projecttimemasterreforged:acceleration_blacklist), so server owners can extend or override it with a datapack â no rebuild needed.
ð Notes
- Fully compatible with existing worlds and items â no IDs or save data changed.
- Requires ProjectE, as always.
- Tier differences remain purely quantitative (speed per tier); a per-tier radius option and EMC drain are planned for a future update.
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:rJG5Mf5e:fXFU3OeI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rJG5Mf5e:fXFU3OeI"
}

