Tags
Creators
Details
Licensed ARR
Published last month
Updated last month
All versions
0.1.3
Release
Dreamshift 0.1.3last month 40.8K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
0.1.3
0.1.3 is mostly a stability update for the things that could leave players stuck, lagged, or carrying the wrong state after Dreamspace did something weird.
- Fixed slippages sometimes staying in the world after their grace period ended. Dreamshift now double checks player dimension changes every server tick, so Immersive Portals entries still get caught even when the usual dimension change event path does not fire.
- Fixed the multiplayer case where everyone enters the same slippage, returns to the Overworld, and the old portal stays behind as a laggy unusable shell. If every online player has entered that slippage session, Dreamshift now closes the source portal immediately instead of waiting for grace to time out.
- Fixed old unusable slippage portals being able to survive after the saved slippage marker was already gone. Cleanup now forces the Immersive Portals entity and Dreamspace runtime reference to clear by slippage ID.
- Fixed broken or invalid slippages skipping part of the normal cleanup path. These now go through the same removal logic as grace-expired slippages, which should stop old portal references from piling up until restart.
- Fixed a respawn edge case with Dreamspace inventory isolation. If the player has a saved normal inventory snapshot after respawning outside Dreamspace, Dreamshift restores it and clears the old return snapshot instead of leaving the player in a bad inventory state.
- Fixed Dreamspace environment locking leaking into the Overworld. Dreamspace still holds its authored sky time and weather for players inside it, but Dreamshift no longer writes shared server gamerules, day time, or weather from Dreamspace environment sync, so Overworld days continue and sleeping advances night normally. Saves already affected by older builds may need
/gamerule doDaylightCycle trueonce. - Added config options to prevent reusable Dreamspaces from resetting and to disable the random unscripted Dreamspace return timer, giving creators more room to preserve progress and author longer visits.
- Tuned natural Reality Slippage spawning so checks run every 20 seconds instead of every 10 seconds. The default 5% roll now averages about one successful spawn roll every 6 minutes 40 seconds per player before caps and wall-candidate checks.
- Changed fresh configs to disable familiarity tracking by default. With familiarity tracking disabled, natural slippages avoid the player's current chunk and only use valid nearby adjacent-chunk wall candidates.
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:sdQwPACz:XQtDBanI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sdQwPACz:XQtDBanI"
}




