Tags
Creators
Details
Licensed ARR
Published last month
Updated 3 days ago
All versions
0.1.4.2-forge
Release
Dreamshift 0.1.4.23 days ago 5,895
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
0.1.4.2
Forge NO LONGER requires the Immersive Portals dependency, as we have a custom update to 5.2.0 bundled inside of Dreamshift.
- Fixed players sometimes returning from a Dreamspace at world spawn or underground.
- Dreamshift now saves the player's last safe position before a slip instead of allowing void falls or portal phasing to overwrite the return point with an unsafe coordinate.
- Slippage portals track the coordinate before the player's hitbox enters the wall, preventing players from returning inside a wall or on top of.
- Unsafe return coordinates from older saves are moved to nearby supported ground, and players who respawn after dying in a Dreamspace are returned to their saved reality position.
- Reality Slippages can no longer spawn inside Dreamspaces, and disabling Slippage Faces now closes their portals, and restores wall collision until the feature is re-enabled.
- Familiar Backrooms now uses its own dedicated ambience track.
- Lethal Dreamspace damage now wakes the player before vanilla death can drop items, with a short return grace period & fallback for restoring the stashed inventory.
- Very rarely would lethal damage cause you to actually die, and lose items.
- Paragraph Aisle's final task appears after you finish the story.
- Updated the macOS Immersive Portals and Iris warning to recommend Legacy Mode for affected Apple Silicon and older GPUs.
- Fixed Forge failing to discover bundled dependencies when Dreamshift was installed alongside mods that require MixinExtras 0.5.x or newer.
- Immersive Portals 5.2.0 remains bundled with Dreamshift on Forge.
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:QaVSXlYb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sdQwPACz:QaVSXlYb"
}



