Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published last month
Updated 2 months ago
All versions
1.1.6
Release
WormholeXTreme 1.1.62 months ago 33
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Paper
Spigot
Changes
- Added a configurable minimum distance between stargates. Default is 0 blocks (disabled). Set it with
/wormhole min_gate_distance <blocks>, or via WORMHOLE_MINIMUM_GATE_DISTANCE in Settings.txt. /wxlistwith no argument now falls back to listing your own gates if you lack permission for/wxlist all, instead of refusing outright.wormhole.listandwormhole.list.allnow default for opped players.wormhole.list.selfdefault for everyone else.- Without a permissions plugin installed, list permissions now fallback to op status: opped players can list every gate, everyone else can list their own.
- Tab completion on
/wxgoand/dialnow only suggests gates you are allowed to list. /wxremovecan now clear an orphaned gate entry left behind by an abandoned build.- Fixed SignDial target lists not looping back to the start after reaching the end of the list.
- Fixed SignDial lists showing only a single destination when several gates shared the same database id.
- Fixed 'ghost' stargates that showed a null owner, never refreshed their dialler sign, and could not be removed with /wxremove. Unfinished builds are no longer registered to a network, and duplicate registrations are now prevented.
- Fixed stale block index entries surviving gate removal, which left a deleted gate reachable by clicking its name sign.
- Stargates now shut down at both ends when either gate is broken or removed. Previously destroying the destination left the origin gate active with an open portal.
- A stargate can no longer be dialled while it is already connected to another gate.
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:y3CYpSr0:yiVyWCRz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y3CYpSr0:yiVyWCRz"
}
