All versions
2.2.0
Release
Create: More Girder 2.2.03 months ago 188
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Version 2.2.0
Added
- Added a configurable server-side toggle (
girder.createGirderPlacementSystem) to switch between CMG's girder placement behavior (sticky TOP/BOTTOM connectors, no beam-to-pole collapse) and base Create's standard girder behavior. Defaults totrue(base Create rules). Syncs to clients on server join. - Added Russian (ru_RU) translation by savereks.
Changed
- Renamed all "Beam" display names to "Girder" (e.g. "Andesite Beam" ā "Andesite Girder"). Block and item IDs are unchanged, so existing worlds, schematics, KubeJS scripts, and datapacks are unaffected.
Fixed
- Fixed copycat girder mimic rendering for blocks that have no
cullfacequads (e.g. Foxy's Mod glowing blocks), multi-layer translucent blocks, and emissive/glow-shell blocks. Each render layer now draws on its own pass with correct brightness and alpha blending, matching base Create's copycat step behavior. - Fixed iron bracket sharing the same crafting recipe as the metal bracket.
- Fixed a mixin remap issue causing incorrect behavior and oversized mod file size.
Migration
- The new default (
createGirderPlacementSystem=true) makes CMG girders behave like base Create's metal girder. Builds relying on sticky brackets or persistent horizontal beams will degrade lazily (brackets cleared, beams collapsing to poles) on their next neighbor update. To keep the old CMG behavior, setcreateGirderPlacementSystem=falseinserverconfig/createmoregirder-server.tomlbefore opening an existing world.
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:sPg2LVAd:pPQAXioU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sPg2LVAd:pPQAXioU"
}

