Links
Tags
Creators
Details
1.3.2-mc26.2-2
Compatibility
Changes
Fixed
-
Copycat walls rendered as several overlapping walls. A straight run showed a diagonal shimmer that moved with the camera, as if the block were duplicated or drifting.
The straight-panel case built the full panel and then carried on to build the centre and sides on top of it — coplanar duplicate geometry, which z-fights. Upstream ended that case with an early
return; converting the method during the port dropped it. Only the wall model of the nine copycats was affected.
No longer a beta
The previous build warned that almost all testing had run with Flywheel on, which skips block entity renderers entirely — leaving 16 of the 24 registrations barely exercised.
That pass is done. All 16 were placed and viewed with /flywheel backend off: no crashes, no missing geometry, no wrong models. The wall bug above is what it found.
If you run Sodium, or keep Flywheel off, that path is now tested rather than assumed.
Known issue, new
- Copycats shade slightly differently from Create Fly's, most noticeable on the layer of blocks sitting on the ground. This is a lighting difference only — the blocks are solid and nothing shows through them. Create Fly gives its own copycat models a FRAPI-aware
emitQuadsthrough per-model mixins so the ambient-occlusion flags survive; this port's nine models have no equivalent yet. Cosmetic, and on the list.
On the version number
1.3.2 is upstream's — this port is built on hlysine's newest commit, so the feature set matches Create: Connected 1.3.2 exactly. The trailing -2 counts builds of this port against that same upstream version; it does not mean new content.
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:DwndSliU:POkYzekU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DwndSliU:POkYzekU"
}