1.1.1
Compatibility
Required content
Changes
Temporal Paradox Update
Added the new Temporal Instability system. Added the Temporal Instability Detector to monitor instability levels. Added instability increases caused by time travel, paradoxes and interference with the past. Added new temporal visual effects, HUD distortion, screen pulses, sounds and travel feedback. Added the Temporal Paradox Replay system in Past10. The game now records the player’s movements, actions, held items and world interactions before their first time travel. Added realistic player echoes that reproduce recorded actions and disappear after using the Time Jumper. Added consequences for approaching, attacking or altering the path of your past self. Added Temporal Shard drops from replay-related instability events. Added the Temporal Collapse event when instability reaches its maximum level. Temporal Collapse now returns the responsible player to the Present and removes temporal equipment and stored temporal items. Added permanent per-world settings for disabling Temporal Instability. Added instability and replay persistence across restarts. Added new advancements related to time travel, paradoxes, instability, replays and collapse. Added the Temporal Shard Block. Improved Time Jumper, Fast Return Device and Instability Detector integration. Added individual replay recordings for every multiplayer player. Multiple personal replays can now exist simultaneously in Past10. Players can only trigger a collapse by interfering with their own replay. Other players’ replays remain visible but only cause a lighter HUD distortion. Fixed Past 10 replay conflicts between multiple players. Fixed freezes occurring during Temporal Collapse and the return to the Present. Added /temporalinstability pause-resume-status command
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:PIKPu4C1:kGEGkGZt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PIKPu4C1:kGEGkGZt"
}

