Using Create
Mod version shipped with FlammiCraft: 6.0.41
Create provides mechanical power, processing, moving contraptions, trains and logistics. This fork prepares version 6.0.40 for Minecraft 1.21.1 and NeoForge 21.1.219 or later. The fork includes native TDCreate optimizations and corrections without moving TDCreate machines or saved IDs into Create. Changes in the imported development branch relative to 6.0.10 have not received a complete review.
Requirements and upgrade (6.0.21)
The fork retains NeoForge 21.1.219 and the Create 6.0 baseline. General packaging, mounted-storage and Schematicannon changes are implemented natively. Migrated storage keeps its tdcreate registry and network IDs. On startup, missing [schematiccannon] settings are imported from tdcreate-server.toml into create-common.toml; existing Create values take precedence and the old file remains intact. Update clients, server and Stock Bridge 0.4.0 or newer together.
Find mechanics and recipes
Inspect a Create item's tooltip in your inventory or recipe viewer. For items with Ponder instructions, use the action displayed in the tooltip; its scene demonstrates the arrangement and mechanic. The recipe viewer shows available crafting and processing recipes. Check Minecraft's Controls menu for current bindings and conflicts.
For stopped machinery, inspect the actual power source, rotation direction, speed and stress capacity first. Follow the requirements displayed in game; higher speed does not fix a missing input or blocked output. The official Create documentation provides detailed mechanic instructions.
If a funnel pauses when you open its attached chest, check the chest type.
A trapped chest (minecraft:trapped_chest) emits a redstone signal when opened
and locks the funnel. Use a regular chest if the funnel should keep working
while its inventory is open.
Configuration and dependencies
TDCreate 1.62.0 or later requires this Create fork with fork API 4. Manually update matching builds together on client and server; content and saved IDs remain owned by TDCreate.
create-client.toml: rendering, tooltips and local control options.create-common.toml: common settings, particularly world generation.create-server.toml: recipes, kinetics, fluids, logistics, schematics, equipment and trains. This SERVER configuration loads in the world/server context; it is not an additional global fork configuration file.
The fork retains these NeoForge configuration types and existing keys. Pack-specific recipes and settings belong in the modpack handbook. Registrate, Flywheel 1.0.6 and the Ponder 1.4.0 fork are embedded in Create. An additional standalone Ponder JAR is not required for this arrangement. Optional integrations need their respective mods; compatibility with this development snapshot still needs manual acceptance.
With ModernFix 5.27.27 or later and dynamic model loading enabled, belt models are prepared on demand instead of building models for every addon-expanded belt state at startup. Without dynamic model loading, the original path remains active. Rendering and resource reloads need manual verification with the installed addons and resource packs.
Native improvements and TDCreate
Processing simulations preserve recipe state. Hose pulleys protect block entities from destructive replacement while ordinary waterlogging stays available. Belt, deployer, Redstone Link, tank and Chute improvements run directly in Create. Compatible stationary storage lookups stay inside loaded chunks.
Hover a Threshold Switch value and scroll: Shift uses tenfold steps, Alt 1000-fold steps and Ctrl+Alt 10000-fold steps. Value ranges and ordering remain. Descending belts retain improved contact for transported players.
TDCreate requires this fork. Manually update the matching pair on both client
and server; older TDCreate versions are rejected. TDCreate content, settings and
saved IDs remain owned by TDCreate. Existing global TDCreate switches
optimizations.emptyBelts and optimizations.idleFluidPipes stay effective. Since 6.0.26
optimizations.idleFluidPipes also lets pipes under pump pressure sleep once their
flow is settled. A change of pressure, neighbouring block or neighbouring flow
wakes them. From 6.0.28, disabling the optimization also restores normal
processing on the next tick for pipes that are already asleep. Mechanical Crafters
read the current redstone level on their first tick after reading their block data.
Do not move config files. Overlapping optimizations still yield to Arcadia
Patch Create, Create Advanced Optimization or Create Lazy Tick respectively.
Runtime acceptance with these third-party mods remains pending.
Water wheels and portal tracks
A vertical waterfall next to a water wheel increases its stress capacity. Each block in the longest uninterrupted falling-water column driving the wheel in its current direction adds 15 SU to a small wheel or 30 SU to a large wheel. RPM stays the same. Still water, bubble columns and lava provide no bonus. Engineer's Goggles show total capacity. Remove the standalone Create Real Water Wheel mod when upgrading.
Existing Nether portal tracks remain usable. Newly laid tracks do not connect through Nether portals.
Version changes and acceptance
From 6.0.32, Create restores the appearance of saved FramedBlocks and FramedBlocks+ camouflage when it loads already assembled trains and other contraptions. Trains can stay assembled at the station.
This fork must stay below version 6.1.0 for modpack compatibility. Version 6.0.39 fixes the startup failure with Create: Vibrant Vaults 0.3.2. It also includes the 6.0.37 fix for Create: Dragons Plus 1.11.9.
Before a manual version change, stop the game/server and back up the world and configuration. Use the same verified build on client and server, and check addon compatibility. Bootstrap adds no custom data migration; that does not establish save compatibility or downgrade safety for the imported upstream development snapshot. Downgrading does not undo subsequent changes to the world.
In-game acceptance is pending. Manually check Ponder/rendering, kinetics, processing, transport, contraptions, trains, logistics, schematics and save/reload before accepting the version.
The German handbook describes the same state.
Native performance and TDLibrary
TDLibrary 0.58.0 or later is required as a separate mod on both client and server. Create keeps its NeoForge 21.1.219 build baseline; other addons retain their own loader requirements. Manually update matching Create, TDCreate and TDLibrary builds together.
Funnels and Chutes use live slot indexes in supported inventories to skip empty extraction ranges. Filters, claims, slot order, simulation and exact counts remain active; unknown inventories use the normal scan. Furnace-cart contraptions skip supported mounted stores only when their current tracker proves the fuel absent.
Scheduled destinations can be calculated from detached railway snapshots on
TDLibrary's shared workers. World access and result acceptance stay on the server
thread. Outdated results are discarded; unsupported addons, busy services and
expired requests retain Create's original search. This does not cap total routing
tick time. Coupler points from the inspected Steam 'n' Rails 0.2.1 implementation
can also be captured, so they no longer force the entire network onto the
synchronous search. Changed coupler implementations retain the original fallback.
The global TDCreate key optimizations.threadedTrainRoutes remains
effective; this path is enabled without TDCreate. Operators can inspect shared
CPU costs with /tdlibrary compute and /tdlibrary compute interval. Worker
settings remain in tdlibrary-common.toml; worker counts and capacities require
a restart. No additional configuration file is introduced.
For Create block breaking, including moving drills, TDLibrary workers prepare
an ordered dispatch plan for global loot modifiers. A modifier is skipped only
when its first table condition is provably inapplicable. Random or unknown
conditions, loot generation, claims and inventory changes stay on the server
thread. The complete list remains active while preparing the plan, after data
reloads or when no plan is available. /tdlibrary compute reports the
create:loot-dispatch consumer.
The inspected Sophisticated Core mounted-storage implementation exposes its live slot hints to TDLibrary. Transfers still pass through the outer handler. Changed wrappers, unknown partitions and relevant insertion/overflow upgrades retain the ordinary scan. Breaking, collection and train movement never wait for a worker.
With Entity Culling and Flywheel's indirect backend, stationary presses, mixers and deployers skip hidden frame animations. Ponder, machine ticks, light updates and forced visibility remain active; Nowheel and Create IceCream take precedence. Presses and mixers avoid rewriting unchanged instance transformations. Visible state changes catch up on the next frame.
From 6.0.27, Fluid Tanks and Item Vaults use TDLibrary 0.58.0's block-entity
sleep. Idle tank and vault blocks leave the server tick list and register again
when their fluid, size, structure or saved data changes. A tank with a running
boiler keeps ticking. Create: Connected's Fluid Vessels sleep the same
way and Design n' Decor's Dyed Containers like vaults; Creative tanks and other addon subclasses tick as before. Stationary shafts, cogwheels and encased shafts and cogwheels without a rotation source also sleep; a new neighbour, a connected source or any speed or network change wakes them before rotation spreads.
blockEntitySleep in tdlibrary-server.toml turns sleeping off; /tdlibrary sleep
lists sleeping block entities by type.
From 6.0.30 (with TDLibrary 0.60.0), idle Funnels and Chutes also sleep, for at
most idleTransferSleepTicks ticks at a time (logistics section of
create-server.toml, default 10, 0 = always tick). This covers collecting,
belt-fed, paused and invalid funnels, extractors whose inventory has not changed
and empty chutes that found nothing to take. Neighbour, filter, redstone and air
flow changes, inserted items and loaded data wake them at once. New items in a
source inventory or above a chute are picked up at most that many ticks later.
From 6.0.32, funnels refresh their access to the attached inventory after waking
if a neighbour change invalidated it.
These changes introduce no new save format or world migration. Automated comparisons do not replace in-game rendering, throughput, schedule and save/reload acceptance. General MSPT or FPS gains require representative runtime measurements.
Additions in this snapshot
The original Create belt behavior page covers supported orientations and switching from the experimental belt build.
The fluid-aware Schematicannon page covers supply, shortages, skipping and use with the ME interface.
The logistics and interaction additions and Entity Observer pages explain recipes, settings and controls.
The extended goggle overlay adds filters, rotation direction, fan, burner and pulse information plus an assignable toggle key.
Unsuccessful scheduled route searches retry at increasing intervals with a per-train offset, capped at 359 ticks. Synchronous searches and the TDLibrary path share the failure state. Successful navigation and ordinary waiting phases reset it. Saving and loading retain only condition state belonging to the active waiting entry, removing excess old entries.
Batched contraption block changes share a collider rebuild; a collision query refreshes any pending rebuild before use. Compiled address patterns use a bounded cache. Tree fertilizer reuses one simulation level per world and clears it before each use. Runtime acceptance and comparable performance measurements remain pending.