Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 9 months ago
Updated 4 days ago
All versions
0.4.1
Release
CobbleSafari 0.4.14 days ago 506
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Features
- Megapolis (+ ultraspace) and Belltower now have custom dimensional objectives
- Megapolis got a makeover, now looks closer to what they look in USUM
- The Megapolis portal now looks like an ultra wormhole instead of an hoopa portal.
- HUD settings move to client_settings.json, a new config files that also let you disable the Rotom Phone totem animations and the Ultra Warp Ride flashes to allow for a better accesibility.
- Creative Portal Spawner can now be placed on a ceiling, and spawns the portal below it (this makes the portal + spawner fit a 2 black tall space)
- Ender pearls, chorus fruit, wind charges and boats are banned in dungeons via the new forbidParkourItems boolean in the restriction API.
Fixes
- Fixed the BellTower lost item loot not being properly distributed (I messed up the loot table).
- Fixed the start of the distortion world not giving the proper reward via their lost item.
- Buckets (including modded ones) now follow the block placing/breaking bans of said dimension (apologize to you, the player who've been cheesing all the jump with water)
- A mixin was added to prevent the Figura mod from overwriting the model of the ultra recon armor and the nihilhat. I wish there was a cleaner way to do it, but figura doesn't seems to have one.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:zj3GsKts:wWeznN5R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zj3GsKts:wWeznN5R"
}

