Links
Tags
Creators
Details
All versions
1.0.30
Release
UniverseGate 1.0.3015 hours ago 7
Compatibility
Minecraft: Java Edition
1.21.1β1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
UniverseGate 1.0.30
Redesigned portals
- Assembled portals now feature a rotating 3D ring. Depending on how the portal is built, its base sits above ground or blends into the terrain.
- Portals have new opening and closing animations, with a dark pixel-art membrane, glowing cracks, electrical arcs, crackling sounds, and steam vents.
- Portal control consoles have been redesigned. Naturally generated village consoles now face the playerβs approach.
Lightning antennas and wiring
- A freestanding, four-block-tall lightning antenna replaces the old portal lightning rod. Connect it to a portal with electric wires and crocodile clips. A lightning strike can open an unstable link to the Rift.
- The antenna stores up to five charges when no connected portal can open. Existing Charged Lightning Rods can be crafted into the new antenna.
- Red and blue wires can run along floors, walls, and ceilings. Each wire connects to its matching antenna terminal. At the portal, exposed copper leads attach to screws on the fixed base. Wires coming from above hang down and rest on the ground before reaching the terminals.
- Cables, clips, and their supports inside the portal opening are preserved when the portal activates or the world reloads. A broken cable run or a clip attached to an isolated frame block cannot trigger a nearby portal.
Minecraft compatibility
- Added Minecraft 1.21.11 support alongside 1.21.1. Both versions are available for Fabric and NeoForge.
- Fixed Rift terrain generation on Minecraft 1.21.11.
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:49TvAMLZ:ztpHIjW8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:49TvAMLZ:ztpHIjW8"
}

