Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 months ago
All versions
1.1.0-mc1.21.1
Release
Create: Pipe Connector 1.1.0 (NeoForge)3 months ago 121
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Additions
- Add an immediate ghost preview for the first selected pipe position
- Add progressive route construction that places confirmed pipes one piece at a time
- Add five construction speed presets: Very slow (
1piece/s), Slow (5pieces/s), Normal (10pieces/s), Fast (15pieces/s), and Very fast (20pieces/s) - Add an option to disable progressive construction for instant placement
- Synchronize per-player animation preferences with multiplayer servers
- Apply animation setting changes to routes already being constructed
- Add independent settings for the complete outline-free construction preview and the highlighted next-piece preview
- Allow several confirmed routes to animate at the same time
Art Changes
- Add dedicated ghost and anchor render types while preserving the established cyan, yellow, pump, and missing-material colors
- Restore transparent ghost models so rear pipe edges remain visible through the preview
- Improve anchor layering so pipe models and cyan outlines remain visible through the yellow overlay
- Keep preview colors and transparency consistent when routes cross water or other fluid surfaces
Gameplay Changes
- Support Create versions from
6.0.6up to, but not including,6.1.0 - Require one copper casing in the inventory without consuming one casing for every encased pipe
- Use regular Create fluid pipes as the only route material for glass styling
Optimizations
- Reorganize routing, geometry, interaction range, materials, sessions, payload handling, and UI code into focused feature packages
- Convert the legacy multiloader workspace into a standard single-module Forge project
- Remove the stale NeoForge module, obsolete loader scaffolding, package metadata, unused code, translations, and project files
- Document mod classes and methods with concise Spanish Javadocs
- Simplify the Gradle tasks used to run and package the Forge build
- Reuse Create and Catnip model buffering through
SchematicLevel,ForgeBakedModelBufferer, andSuperByteBuffer - Cache preview geometry, fluid groups, outline boxes, outline colors, anchor lookups, and visible sections instead of recalculating them every frame
- Reduce temporary allocations and duplicate work while building routes, drawing outlines, updating anchors, and rendering long previews
- Update the README and Forge documentation for the final project structure, Create compatibility, controls, and placement animation settings
Bug Fixes
- Fix Forge production jars not being reobfuscated correctly
- Fix the initial pipe preview not appearing until the route contains at least two positions
- Fix preview pipes becoming opaque, partially invisible, or losing transparency with Embeddium, Oculus, shaders, and other rendering modifications
- Fix hidden cyan pipe outlines inside the yellow anchor overlay
- Fix triangular gaps and malformed faces in the translucent anchor cube
- Fix preview transparency and colors changing after adding or removing anchors
- Fix previews disappearing when the camera and route are on opposite sides of a water or fluid surface
- Fix placed pipes, elbows, pumps, and encased sections not consistently preserving waterlogging
- Fix anchor positions occasionally leaving an empty gap in the placed route
- Fix the all-glass style requesting or consuming separate glass pipe items instead of regular fluid pipes
- Fix missing-material highlighting so glass-styled sections use the available regular pipe count
- Fix placement animation settings not applying reliably after joining, closing the config screen, or changing an active route
- Fix disabling progressive construction not finishing already queued routes immediately
- Fix completed pieces remaining visible in the construction preview after being placed
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:M1DHa9hR:wjXtqQwF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M1DHa9hR:wjXtqQwF"
}

