All versions
1.0.1+26.1
Release
Dimensional Inventories Extension: Warp 1.0.1+26.1last month 8
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
Changelog
[1.0.1] — 2026-06-02
Added
- LuckPerms / Fabric Permissions API support — permission nodes
diminv.warp.selfanddiminv.warp.othersnow control access to/warpand/warp player. Falls back to vanilla OP level 4 when no permissions mod is present. Fabric Permissions API 0.7.0 is bundled via JiJ (no extra mod required). - Creative-mode pool Y override — when the target pool has
gameMode: CREATIVEin Dimensional Inventories config, the teleport Y coordinate is forced to100.0; X, Z, and rotation are still restored from the player's saved position.
Changed
- Pool-based warping —
/warpnow accepts a pool ID instead of a dimension ID. Players are teleported to whichever dimension within that pool they were last in, preserving exact coordinates. Leaving any dimension (including via portals) updates the per-pool last-dimension record. Falls back to the first dimension in the pool on first visit. - JSON save format v2 — positions are now nested under a
"positions"key and a"lastDimensionInPool"map is written alongside them. The old flat format is still read transparently and re-saved in the new format.
Fixed
- Fallback spawn position now always lands on a solid surface block. Two edge cases addressed:
getRespawnData()could returnnullfor dimensions without explicit spawn data; falls back toBlockPos.ZERO.getHeight(MOTION_BLOCKING_NO_LEAVES)returnsgetMinY()for ungenerated chunks, which would place the player underground; falls back tospawnPos.getY() + 1instead.
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:3RMPyNE3:gqA1FlWa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3RMPyNE3:gqA1FlWa"
}
