All versions
1.20.2-0.12.0
Beta
Stormward 1.20.2-0.12.0last year 51
Compatibility
Minecraft: Java Edition
1.20.2
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
- Shadesmar True Spren
- Encompasses nine different mobs: Highspren, Peakspren, Cryptics, Ashspren, Lightspren, Honorspren, Inkspren, Cultivationspren, and Mistspren
- Can be found in Shadesmar Ships and Shadesmar Outposts
- Every True Spren trades an item in exchange for Stormlight
- Deadeyes
- Deadeyes are variants of True Spren, but do not occur naturally and cannot trade
- When a mob enters the Shadesmar with a Shardblade, the Shardblade transforms into a Deadeye bonded to that mob
- Deadeyes follow their bonded mob
- When a Deadeye is killed, the associated Shardblade is lost permanently
- Shadesmar Changes
- While in the Shadesmar, Shardplate disappears and is unusable
- Unless KeepInventory is on, dying in the Shadesmar will cause any stored shards (both plate and blade) to drop at the location the player entered the Shadesmar
- Instead of one monolithic biome, the Shadesmar is now composed of four slightly different biomes
- Pillars and fractals in the Shadesmar generate slightly differently
- Shadesmar flora generates slightly differently
- Fewer monsters spawn in the Shadesmar
- Boats now work when sailing on Cognitive Bead Blocks
- Shadesmar Ships and Shadesmar Outposts now generate in the Shadesmar
- Shadesmar Ships
- New structure that generates in Shadesmar Oceans
- Has some loot, and contains True Spren
- Shadesmar Outposts
- New structure, similar to overworld villages, that generates in Shadesmar biomes
- Primarily place to find True Spren
- New Items
- Highspren Spawn Egg
- Peakspren Spawn Egg
- Cryptic Spawn Egg
- Ashspren Spawn Egg
- Lightspren Spawn Egg
- Honorspren Spawn Egg
- Inkspren Spawn Egg
- Cultivationspren Spawn Egg
- Mistspren Spawn Egg
- New Mobs
- Highspren
- Peakspren
- Cryptic
- Ashspren
- Lightspren
- Honorspren
- Inkspren
- Cultivationspren
- Mistspren
Optional dependencies
Any compatible version
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:D0RGGSjV:teWU9rhj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D0RGGSjV:teWU9rhj"
}

