Planter layout, filters and recipe reference
Mod version shipped with FlammiCraft: 3.44.0
Features
Herbs & Harvest mint, basil, bay leaf, chive, cilantro, dill, lemongrass, oregano, parsley, peppercorn, rosemary, sage, and thyme have explicit growth recipes. Plant their seeds on crop soils (tdplanter:crop_soils) to harvest one fresh herb (fresh_*) plus one seed per base cycle. A cycle takes 1,200 ticks before modifiers and needs no tool or fertilizer, so Simple Planters can use these recipes too. Harvest products were checked against Herbs & Harvest 1.21.1-24; in-game acceptance is still pending.
Manually insert an ordinary red or brown Minecraft mushroom on natural soil. Without shears, harvest 2–5 matching mushrooms per 1,200 base ticks. With shears in a modular planter, harvest 1–2 matching mushroom blocks instead, per 1,800 base ticks. At 20 TPS these are 60 and 90 seconds before modifiers, compared with 2,400 base ticks for automatically detected trees. Farmer's Delight retains five mushrooms without shears and additionally retains one matching colony alongside the blocks with shears. The seed remains in place; block seeds are no longer needed or supported. Simple Planters use the ordinary mushroom branch; mushroom stems are not produced. Tool changes retain completed work, so late shears still require the remaining work up to 1,800. Paid output queues remain intact. Recipe viewers list the possible outputs; hover the seed for both base-work values. Actual client presentation still needs an in-game check.
- One universal planter instead of separate blocks for every tier and material combination
- A rustic Simple Planter variant with a built-in downward output for hands-off setups without tools, modules, tiers, or energy
- Manually inserted soil and seeds, with optional hoes, shears, and fertilizer
- Right-click either planter with a supported seed or sapling to insert one directly into an empty seed slot
- A two-block-tall glass hood that acts as a growth upgrade
- An optional Growth Lamp with a rear-facing FE connection
- Two permanent output buffer slots and automatic harvesting in every planter
- Server configuration snapshots refresh on config load/reload, and empty buffers skip export lookups.
- Harvesting runs exclusively on the server into the output buffer; there is no manual harvest button, packet, output-mode setting, or interaction action. Fertilizer and hoe wear are committed once when a valid growth cycle starts, while shears wear is committed when that cycle is harvested. The Details tab keeps showing the cycle's locked fertilizer as its normal item icon and tooltip even after the input slot empties. Before the first batch fits, a blocked harvest retains its roll across saves; relevant input, recipe, or effective configuration changes invalidate that unpaid result. Any paid remainder survives saves and input changes, fills free output space automatically, and pauses growth until fully transferred. Breaking a planter drops both buffered and queued output.
- Fertilizer paid for multiple cycles retains its active effect until those cycles are exhausted, including after the last item is consumed and across save/load. Replacing the slot contents affects the next payment, not the already-paid cycles.
- Growth recipes can require a specific supported fertilizer. Reusable water-bucket fertilizer remains available for custom datapacks; built-in aquatic plants use the irrigation tank.
- The Irrigation Module holds 4,000 mB of water, accepts buckets and fluid pipes, and gives 25% faster growth with at least 100 mB available. A successful irrigated harvest consumes 100 mB; blocked harvests consume none. Living aquatic plants, rice, and Cattail Sprout require a Glass Hood and stored water. Removing the hood or draining the tank pauses them without losing progress. Water appears inside the hood while the tank contains water. Dead coral remains dry.
- The Compost Module diverts compostable blacklist exclusions into a saved buffer. Once per second it converts up to one stack of fertilizer, capped at 64 items and the selected destination's available space. The default recipe consumes eight plant items per bone meal, processing up to 512 plant items per second. The destination is the output buffer by default, or the fertilizer slot. Manual/redstone pauses stop conversion; a full selected destination preserves the inputs. Whitelist exclusions are not composted.
- Datapacks can grant nearby entities or tagged blocks growth and yield bonuses. Entity tags support modded pollinators. By default, only the strongest bonus per group and effect applies;
environment.stackNeighborBonuses=truemultiplies all matching condition bonuses instead; the server caps each combined neighbor multiplier at 1.25 by default. Built-in recipes do not enable neighbor bonuses. - A Hopper Module for tool and fertilizer resupply and downward output export
- A wax mode that freezes the current state
- Basic, Advanced, Elite, and Ultra tiers with configurable values; Ultra has two manual seed slots with independent growth cycles and shared soil, tools, energy, filter, and output
- Interchangeable material designs and state-preserving in-world and crafting upgrades
- A portable, copyable Filter Module with direct planter editing, item pictures, individual harvest choices, and advanced item/tag/group rules
- Field-crop and compact bonsai/tree rendering
- Bonsai wood and foliage follow the resolved growth recipe, with distinct Pewen and eucalyptus silhouettes and leafless Thornwood/Licoroot branches. Optional Alex's Caves recipes correct Pewen, Ancient, Thornwood, and Licoroot harvest materials. With Quark installed, Azalea and Flowering Azalea yield Quark Azalea Logs instead of Oak Logs.
- Reloadable datapack recipes and optional KubeJS support
- Automatic discovery of conventional crops, stems, saplings, dirt, and farmland from loaded registries and tags; detected stems use their fruit block's loot table
- Optional JEI, EMI, REI, Jade, GuideME, and KubeJS integration
- Optional growth recipes also support Alex's Caves Cycad, Curly Fern, and Flytrap, each yielding its own plant item.
- Optional growth recipes support 93 additional flowers, bushes, grasses, mushrooms, cacti, and decorative plants from Oh The Biomes We've Gone, Regions Unexplored, Some More Blocks, and Candlelight. Ordinary plants use natural soils; cacti and Aloe Vera use sand. Sandy Grass, Small Desert Shrub, and Dune Grass accept natural soils or sand. Grasses retain their shears-dependent harvests, and Cattail Sprout needs natural soil or sand plus a hood and irrigation water.
- Optional recipes also cover 52 built-in Mystical Agriculture essence crops, all 16 Botania mystical flowers, and Immersive Engineering hemp. Mystical Agriculture recipes produce essence without extra seed drops. Farmer's Delight cabbage and onion use automatic detection; tomato and rice retain explicit recipes.
- With Farmer's Delight installed, wheat produces straw only when a knife is installed in the harvest-tool slot. Knives use the configured shears wear and accept the same manual/menu/automation insertion routes. Actual shears remain necessary for shears-required plants. The standalone farming fallback retains its native wheat-straw behavior.
- See Datapack Recipes for the installed-mod compatibility tests.
- A complete LDLib2-powered planter and Filter Module interface with reusable tabs, slots, buttons, and progress components
- English and German localization
Field plants use the resolved recipe's display.model block; sweet berry bushes show their configured growth stage. Nearby block and entity conditions refresh every 20 ticks during growth, so changes can take up to one second at 20 TPS to affect growth. Other conditions remain immediate, and every new harvest checks its required conditions and yield bonuses against the current world state.
Indigo Jacaranda Bush, Prairie Grass, Bladed Grass, and Steppe Shrub accept natural soils. Indigo Jacaranda Bush yields one bush without a tool. The other three yield one plant with shears, or have a 12.5% chance of yielding one wheat seed without shears. A Simple Planter has no shears slot and therefore only uses their wheat-seed branch. These definitions follow the installed mods' loot tables; in-game acceptance is still pending.
Optional Booster fertilizer
The Booster still requires FE and plant remains. Its Overview has one separate fertilizer slot that supports click and shift-click insertion/removal, with the player inventory and hotbar below the tabs. The same plant-remains port exposes four plant-remains slots followed by the fertilizer slot. Their capacities are independent: a full buffer does not prevent filling the other. Automation cannot extract either resource.
Loaded tdplanter:fertilizer recipes with yield_factor > 1 determine acceptance and strength. Defaults are bone meal ×1.5, Farm & Charm Fertilizer ×1.75 and Alex’s Caves Fertilizer ×2.0; optional items require their loaded recipes. Water buckets do not qualify. One fertilizer stack is supported, without mixing varieties. Fertilizer affects yield only and does not meet a growth recipe's local planter-fertilizer requirement.
One item buys one plant-remains interval, normally 200 active ticks regardless of planter count. A new purchase occurs at the beginning of an active bill with no remaining fertilizer credit. Missing FE, plant remains or structure prevents a purchase. The paid factor and remaining time survive an empty or replaced input stack, pauses, recipe reloads and saves. Recipe changes affect the next purchase; invalidated stock remains available for manual removal. Without more fertilizer, the ordinary Booster continues working. The menu and Jade distinguish stored quantity, paid factor and remaining active ticks. Breaking the core returns stored fertilizer with item components intact. Billing periods end no later than the paid fertilizer effect, so available stock renews without a bonus gap after pauses or reloads. FE and plant remains are charged only for the actual period length.
Multiply each Booster's yield by its paid fertilizer factor before strongest/stacked selection. Basic with bone meal gives ×1.875. Without stacking, Ultra with Alex’s Caves fertilizer gives ×5. With stacking enabled, the existing combined yield cap still applies (×2.5 by default), so fertilizer has no extra benefit at an already reached cap. Local planter fertilizer applies separately; the existing total harvest multiplier cap of ×16 remains. Client presentation, GUI scaling and multiplayer interaction still require manual in-game acceptance.
Requirements
Required:
- Minecraft 1.21.1
- Java 21
- NeoForge 21.1.250 or newer; developed and tested with 21.1.250
- LDLib2 2.2.37 for Minecraft 1.21.1 and NeoForge
- TDLibrary 0.58.0 or newer, installed on both client and server
Optional:
- JEI, EMI, REI, Jade, GuideMe, Ponder, and KubeJS are optional. GuideMe opens the English and German in-game guide. Ponder shows the Booster assembly tutorial.
TDPlanter is declared as BOTH. In multiplayer environments, the server and all clients must use the same mod version.
Planter Layout
| Component | Purpose | Automation |
|---|---|---|
| Soil | Determines the soil class and growth modifier | Manual only |
| Seed | Selects the crop or tree | Manual only |
| Hoe | Speeds up the growth cycle by default | Refillable with the Hopper Module |
| Shears | Enables leaf drops and other recipe-specific results | Refillable with the Hopper Module |
| Fertilizer | Increases yield; consumption is configurable | Refillable with the Hopper Module |
| Filter Module | Stores the configured output whitelist or blocklist | Manual module slot only |
| Output | Stores filtered harvest results | Extractable downward with the Hopper Module |
The glass hood attaches to the planter and occupies the block above it. The Growth Lamp is installed as an additional hood module and accepts FE only from the side that is behind the planter relative to its facing direction.
Both planter variants can be rotated by right-clicking with a Create Wrench, a Mekanism Configurator in Rotate mode, or any wrench in the common c:tools/wrench tag. Shift-right-click with these tools dismantles either planter variant or individual Booster blocks through the normal player block-breaking path, including regular drops and protection checks. The Mekanism Configurator also supports dismantling in Wrench mode. Clicking an installed glass hood dismantles its planter as well.
Changes to a modular planter's facing invalidate its cached capabilities, so cached FE connections follow the new rear side. Mining, dismantling, or replacing a Booster Core drops its stored plant remains separately with item components intact; changing only its formed or active state does not spill its inventory. These transitions have GameTests; in-game acceptance remains pending.
A vanilla Hopper placed on top of an installed Glass Hood inserts hoes, shears, and fertilizer through the hood tip. Soil and seeds remain manual inputs.
Right-clicking a modular planter with a Growth Lamp requires an installed Glass Hood. If the hood is missing, a message explains the requirement, the lamp is not consumed, and the menu stays closed for that item interaction. Ordinary right-clicks still open the menu without a hood.
Right-click an Ultra Planter with seeds or saplings to fill both empty plant slots with the held plant. Shift + right-click fills only one empty slot per click. If one slot already has a plant, either click fills the remaining slot without replacing the existing plant. Survival consumes one held item per newly filled slot; holding only one item fills only one slot. Creative keeps the held stack. Lower tiers and Simple Planters retain their single plant slot.
In Survival, mining either the pot or its upper hood/lamp block drops the entire planter with its installed modules, tier, material, Filter Module, and stored energy. Working contents drop separately. Mining the upper block no longer detaches the hood.
Use the eject buttons beside the modules in the Overview tab to remove them. Ejecting the hood also ejects its lamp and plays the glass-breaking sound. Ejecting the hopper stops external item transfer but preserves buffered output and open menus. Drain irrigation water before ejecting its module; a compost buffer must finish converting or be recovered by breaking the planter before its module can be removed. Breaking drops both seeds and compost inputs separately while the planter item retains its modules and water. Ejected modules go into the player's inventory. If there is not enough room for all returned modules, they remain installed. Waxed planters must be unwaxed before ejecting modules.
Installing Modules by Crafting
Combine exactly one modular Planter item with the modules you want to add in any arrangement. These recipes fit the inventory's 2x2 grid as well as a crafting table:
| Ingredients | Result |
|---|---|
| Planter + Hopper Module | Planter with Hopper |
| Planter + Glass Hood | Planter with Glass Hood |
| Planter + Glass Hood + Growth Lamp | Planter with Hood and Lamp |
| Planter + Hopper Module + Glass Hood + Growth Lamp | Planter with all three modules |
| Planter already containing Hopper and Hood + Growth Lamp | The same Planter with its Lamp added |
The recipe consumes one item from each occupied ingredient slot and returns one equipped planter. Installed modules, tier, material, stored contents, Filter Module configuration, energy, wax, and custom item components are retained. Crafting can equip a waxed item while keeping it waxed. Duplicate modules, modules already installed on the planter, a lamp without a hood, unrelated extra ingredients, and Simple Planters produce no result. Tier or material upgrades still use their separate one-catalyst recipes.
Module catalysts use the existing tdplanter:transform recipe type. For example, data/tdplanter/recipe/transform/install_hood.json contains:
{
"type": "tdplanter:transform",
"catalyst": { "item": "tdplanter:glass_hood" },
"target": { "install_module": "hood" },
"crafting": true,
"in_world": false
}
install_module accepts hopper, hood, lamp, irrigation, or compost. Module targets cannot also change tier or material and must disable in_world; direct module installation is handled separately. Override the five transform/install_* recipes to change catalysts. Each catalyst must resolve to exactly one matching crafting transform. The existing planter_transform_crafting recipe combines matching module transforms when multiple modules are supplied; larger sets need a crafting table.
Tiers and Designs
The four tiers are represented by colored bands, each with a horizontal sheen that runs dark at the edges to bright in the middle:
- Basic: grey
- Advanced: red
- Elite: blue
- Ultra: purple
Higher tiers can improve growth speed, yield, FE storage, and energy intake. Every planter has two output slots regardless of its tier or modules. The tier values and energy costs are configurable on the server.
Material designs are independent of tiers. Transformations preserve the inventory, filters, energy, growth progress, and installed modules. For example, a terracotta planter can be upgraded without losing its visual material family.
Built-in material recipes cover vanilla planks, logs, wood, Nether stems and hyphae (including stripped variants), bamboo blocks and mosaic, solid stone building blocks, all concrete colors, and plain, colored and glazed terracotta. Right-click an unwaxed modular planter with one material block, or craft the planter with that block. Leaves, ores, redstone and utility blocks, concrete powder, stairs, slabs and walls are excluded. Simple Planters retain their fixed appearance. Datapacks can override each tdplanter:transform recipe separately.
Simple Planter
The Simple Planter is a rustic, single-tier pot for hands-off farming. It holds soil and a seed, always pushes the harvest into the container below it, and can be waxed. It has no tool, fertilizer, or filter slots, takes no modules or tier upgrades, and has no energy. Growth uses the same tdplanter:growth recipes at the Basic rate. When the server config sets the hoe requirement to always_required, the Simple Planter cannot grow hoe-gated crops. It has a default crafting recipe of eight terracotta around a hopper, which a datapack can override.
Redstone and Comparators
A redstone signal powering the lower planter block pauses growth and new harvests in both variants. Growth progress is retained and the Growth Lamp consumes no FE while paused. Both interfaces also provide a persistent Production: On/Off button. Redstone is authoritative: while powered, the button shows Redstone: Off and cannot manually resume production. Removing the signal restores the saved manual preference. Already paid output continues draining during either pause.
Already harvested items, including a paid harvest queue, can continue filling and leaving the output buffer while powered. Tool and fertilizer automation also remains available. Waxing still freezes the planter and blocks item transfer.
A comparator reading the lower block measures output-buffer fullness by default: 0 when empty, 8 for one full stack and one empty slot, and 15 when both slots are full. The Details tab can switch it to operating status: 0 running, 5 waiting for an input or condition, 10 output blocked, and 15 recipe error. No Hopper Module is required.
The modular planter's third comparator mode, Harvest, emits strength 15 for four game ticks after a successful harvest. It also powers the front face, allowing nearby redstone machinery to respond. Harvests that happen together share a pulse. The pulse is transient and is not replayed after loading.
The Details tab also tracks successful harvests, produced items, average harvests per hour, the last harvest, and time blocked by a full output. Its copy icon places the current seed, soil, status explanation, and effective growth and yield factors on the clipboard for support reports.
Filters
Select View harvest in Overview to preview possible results from the current plant and soil. With a Filter Module fitted, select Choose harvest to edit which results to keep. Ultra previews include both active seeds and use the same shared filter. The preview uses the current tools, and recipe amounts, chances and growing conditions still apply. Select all affects the pictured items and keeps rules for other plants. Undo restores the previous edit. Done sends queued changes and returns to the planter.
Servers can optionally enable filter.boostDropChances (off by default) to raise the chance of allowed drops when a Filter Module excludes a possible drop. filter.dropChanceMultiplier defaults to 1.25 and is capped at 2.0; final chances cannot exceed 100%. Rare special drops can opt out per growth-recipe drop with filter_chance_bonus_excluded, as TDPlanter's built-in rare special drops do. The setting changes chances, not stack sizes.
The Filter Module stores its settings in the persistent tdplanter:filter_config item component, serialized with the item in NBT. New modules stack normally, and configured modules stack when all their settings match:
- Exact items
- Item tags
- Logical drop groups such as logs, sticks, or leaves
- Whitelist and blocklist modes
- Individual item choices, which take precedence over the mode and broad rules
You can also hold the module and right-click to configure it before installation. Inventory clicks copy an item into the rules without consuming it; JEI, EMI, and REI can supply ghost ingredients or drag-and-drop entries. Harvest only these allows matching entries, while Do not harvest these excludes them. Advanced exposes all saved rules and text fields for tags such as minecraft:logs (optional #) and logical drop groups such as logs (optional @). Individual harvest choices override these general rules; remove an individual rule to return that item to the general mode. Rule tooltips show matching results for the current plant where available.
Give the module to another player or insert it into another planter to reuse its settings. Changing plants never deletes saved rules. Unknown item IDs already in the module are preserved and simply match nothing until the mod is available again. A lower server entry limit restricts new rules without trimming the saved module. An empty module slot means no filtering. A filter with no allowed results prevents harvesting; it does not leave rejected items in the output buffer.
To duplicate a filter, craft one configured Filter Module plus one new Filter Module in any crafting grid. Take the configured copy from the result slot; the original remains in the grid. The two modules are independent. The recipe rejects two configured modules, multiple blanks, or unrelated ingredients. A new blank is a module without a saved filter component; a deliberately configured empty filter is still a valid original. The copy keeps the blank's custom name and other components.
Hold a Filter Module stack in either hand and Shift + right-click into the air to clear its saved rules and mode. This resets the entire held stack to blank filters for stacking and copying, preserving its count, custom name and other item data. A message confirms the reset. Aiming at a block or using it without Shift does not clear the filter.
The editor closes if the source module, plant, soil, installed tool types, recipe revision, distance, or writable state changes, preventing stale edits. Recipe previews use the resolved plant definition; supported stem loot is inspected without rolling an actual harvest. Unsupported dynamic loot provides no item preview and can still be filtered using the saved-rule editor. The UI preserves its page and input drafts across resizing and uses one scale transform for drawing and hit testing. Tab/Shift+Tab navigate editor controls; Enter/Space activate focused buttons.
Harvest choices are recalculated whenever the installed filter is opened. Tool-gated drops, such as leaves, appear when a matching tool is installed. Removing the tool hides those choices without deleting their saved rules.
Existing saved planter filters are migrated into an installed Filter Module when their state is loaded.
Datapack Recipes
The optional growth field shears_base_ticks selects a different positive base-work requirement while the harvest-tool slot holds an item tagged c:tools/shear. Without that field, both tool states use base_ticks. Tool changes retain completed work rather than scaling its percentage. An increased requirement resumes growth before harvesting; a shorter requirement permits the ordinary harvest once its work is complete. The field is supported by JSON recipes, the KubeJS growth schema and the pack validator. EMI and JEI include both work values in the seed tooltip.
TDPlanter registers five custom recipe types:
tdplanter:growth– seeds, soil, optional tool/fertilizer requirements, growth duration, rendering, and dropstdplanter:soil– valid soils, classes, and growth modifierstdplanter:fertilizer– fertilizers, yield modifiers, and optional consumption valuestdplanter:interaction– data-driven right-click interactionstdplanter:transform– tier and material transformations
Recipes are stored under data/<namespace>/recipe/. Explicit definitions are resolved deterministically, while conflicts and unrecognized crops can be investigated with the diagnostic commands.
Soil recipes still require display as a resource ID, but this field currently has no rendering effect. The client uses the inserted soil block's own default model; non-block items have no soil model. Changing display does not override either behavior.
Growth recipes may set requires_hoe, requires_shears, and an optional required_fertilizer ingredient independently. The boolean fields default to false. A required fertilizer and hoe are validated and paid when a growth cycle starts; their effect remains locked for that cycle even if the input is consumed or removed. Required shears remain a harvest-time requirement and receive their configured wear only after a successful harvest. Drop-level tool_tag and without_tool_tag conditions inspect the shears slot and use the same harvest-time shears wear. Because the Simple Planter has no tool or fertilizer slots, it cannot process recipes that enable these requirements.
For aquatic plants, set display.water to true to render water inside an installed Glass Hood when the irrigation tank is nonempty. This field defaults to false. Add {"type":"hood","value":"true"} and {"type":"fluid","value":"minecraft:water"} to require a hood and at least 100 mB of stored water. Conditions are checked again before every new harvest, including blocked retries. A Simple Planter cannot install these modules. Lily pads float on the displayed surface. nearby_entity, nearby_entity_tag, and nearby_block_tag conditions support radius (1–8), required (default true), yield_factor and growth_factor (1–4), and bonus_group (default neighbors). Use required: false for an optional bonus. With environment.stackNeighborBonuses=false (default), only the strongest factor per group and effect applies; different groups multiply up to environment.maxNeighborBonusFactor (default 1.25). Set environment.stackNeighborBonuses=true to multiply all matching condition factors, including those in the same group. The combined cap applies in both modes. Setting the cap to 1 disables bonuses while retaining required conditions. Extend tdplanter:pollinators to include modded species; tdplanter:greenhouse_cores is empty until a custom core is provided.
Conventional crops, berry and grape bushes, melon- and pumpkin-style stems, saplings, natural soil blocks, and farmland blocks are added as automatic fallbacks at reload time. The additive tdplanter:natural_soils item tag is the opt-in boundary for ordinary plants and automatically detected trees; it excludes farmland and sand while including full-block bonus soils such as Farmer's Delight Rich Soil and Farm & Charm Fertilized Soil. Datapacks may extend this tag without adding a soil recipe unless custom growth or yield factors are needed. Built-in definitions cover vanilla bamboo, cactus, chorus, glow and sweet berries, mushrooms, Nether fungi and wart, and the other non-conventional plants that cannot be inferred safely. Tree detection also reads conventional trunk, log, foliage, and leaves providers from custom configured features. Sapling-named plants that grow a single same-named stem block are supported without inventing a leaves drop, while ambiguous matches remain unsupported. Explicit datapack definitions always take precedence. Right-clicking an inserted soil with a compatible hoe applies NeoForge's HOE_TILL transformation, including transformations supplied by other mods.
Automatic crop detection prefers the block actually planted by a seed over additional blocks matched by name. For juvenile blocks with a different name, it also checks the seed's crop name to identify mature produce. This handles Farmer's Delight 1.3.4's budding tomato stage without conflicting recipes or a seed-only harvest.
Hover over the planter status or focus it with Tab for an explanation and next steps. Recipe errors distinguish missing inputs, unsupported seeds, unsuitable soil, disabled cultivation, and conflicting recipes. Unsuitable-soil explanations list alternatives that resolve to an enabled, unambiguous recipe. Conflicts identify the affected seed, soil, and recipe IDs. The server supplies these explanations and the client translates them into English or German.
Menu diagnoses contain at most 16 detail lines. Long explanations retain the recipe, the first hints, and the final status guidance, with a count of omitted hints. The full recipe remains available to datapack authors; this display limit does not limit recipe conditions. Automated tests cover large recipe diagnoses through the packet codec.
To run all installed-mod compatibility checks after mod updates, pass "-Ptdplanter.compatModsDir=<absolute-path-to-mods-folder>" to test and runGameTestServer. Version-independent filename patterns in gradle.properties select exactly one Alex's Caves, Farmer's Delight, Farm & Charm, Architectury, and Mekanism JAR. The installed Alex's Caves fork uses TDLibrary and no separate CodxLib artifact. Missing or duplicate matches fail the build instead of silently testing the wrong artifact. These dependencies are used only for tests and are never bundled with TDPlanter.
The narrower tdplanter.farmersDelightJar, tdplanter.alexsCavesModsDir, tdplanter.farmAndCharmModsDir, and tdplanter.mekanismJar properties remain available for isolated checks. The optional GameTests cover Farmer's Delight growth and harvesting, Farm & Charm soil insertion and tilling, Alex's Caves registry compatibility, and Mekanism output transport before and after hood changes.
Optional datapack-only integrations deliberately have no restrictive dependency range in neoforge.mods.toml: their neoforge:mod_loaded recipes remain eligible after compatible mod updates, while the installed-artifact tests detect renamed or removed registry content. Java API dependencies keep their declared ranges in gradle.properties.
KubeJS discovers the TDPlanter schemas automatically. Modpacks can therefore create the same five recipe types from server scripts without modifying TDPlanter code.
Pack authors can start with the ready-to-copy example datapack, check its files with rtk proxy python tools/validate_pack.py examples/tdplanter-pack-starter, and use the pack author guide to adapt recipes, server settings, and optional mod support.
Datapack Interaction Rules
Datapack module actions are restricted to modular planters. Simple Planters may be waxed but cannot gain or lose modules through interaction recipes. Waxed planters remain read-only. Use an axe to unwax them; unwax is rejected as an unknown recipe action during loading and by the pack validator. Existing recipes using it must be removed or rewritten before reloading. These rules have automated source-level checks; in-game acceptance remains pending.
Diagnostic Commands
/tdplanter diagnose held/tdplanter diagnose block/tdplanter diagnose definitions/tdplanter diagnose all [namespace]requires operator permission level 2 and scans every loaded item for covered seeds, recipe displays and drops, soils, and candidates that still need review. Candidate names must end in a plant or soil term, so crafted variants such as bamboo buttons, End Stone bricks, stairs, walls, and ores are counted as ignored name noise instead of missing recipes. The first 40 review candidates are shown in chat; covered recipe results and the complete review list are written to the server log, while ignored name noise is summarized as counts. Datapacks can suppress reviewed false positives through the additivetdplanter:coverage_ignored_plantsandtdplanter:coverage_ignored_soilsitem tags without changing the diagnostic code./tdplanter diagnose export [namespace]writes the same coverage model as structured JSON tologs/tdplanter/diagnosis-all.jsonordiagnosis-<namespace>.json. Each run replaces the previous file for that scope. The report includes runtime and loaded-mod versions, reload warnings, classified plant and soil entries, namespace review counts, expanded plant-to-soil and soil-to-plant compatibility maps, and the effective growth, soil, fertilizer, interaction, and transform recipes./tdplanter reload-report
These commands do not modify inventories, recipes, or block states. Full coverage scans and exports require operator permission level 2. The export command writes its
report file under logs/tdplanter.
Conflict checks use effective recipe resolution for each seed and soil, including priorities, explicit definitions over automatic fallbacks, and explicit disabled overrides. Compatibility maps include only enabled, unambiguous pairs. A plant remains supported if another soil resolves successfully; unresolved conflicts require review instead of counting as support. These rules are covered by automated tests; in-game command acceptance remains pending.
Jade's planter tooltip reads existing booster bonuses without advancing booster ticks, billing, or compost consumption. The optional Jade GameTest is included with -Ptdplanter.jade=true; it checks tooltip queries against a due bill and the following ordinary booster tick. Compiling it does not establish in-game acceptance.
Farmer's Delight Fallback Content
JEI, EMI, and REI provide tree bark production views with axes, logs, bark, and stripped wood, plus a compost maturation view showing rich soil and the water, skylight, and nearby activators that accelerate it. Use the recipe lookup on bark or rich soil, or the usage lookup on a log or organic compost. These views are only registered without Farmer's Delight; when it is installed, its native recipe views apply.
Without Farmer's Delight, TDPlanter provides organic_compost, rich_soil, rich_soil_farmland,
tree_bark, and straw under its own namespace. With Farmer's Delight installed, these fallback
blocks and items are not registered and their recipes are disabled; the existing integration uses
Farmer's Delight content instead. Adding or removing Farmer's Delight in an existing world changes
which registry IDs are available and does not migrate existing fallback items or blocks.
Strip a placed log with an axe to obtain one bark. Alternatively, craft one axe with one log:
the output is one bark, the stripped log returns to the log's input slot, and the axe returns with
one durability consumed (or breaks). Vanilla logs, wood, stems, and hyphae are supported.
Modded crafting inputs use native axe mappings or an existing same-namespace stripped_<log> block;
placed logs use the mod's NeoForge stripping ability. Logs without a stripped counterpart are rejected.
Already stripped wood cannot produce bark again.
Harvest mature wheat with any tool or bare-handed for one straw. Planter wheat harvests also produce one straw, using Farmer's Delight straw when installed and TDPlanter straw otherwise. Short/tall grass harvested with shears has a 50% straw chance. The original shapeless compost recipes are retained: one dirt, two straw, two bone meal, and four bark; or one dirt, two straw, four bone meal, and two rotten flesh. Bark can also be crafted into paper and retains its original fuel and composting values.
Place organic compost and stay nearby while it matures. At the default randomTickSpeed=3 and
20 server ticks per second, the calculated average is about 45 minutes with nearby water and
strong skylight, 91 minutes with strong skylight alone, 61 minutes with water alone, or 3 hours
without either. Nearby blocks in tdplanter:compost_activators shorten these times further.
These are averages, not deadlines: random ticks make individual times vary. Maturation pauses
outside randomly ticking chunks or with randomTickSpeed=0; slower server ticks extend real-time waiting.
Rich soil gives eligible plants above or below it a 20% bone-meal boost chance per random tick and can be hoed
into rich soil farmland. That farmland does not dry into dirt or suffer trampling; its boost requires
full hydration. Both soils retain the existing Farmer's Delight planter bonuses through soil recipes.
Mushroom colonies and other Farmer's Delight-specific plants are outside the fallback content.
The production JAR includes the license in META-INF/LICENSE.txt.