Tags
Creators
Details
All versions
1.18.2-0.5.1.e
Release
Create 1.18.2 0.5.1.e3 years ago 35.8K
Compatibility
Minecraft: Java Edition
1.18.2
Platform
Forge
Supported environments
Server-side
Client and server
Changes
- Addons can now more easily register custom fan processing types
- Added tags to allow controlling which blocks and fluids act as catalysts for certain fan processing types
- Fixed unlit campfires providing boiler heat
- Fixed crash when applying trapdoors to copycat panels
- Added tag to prevent specific vanilla recipe types from integrating with create
- Rollers no longer break blocks adjacent to blocks tagged #minecraft:portals
- Added safety checks for active rollers passing through a portal
- Fixed rollers in fill mode consuming blocks from a train without placing any
- Changed lava diving advancement from hidden to challenge, as it is an actual intended player ability since 0.5.1
- Changed title of speed controller advancement
- Funnels, Chutes and other Create components should now perform a little better when used with large vaults
- Added support of other packet size optimisation mods: connectivity and Packet Fixer (KostromDan)
- Spectators can no longer interact with Super Glue and Valve Handles (attackeight)
- Fixed Elevator Contraptions sometimes powering multiple contacts upon arrival (laxadeR)
- Fixed Deployers not able to interact with blocks using block-like items (NovaStarter)
- Integrate new modded wood types with create: Environmental, Atmospheric, Infernal Expansion, Good Ending, Biome Makeover (Tempystral)
- Addons can now specify custom behaviour when pipe fluids collide (Notenoughmail)
- Localisation updates from CrowdIn
- 1.19, 1.20: Trains can now travel to the Aether
- 1.20: Fixed some blocks incorrectly treated as non solid
- 1.20: Fixed crash when other mods query creative tabs server side
- 1.20: Integrate new vanilla wood types with create (attackeight)
- 1.20 (Flywheel): Fixed compatibility with Starlight
- 1.20 (Flywheel): Fixed compatibility with Embeddium
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:LNytGWDc:ZyOnhaSB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LNytGWDc:ZyOnhaSB"
}

