Cloning

Requires the player to take cuttings (clones) from the specified plants. Counts the number of clones produced.

{
  "type": "Cloning",
  "title": "Take hemp cuttings",
  "description": "",
  "amountRequired": 20,
  "conditions": {},
  "items": ["clone.hemp"]
}

Fields

Field	Type	Description
type	string	Exactly 'Cloning'.
title	string	Short, human-readable name. Must not be empty.
description	string	A blurb of 1 to 3 sentences. May be empty if the title is self-explanatory.
amountRequired	integer (≥ 1)	How many units must be completed. What a unit means depends on the objective type. Minimum 1.
conditions	map	Optional conditions that restrict when progress counts. Progress is recorded only when the objective's main requirement and all of these conditions are met. Use an empty map for none.
items	string[]	Clone item shortNames to create (e.g. clone.corn, clone.hemp). Empty = any clone.

Notes

• Progress increments by the number of clones a cutting produces. That count scales with the plant’s genetics: better Yield genes yield more clones per cutting, so a single cutting can advance the objective by more than one.
• See also Harvest for taking the yield and Plant for planting seeds.

Caution

Oxide only has a hook that fires BEFORE a cutting happens (CanTakeCutting). The plugin can therefore only track cuttings before they actually occur, not after. This means that if another plugin hooks on the same CanTakeCutting event and cancels the cutting after the plugin tracks it, the player would still get progress for that cutting even though it didn’t actually happen. They could then potentially spam cuttings to complete the objective.

Due to the unlikely-ness of this scenario by most popular plugins, I’ve decided to accept this edge case rather than add complexity to a simple objective type. Even the only plugin I know to do this (DrugDeals) actually removes the plant after the cutting is cancelled anyway, so this can’t be exploited.