Automating crops with TDPlanter
Mod version shipped with FlammiCraft: 3.44.0
TDPlanter requires TDLibrary 0.58.0 or newer on both client and server. With GuideMe installed, the in-game guide is available in English and German. With Ponder installed, hold its configured key over a Booster part to see how to build it.
TDPlanter 3.31.0: LBR extensions now belong to the Little Big Redstone fork. Earlier LBR descriptions in this handbook are historical; components, recipes, editor and readers are maintained in LBR. Old TD IDs are not migrated. Client and server need matching updated JARs.
TDPlanter uses loaded growth, soil, fertilizer, interaction and transformation recipes. The current server's recipe viewer and diagnostics determine supported combinations.
Jump to your first harvest, harvest filters, the Booster, or troubleshooting.
Start a crop
- Craft and place a Rustic Planter Pot or a modular Planter Pot using its current recipe.
- Insert appropriate soil and a seed or sapling manually. These slots are not automation inputs.
- Read the status. Hover over it or focus it with Tab to see the diagnosis. The modular pot shows it in Overview.
- Wait for one complete growth and harvest cycle and inspect the actual output.
- Put a container below a Simple Planter. Install a Hopper Module for automatic modular-planter output and leave receiving inventory space. If that inventory takes nothing, the next attempt waits 2, 4 and at most 8 output intervals; a successful move or a change of the block below ends the pause.
Simple Planters have no energy, tool, filter, module or tier slots. Mandatory-hoe crops cannot grow there when the server requires a hoe. All modular tiers have two output slots; material appearance and performance tier are independent.
Starting with 3.38.0, Lollipop Flower, Cyan Rose and Protea Flower from Oh The Biomes We've Gone grow on natural soil such as dirt in either planter. Pink, blue and white Magnolia Flowers from Regions Unexplored and Liverwort from Crop Critters require shears in a modular Planter for harvest. Liverwort also accepts farmland. Each of the seven plants yields one of its own item per 1,200 base ticks. The recipes were checked against the installed mod JARs. In-game testing is pending.
Puffbomb Mushrooms
Look for rare Puffbomb caps in newly generated Plains chunks. Silk Touch drops the cap itself. Breaking a cap normally yields up to two slices or has a small chance to yield a mushroom. Fortune improves the chance of a mushroom. Plant it on dirt, mycelium, or farmland. It grows through three stages, and bone meal can speed it up. Break it at the last stage for two mushrooms. Let it finish growing to produce a cluster of caps. The growth burst knocks back entities.
In a planter, insert mycelium and a Puffbomb Mushroom. With no shears, harvest two mushrooms per 1,200 base ticks. With shears in a modular planter, harvest one or two cap blocks instead, per 1,800 base ticks. The planted mushroom stays in place for further harvests.
Cook slices into steak in a furnace, smoker, or on a campfire. A smoker turns whole mushrooms into gunpowder. Eating a whole mushroom raw gives Ticking. Just before the effect expires, it causes a blast that can damage entities and leaves blocks intact.
These mushrooms use their own tdplanter: IDs. Existing Crop Critters mushrooms
keep their original IDs.
Modules and Ultra planting
Datapack interactions cannot install or remove modules on a Simple Planter; its built-in export remains intact. Waxed planters do not execute datapack interactions. Use an axe to unwax them. The unwax action is invalid and is rejected when recipes load.
A Growth Lamp requires a Glass Hood. Install modules directly or through their transformation recipes. Use the Overview eject buttons to remove modules, with enough inventory space and the planter unwaxed. Removing the hood also removes its lamp. Drain irrigation first and finish compost conversion before ejecting that module.
Normal right-click on an Ultra Planter fills both empty plant slots when enough seeds are held; sneak-right-click fills one. Existing crops are retained.
Filter the harvest
View harvest previews possible drops. With a Filter Module fitted, use Choose harvest to toggle individual results or Advanced to edit item, tag and drop-group rules. Harvest only these allows selected results, and Do not harvest these excludes them. Individual choices override broad rules. Select Done to return. A filter allowing no outputs prevents harvesting.
Craft one configured filter with exactly one new blank to duplicate it; the original remains in the grid. Sneak-use in the air resets the entire held filter stack. The separate Settings Card copies settings with sneak-right-click on a source planter and applies them with normal right-click on the target.
Supply and configure the Booster
Connect FE to the Energy Port and feed accepted plant remains into the Plant Remains Port. Open the Core and check whether it is active in Overview. Set dimensions and offsets in Work area. Show range outlines the active area in white and a different draft in cyan. Apply saves the draft. The status at the top tells you whether the new area is pending until the next billing period or already active.
Optional fertilizer increases yield through a dedicated slot. See Booster fertilizer for the supported inputs and how billing works.
A new core placed inside a complete Booster shell forms the structure on its first server tick and then accepts plant remains. The rest of the shell can stay in place when replacing the core. GameTests cover this sequence; manual in-game acceptance is still pending.
Diagnose stalled production
After startup or a recipe reload, a planter may show Preparing recipes. Wait for preparation to finish. Growth and harvesting resume automatically, with contents, energy and saved progress intact.
Use /tdplanter diagnose held for a held plant and /tdplanter diagnose block for the aimed planter. diagnose definitions reports loaded definitions; reload-report shows the latest reload. Complete coverage scans and JSON exports require permission level 2.
Definition conflicts are checked per seed and soil using actual recipe precedence. Coverage scans and compatibility exports count only enabled, unambiguous combinations as supported; disabling one soil does not exclude other usable soils for that plant. Jade queries show the existing booster state without triggering billing or compost consumption. Long datapack recipes synchronize their full work values for the progress display.
Large recipe diagnoses retain the recipe and status guidance and report the number of omitted hints to keep the menu within its network limit. Rotating a planter refreshes cached FE connections; input remains limited to its new rear side. Mining, dismantling, or replacing a Booster Core drops its remaining plant items with their components intact. Property-only core state changes do not spill contents. These world interactions have GameTest coverage, with in-game execution still pending.
The required display field in soil recipes currently has no rendering effect. The client renders the inserted soil block's own default model; items without a block have no soil model. This field does not override that behavior.
Check full outputs, excluded harvests, required tools, soil, seeds and redstone mode first. A plant-like item name does not establish growth-recipe support. Datapack changes support /reload; replacing the mod JAR requires a full restart. The reference covers layout, redstone and datapack recipes.