How propulsion-team/create-propulsion-simulated works
1. What the mod is
- This is a NeoForge 1.21.1 Minecraft mod called Create Propulsion: Simulated.
- It is not a standalone gameplay mod; it is an addon for the Create / Sable / Create Aeronautics ecosystem that adds propulsion, fuel handling, and contraption integration.
2. Core domain: propulsion content
- The main gameplay layer lives under content/thruster, content/heat, content/platinum, content/redstone_transmission, content/tilt_adapter, and content/wing.
- The central objects are thrusters (fuel-based, FE-based, creative variants), burners, engines, wings, tilt adapters, and redstone/control blocks.
- Many of these are implemented as block + block entity pairs, with separate renderers/visuals for client-side presentation.
3. Main physics integration boundary
- The mod’s most important boundary is with Create Aeronautics / Sable contraption physics.
- Thrusters do not just emit effects; they contribute force at a point, torque, and multi-thruster behavior on assembled ships/contraptions.
- The files around thruster/SimulatedThrustAdapter, ThrusterForceProvider, ThrusterTorqueMath, and the assets/aeronautics data indicate that propulsion is wired into the simulated craft model rather than only into block-local logic.
4. Fuel and heat pipeline
- Fuel handling is split into a reusable subsystem under content/thruster and content/heat.
- ThrusterFuelManager, ThrusterFuelDefinition, and the generated data/createpropulsion/thruster_fuels/** files define what fuels are accepted from other mods.
- HeatBuffer, HeatMapper, HeatSourceBehavior, and burner classes form the thermal side of the system, feeding blocks like solid burners, liquid burners, and the Stirling engine.
5. Energy and resource variants
- The mod supports multiple propulsion input types:
- Fluid/fuel propulsion for standard thrusters and burners.
- FE-powered propulsion for the Ion Thruster.
- Creative/high-power propulsion for sandbox/testing.
- content/platinum adds a material tier used for several utility blocks and components, including ore generation, casing, tanks, and generator-related infrastructure.
6. Auxiliary block systems
- Several subsystems support propulsion rather than being the propulsion source themselves:
- content/cable implements a cable network with hubs, relays, FE cables, and spool items.
- content/redstone_converter and content/redstone_transmission handle control/signaling.
- content/tilt_adapter provides mechanical alignment/snap behavior for propulsion assemblies.
- content/wing adds Copycat Wings and standard wings for aerodynamic construction.
7. Interaction and assembly tools
- The assemblerstick package provides player tools for manipulating contraptions:
- stick-based assembly interactions,
- auto-gluing,
- moving, cloning, and removing glued contraptions.
- These tools are a separate gameplay interaction layer from the blocks themselves and bridge the player directly to contraption state.
8. Client-side presentation
- Rendering-heavy classes are isolated under each feature package plus client.
- Client presentation includes:
- custom block/entity renderers,
- partial models and CT/visual behaviors,
- particles for ion/plasma/plume effects,
- a looping thruster sound controller,
- tooltip providers for item UI.
- This keeps the simulation and network-facing logic on the server side while the visual layer remains client-only.
9. Compatibility integrations
- The mod has explicit integration boundaries for other systems:
- compat/computercraft exposes peripherals and behavior for CC: Tweaked.
- compat/kubejs registers a KubeJS plugin for scriptable extension.
- registries/PropulsionSableBridge and PropulsionCompatibility likely mediate mod-specific API differences.
- The README also lists fuel compatibility with multiple external mods, and the data/createpropulsion/thruster_fuels directory confirms that fuels are data-driven per mod namespace.
10. Mixin-based hooks
- The mixin package indicates the mod needs to alter behavior in base or dependency code.
- Mixins target things like basin behavior, projectile behavior, and schematic placement.
- This is a sign that some features cannot be implemented only with normal Forge/NeoForge events and need deeper runtime patching.
11. Networking and synchronization
- The network package contains a small packet layer:
- request/sync ship data,
- sync thruster fuel state.
- This suggests the client needs authoritative server state for contraption visuals/UI, while the server owns actual propulsion calculations and fuel consumption.
12. Registration and lifecycle
- The registries package is the bootstrap center for blocks, items, block entities, fluids, particles, sounds, shapes, render types, creative tab, capabilities, commands, and default stress values.
- events contains NeoForge event wiring for setup, client setup, capability registration, and config hooks.
- This is the mod’s startup boundary: content is registered here, then consumed by gameplay, rendering, and compatibility layers.
13. Data-driven content and assets
- A large portion of the repository is generated resources and datapacks:
- blockstates, models, loot tables, recipes, tags, advancements, worldgen, biome modifiers, damage types, and fuel definitions.
- The mod uses Create-style conventions heavily: partial models, ponder scenes, and tag-based integration with other mod ecosystems.
- Architecture-wise, this means much of the content is declarative and loaded by Minecraft’s resource/datapack systems rather than hardcoded.
14. Guidance materials and developer tooling
- The ponder package and NBT scenes are in-game tutorial content for explaining mechanics.
- The wiki/ directory provides API docs for ComputerCraft, KubeJS, and datapack usage.
- Build and release are handled by Gradle plus GitHub Actions, but these are secondary to the runtime architecture.
15. High-level flow to diagram
- Player places a propulsion-related block or uses an assembly tool.
- Server-side block entity logic consumes fuel/energy/heat and updates propulsion state.
- That state feeds contraption/ship physics through the Aeronautics/Sable integration layer.
- Network packets synchronize key state to clients.
- Client renderers, particles, sounds, and tooltips present the result.
Main entry points: PropulsionBlocks.java Registries · ThrusterState.java Thruster Core · ThrusterBlock.java Thruster Blocks · ForgeClientEvents.java Client Layer
Components 23
Bootstrap
Mod entrypoints, registration, and lifecycle wiring.
- Create Propulsion · Main mod entrypoint and config bootstrap.
src/main/java/dev/propulsionteam/propulsionsimulated/CreatePropulsion.java - Registries · Central registration for blocks, items, fluids, particles, sounds, shapes, and bridges.
src/main/java/dev/propulsionteam/propulsionsimulated/registries/PropulsionBlocks.java - Mod Events · NeoForge setup, client setup, capability registration, and config events.
src/main/java/dev/propulsionteam/propulsionsimulated/events/ModSetupEvents.java
Propulsion
Thrusters, fuel, heat, and physics integration.
- Thruster Core · Shared thruster state, fuel handling, torque math, force provision, and simulated ship adapter.
src/main/java/dev/propulsionteam/propulsionsimulated/content/thruster/ThrusterState.java - Thruster Blocks · Standard, vector, liquid, ion, and creative thruster block families.
src/main/java/dev/propulsionteam/propulsionsimulated/content/thruster/thruster/ThrusterBlock.java - Fuel Manager · Accepted fuels and their burn properties for propulsion.
src/main/java/dev/propulsionteam/propulsionsimulated/content/thruster/ThrusterFuelManager.java - Heat System · Heat buffers, mapping, source behavior, and heat contracts.
src/main/java/dev/propulsionteam/propulsionsimulated/content/heat/HeatBuffer.java - Burners & Engine · Solid burner, liquid burner, and Stirling engine logic.
src/main/java/dev/propulsionteam/propulsionsimulated/content/heat/burners/AbstractBurnerBlock.java
Support Systems
Assembly tools, cables, redstone control, wings, and material infrastructure.
- Platinum Tier · Platinum ore, casing, tank, generator, and resource-processing infrastructure.
src/main/java/dev/propulsionteam/propulsionsimulated/content/platinum/PlatinumCasingBlock.java - Cable Network · Cable hub, relay, FE cable, and spool transport network.
src/main/java/dev/propulsionteam/propulsionsimulated/content/cable/hub/CableHubBlock.java - Redstone Control · Redstone converter and transmission blocks for control routing.
src/main/java/dev/propulsionteam/propulsionsimulated/content/redstone_transmission/RedstoneTransmissionBlock.java - Tilt & Wings · Tilt adapter, standard wings, and copycat wing construction parts.
src/main/java/dev/propulsionteam/propulsionsimulated/content/tilt_adapter/TiltAdapterBlock.java - Assembler Tools · Assembler stick, auto-glue, mover, cloner, and remover tools.
src/main/java/dev/propulsionteam/propulsionsimulated/assemblerstick/interaction/AssemblerStickInteractionHandler.java
Integration
Compatibility, mixins, networking, and external API bridges.
- Compat Layer · Shared compatibility entrypoint and Sable/Create API bridging.
src/main/java/dev/propulsionteam/propulsionsimulated/compat/PropulsionCompatibility.java - CC Tweaked · Peripherals exposing thrusters, engines, transmission, and tilt adapters.
src/main/java/dev/propulsionteam/propulsionsimulated/compat/computercraft/CCProxy.java - KubeJS · Scriptable extension plugin for datapack and gameplay integration.
src/main/java/dev/propulsionteam/propulsionsimulated/compat/kubejs/PropulsionKubeJSPlugin.java - Mixin Hooks · Deep hooks into upstream behavior for basins, projectiles, and schematic placement.
src/main/java/dev/propulsionteam/propulsionsimulated/mixin/plugin/PropulsionMixinPlugin.java - Network Sync · Server-client sync for ship data and thruster fuel state.
src/main/java/dev/propulsionteam/propulsionsimulated/network/PropulsionPackets.java
Presentation
Client rendering, sounds, particles, tooltips, and tutorials.
- Client Layer · Client setup, render registration, and visual bootstrap.
src/main/java/dev/propulsionteam/propulsionsimulated/events/ForgeClientEvents.java - Thruster FX · Particles, sounds, renderers, and UI feedback for propulsion blocks.
src/main/java/dev/createpropulsionsimulated/client/sound/ThrusterLoopSoundController.java - Tooltips & Ponder · Tooltip providers and in-game tutorial scenes.
src/main/java/dev/propulsionteam/propulsionsimulated/client/tooltip/TooltipHandler.java
Data
Datapacks, generated resources, and declarative content.
- Fuel Datapacks · Generated and hand-authored thruster fuel definitions.
src/main/resources/data/createpropulsion/thruster_fuels/cdg/cdg_diesel.json - Recipes & Tags · Recipes, tags, loot tables, advancements, and worldgen resources.
src/main/resources/data/createpropulsion/recipe/crafting/thruster.json
Connections 29
- Create Propulsion → Registries: initializes · Entrypoint bootstraps content registration and shared state.
- Create Propulsion → Mod Events: hooks · Entrypoint connects NeoForge lifecycle events.
- Mod Events → Registries: registers · Lifecycle events register blocks, items, entities, and client assets.
- Registries → Thruster Blocks: defines · Registry exposes the propulsion block families.
- Registries → Burners & Engine: defines · Registry exposes thermal blocks and machines.
- Registries → Platinum Tier: defines · Registry exposes platinum material blocks and items.
- Registries → Cable Network: defines · Registry exposes cable transport content.
- Registries → Redstone Control: defines · Registry exposes signal and converter blocks.
- Registries → Tilt & Wings: defines · Registry exposes wings and tilt adapter assemblies.
- Registries → Assembler Tools: defines · Registry exposes player interaction tools.
- Thruster Blocks → Thruster Core: feeds · Block entities update shared thruster runtime state.
- Fuel Manager → Thruster Core: configures · Fuel manager supplies accepted fuels and burn properties.
- Heat System → Burners & Engine: drives · Thermal contracts power burners and the Stirling engine.
- Cable Network → Burners & Engine: powers · FE transport supports energy-fed thermal and utility blocks.
- Redstone Control → Thruster Core: controls · Signal blocks influence propulsion and transmission behaviors.
- Tilt & Wings → Thruster Core: aligns · Assembly parts and wing geometry support thrust assemblies.
- Assembler Tools → Thruster Blocks: manipulates · Player tools act on glued contraptions and propulsion assemblies.
- Compat Layer → CC Tweaked: exposes · Compatibility layer publishes CC peripheral behavior.
- Compat Layer → KubeJS: exposes · Compatibility layer publishes script integration.
- Mixin Hooks → Thruster Core: patches · Runtime hooks adjust upstream behavior needed by propulsion.
- Thruster Core → Network Sync: syncs · Thruster runtime publishes fuel and ship state updates.
- Network Sync → Client Layer: synchronizes · Packets deliver server-authored state to client visuals.
- Client Layer → Thruster FX: renders · Client setup registers renderers, sounds, particles, and overlays.
- Client Layer → Tooltips & Ponder: shows · Client UI exposes tooltips and tutorial content.
- Fuel Datapacks → Fuel Manager: loads · Datapack fuel entries populate the fuel manager.
- Recipes & Tags → Registries: supports · Resources back the registered blocks, items, and generated content.
- Recipes & Tags → Platinum Tier: supports · Recipes and worldgen define the platinum material pipeline.
- Thruster FX → Thruster Blocks: visualizes · Renderers and particles present propulsion block state.
- Tooltips & Ponder → Assembler Tools: explains · Tutorials and tooltips document player assembly tools.