Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 15 hours ago
All versions
3.5.1-1.20.1
Release
Sensory Abyss 3.5.1-1.20.1last week 63
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Sensory Abyss 3.5.1
Mostly a repair update.
Fixes
- The game wouldn't load on some AMD graphics cards. It stopped on the loading screen with
'active' : Reserved word. - Clicking a World difficulty tile in the settings crashed the game when the settings were opened from the title screen. Outside a world the tiles now say they're set per world.
- A Shattered reaching level 3 got stuck on an empty card screen. Nothing could be picked, and every later level-up waited behind it.
- The Ritual Altar, Pedestal and Brazier couldn't be mined. They broke very slowly and dropped nothing. So did every candle, candelabra, chandelier and candle holder, the macabre lights, the Fueled Lantern, the Ward Totem, Cooled Magma and the Chalk Snare. They take a pickaxe now (an axe for the bamboo ones, a shovel for the Chalk Snare). The Brazier needs a stone pickaxe or better.
- Ice, slime, honey and stained glass glowed in the dark. Ice, slime and honey blocks, the edges of stained glass panes and the frames of Deep stained glass showed fully lit in pitch dark. Stained glass under a night sky was also brighter than the ground around it.
New
- Report a Bug. Journal → Credits → Report a Bug, or type
/sabugreport. It uploads your latest log, and a crash report from the last day if there is one, to mclo.gs, then opens the bug report form with your mod version, loader, mod count and log links filled in. No account needed. You can also open the form without sending the log.
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:HqTVssgg:NzceFnv6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HqTVssgg:NzceFnv6"
}

