Tags
Creators
Details
0.8.0-SNAPSHOT.1+mc1.19.2
Compatibility
Changes
IMPORTANT NOTE!
This release is only for 1.19.2, 1.20.1, 1.21.1, 1.21.11, and 26.x, as I plan on dropping support for all other versions. If you are on a version not mentioned here, please reach out to me in my Discord server, and I'll make sure to keep supporting your version.
New system for simulating BlockEntities and Entities
This will make it simpler for other devs to add support for their modded BlockEntities and Entities, as they are no longer required to override a method from an interface in my mod. (WIKI COMING SOON)
Support using "game time" for simulating time
"game time" is similar to "day time", except it doesn't jump whenever the player skips the night, and it keeps doing if the advance_time gamerule is false.
This can be changes with the new config option "simulationClock" (/unloadedactivity config simulationClock in-game).
Valid values are:
- DAY_TIME
- GAME_TIME
- SYSTEM_TIME
Trial spawner support (1.21+)
Trial spawner cooldown is now supported.
Properly support Lithium
Furnaces now get Lithiums sleeping BlockEntity optimizations while still working with Unloaded Activity. Previously, Unloaded Activity would simply just disable that optimization.
Fixes
- Fixed the
neapolitan:banana_frondtag throwing an error if neapolitan wasn't present. - Fix the version range for 26.1.2 on NeoForge. (This would cause dedicated servers to fail to start. Not sure why clients weren't affected)
Snapshot reason
The reason this is a snapshot is because I still have some things I want to add, as well as adding support a few modded BlockEntities and Entities to test out the new simulation system. Please report any bugs or oddities you find!
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:Oo4rJCDP:rl0Flctm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Oo4rJCDP:rl0Flctm"
}

