
Stargate: Wellspring, a The Sift Dimension
Dial ancient stargates to eight kinds of worlds: Wellspring, a fan-made take on Minecraft's Sift dimension, sky islands with glowing heart trees, frozen wastes, molten depths and more. Vanilla potions and armour beat every hazard. Needs the Worlds mod.
Tags
Creators
Details
1.8.8+26.3-pre-3
Compatibility
Required content
Changes
Requires Worlds 1.8.18 or newer.
Added
- Support for Minecraft 26.3 Pre-Release 3
- Every gate now has a supply chest. What's inside suits the world the gate stands in — torches and glow berries in the dark dimension, fire charges and blaze rods in the molten one, snowballs and blue ice in the frozen one, and useful everyday gear at gates in the Overworld and the Nether.
Fixed
- Desert and mountain gates are properly sunk into the ground now. Around two thirds of desert gates and half of mountain gates were standing fully exposed on the surface.
- Stargate eyes no longer do nothing when you throw them while aiming at a block.
- Endermen no longer appear in lit rooms in the dark dimension.
- Filling your inventory no longer destroys the book from
/stargate debug givebook.
Changed
- Your Stargate advancements have been reset and must be earned again. They were filed under Minecraft's own advancements by mistake, which also meant the game counted them as vanilla progress. They now sit in their own Stargate group, where they belong.
- Your stargate worlds will now keep their landscape through future Minecraft updates and through changes to the mod's dimension line-up. Each world remembers how it was first rolled and rebuilds itself the same way every time.
- Mobs in stargate dimensions now spawn under the normal rules, so they turn up in the places you would expect. Parrots and allays are unchanged.
- The address book can now be translated into other languages.
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:a4uUVkNz:h7SBc8yN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a4uUVkNz:h7SBc8yN"
}
