Links
Tags
Creators
Details
All versions
0.3.2
Release
CBC: Firepower Components 0.3.2last month 42.6K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
CBC: Firepower Components 0.3.2
- Added mount/control compatibility data for more addon cannon types, including CBC: Advanced Technologies, CBC: Military Supplement / cbcmoreshells, and CBC Modern Warfare-style cannon families.
- Added support data for heavy autocannons, twin autocannons, manual twin autocannons, rocket pods, medium rocket pods, dual cannons, projectile racks, torpedo tubes, medium cannons, mounted launchers, and rotary cannons where their mounted contraption data is available.
- Added the Large Autocannon Ammo Box, with 64 normal rounds + 64 tracer rounds capacity.
- Improved large autocannon ammo box handling, menu behavior, item validation, and compatibility with CBC's ammo container system.
- Improved mounted weapon item input through a shared strategy layer, so compact mounts can route inserted items more safely to mounted weapons.
- Improved mechanical arm and item-handler insertion behavior for compact cannon mounts.
- Added an initial compatibility layer for Create: Radars on NeoForge 1.21.1.
- Compact cannon mounts can now be selected by the Create: Radars data link.
- Added adapter logic for radar yaw and pitch controllers to drive compact cannon mounts without inheriting from vanilla CBC cannon mounts.
- Added development groundwork for broader heavy, twin, rocket, and addon weapon compatibility.
Notes:
- Create: Radars compatibility is an early implementation. Please report issues with automatic aiming, firing, or controller setups.
- Addon weapon compatibility currently focuses on mounting/control and safe item routing. Some special launcher or addon ammunition systems may still need dedicated support.
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:fRWr6eJq:4695joRq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fRWr6eJq:4695joRq"
}

