0.1.3
Compatibility
Required content
Changes
Added
-
Added three fully functional traffic sign poles:
- Traffic Sign Pole
- Traffic Sign Pole with Base
- Mobile Construction Sign Pole
-
Added concrete road barriers and impact-protection variants.
-
Added 11 new clinker facade variants in gray, orange, red, and yellow, including straight sections and available inner/outer corners.
-
Added complete German and English translations for previously untranslated traffic signs and other items.
-
Added new creative menu categories for Road Furniture and Garage Doors.
Improved
- Traffic sign poles were resized to correctly match the width of existing traffic sign posts.
- Guardrail end pieces were updated and corrected, including left/right variants and all rust stages.
- Rotating blocks now use matching model-based collision boxes.
- Guardrails, sign poles, concrete barriers, and clinker blocks are fully integrated with recipes, loot, tags, tool requirements, and creative inventory entries.
- Creative menu entries were reorganized to remove duplicates.
- Existing texture and model compatibility has been preserved where required.
Fixed
- Fixed incorrect face orientation on the right guardrail end piece.
- Fixed missing or incorrect texture references in imported models.
- Fixed a typo in one clinker variant while keeping compatibility with the intended registry name.
- Completed missing German and English translations across all registered blocks and items.
Removed
- Removed the legacy
Sectional Garage DoorandRoll-Up Garage Doorblocks. - The dynamic garage door system using the controller, creation tool, key, and remote remains fully available.
Note: Existing worlds containing the two removed legacy garage door blocks may lose those placed blocks when loaded.
Validation
- Full project build completed successfully.
- All asset, language, converter, regression, and system tests passed.
- No new model or texture warnings were introduced.
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:BwVex3Tv:3HCS7oFE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BwVex3Tv:3HCS7oFE"
}

