Modpack developers

Everything in Plantations is data: tags, data maps, datapack registries and recipe types. A datapack, KubeJS or CraftTweaker can change all of it. The examples on this page are in docs/examples and are tested (see Testing the examples).

Two op commands show how the mod sits in a pack; both print to chat and the log, so they also work from a server console:

• /plantations diagnose: the mod's recipes per type, the compat recipes that loaded for each mod (with their ids), what the input tags resolve to, and which plants are on.
• /plantations scan <chunks>: counts the ores and the Plantations plants in the chunks around the position (it generates missing chunks, so keep the radius small).

#Config

config/plantations-common.toml (all options in CONFIG.md). The ones packs usually touch:

Screen effects are per player in config/plantations-client.toml (visuals.intensity, visuals.photosensitive, visuals.hallucinations).

#Tags

Exported: other mods' recipes find Plantations items through these.

Consumed: recipes take conventional tags wherever one exists, for example:

• c:crops/wheat, c:crops/sugar_cane, c:crops/cocoa_bean, c:crops/potato, c:crops/rice
• c:eggs, c:bones, c:mushrooms, c:foods/fruit, c:foods
• c:buckets/water, c:buckets/milk, c:buckets/empty
• c:dyes/*, c:dusts/glowstone, c:dusts/redstone, c:ingots/*, c:tools/shear
• the mineral tags above

Machines and mechanics read these mod tags. Add your items to them:

#Data maps

All are in data/<namespace>/data_maps/item/<name>.json. Entries merge across packs; set "replace": true to override an entry.

Example, tested through the KubeJS data folder (kubejs/data/plantations/data_maps/item/soil_amendment.json):

{
  "values": {
    "minecraft:rotten_flesh": { "n": 1, "organic": 2, "life": 1 }
  }
}

#Datapack registries

#Recipe types

plantations:quality_shapeless and plantations:microbe_shapeless are shapeless crafting recipes that carry the quality or microbe profile of their inputs into the result. Plant recipes carry the plantations:plant_enabled condition, so they switch off with their plant.

#KubeJS

Every recipe type works through event.custom with the JSON above. The tested example is examples/kubejs/server_scripts/plantations_examples.js. It adds one recipe of every type and removes one; an excerpt:

ServerEvents.recipes(event => {
  event.custom({
    type: 'plantations:fermenting',
    ingredients: [{ item: 'minecraft:carrot' }, { item: 'minecraft:sugar' }, { item: 'minecraft:glass_bottle' }],
    result: { id: 'plantations:fermented_plant_juice', count: 2 },
    time: 12000
  }).id('plantations:kubejs/fermenting_carrot')

  event.remove({ id: 'plantations:campfire/charred_bone' })
})

Data maps and registries go in kubejs/data/<namespace>/… like any datapack.

#Black market

The market is data too (details in BLACK_MARKET.md §11). The tested examples are in examples/kubejs/data:

// data/plantations/data_maps/item/market_value.json: the Dealer buys sweet berries (merges with the mod's own file)
{ "values": { "minecraft:sweet_berries": { "value": 0.5, "tier": "t0", "capacity": 128 } } }

// data/kubejs/plantations/black_market/offer/glowstone_dust.json: the Dealer sells 8 glowstone dust from tier 1
{ "item": "minecraft:glowstone_dust", "count": 8, "value_each": 2.5, "min_tier": 1, "stock": 4 }

// data/kubejs/plantations/black_market/contract_template/berry_rush.json: a contract from tier 2
{ "item": "minecraft:sweet_berries", "count_min": 32, "count_max": 64, "days": 2, "reward_multiplier": 1.3, "min_tier": 2 }

To remove one of the mod's offers or templates, override its file (same id) in a datapack with a NeoForge neoforge:false condition ("neoforge:conditions": [{ "type": "neoforge:false" }]). For quest mods there is the plantations:reputation_tier criterion (and one advancement per tier) and the plantations:contracts_completed statistic; INTEGRATIONS.md has an FTB Quests chapter.

#CraftTweaker

Decision: no native ZenScript handlers. CraftTweaker's addJsonRecipe takes the same JSON for any recipe type, so handlers would only duplicate it. The tested example is examples/crafttweaker/scripts/plantations_examples.zs; an excerpt:

<recipetype:plantations:pressing>.addJsonRecipe("plantations_pressing_sunflower", {
    type: "plantations:pressing",
    ingredient: {item: "minecraft:sunflower"},
    count: 2,
    result: {id: "minecraft:yellow_dye", count: 3},
    presses: 2,
    heated: false
});

<recipetype:minecraft:campfire_cooking>.removeByName("plantations:campfire/roasted_eggshells");

The recipe ids are crafttweaker:<name>. Data maps and registries need a datapack.