Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 years ago
Updated 3 months ago
All versions
2.2.0
Release
Warp Pipes 1.20.1-2.2.0-forge2 years ago 131
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
- Renamed pipes now display text on the block similar to signs
- Right-click with dyes to color text (automatically compatible with Dye Depot)
- Right-click with a glow ink sac for glowing text
- Right-click with an ink sac to remove glowing text
- Right-click with a brush or Supplemetaries soap/bubble wand to remove text on specific sides of the pipe
- Right-click with a honeycomb to wax the pipe to prevent name editing
- Right-click with an axe to remove wax. This is off by default (like with signs) and can be enabled in the config.
- Previously renamed pipes may need to be renamed and right-clicked with a brush to display text on the pipe
- Improve structures
- Add custom loot chests to structures
- Fix hole in structure
- Add advancements
- Add swimming animation when in the clear warp pipe
- Add message when the warp pipe destination is missing
- Change entity
can_warptag toprevent_warpfor consistency with the pipe tagprevent_warp - Improve warping logic
- Improve gui buttons
- Warp Pipes are now dynamically registered, making it automatically compatible with mods such as Dye Depot. (Textures will still need to be provided)
- Fix gui buttons not animating in certain rare cases
- Fix gui sliders repositioning to the default values when the gui is reopened
- Fix north and west facing pipes warping entities to an incorrect position
- Fix cooldown message showing before warping
- WarpCooldown is now seperate from PortalCooldown, fixes being unable to use other portals if the cooldown was set to a high number in the config
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:iJHgOq1R:12OHQIZv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iJHgOq1R:12OHQIZv"
}

