Manage shared stew pots

Stew pots share finite portions between players in the same virtual world. Stocked pots start with four portions, empty pots start empty, and neither refills automatically. Server scripts use CookPot to manage the supply.

const pot = CookPot.all()[0];
if (pot) {
  CookPot.refill(pot.guid, 8); // replace the supply with eight portions
  console.log(CookPot.get(pot.guid)?.portions);
}

Find a pot

CookPot.all(virtualWorld = 0) returns snapshots of catalogued pots on the server’s level. CookPot.get(guid, virtualWorld = 0) returns one or null. Use the snapshot’s GUID, which names the fireplace, rather than an ID from the eating trigger or visible cauldron.

Snapshot field	Meaning
guid, position	Stable fireplace identity and the eating position.
portions, capacity	Remaining meals and the size of the current refill.
state	empty, half or full.
enabled	Whether the server allows eating.
food, nutrition	Meal type and its base nourishment value.
poison	Added ingested buff GUID or null, visible to server scripts.
virtualWorld	The world whose supply was read.

Snapshots are frozen values, not live handles. Read again after changing stock; assigning to a snapshot does not refill a pot.

Set the supply

Call	Effect
CookPot.refill(guid, portions = 4, world = 0)	Replaces stock and capacity and clears poison. Integer portions from 0 to 1000.
CookPot.setState(guid, state, world = 0)	empty, half or full means zero, two or four portions, with capacity four.
CookPot.setEnabled(guid, enabled, world = 0)	Allows or blocks eating without changing stock or appearance.
CookPot.setFood(guid, food, world = 0)	Changes the meal and its appearance while preserving stock, poison and enabled state.

Setters return false for an unknown pot and throw for invalid arguments. Refilling or changing state preserves enabled. A pot looks half full when at most half of its refill remains, and empty with none.

const pot = CookPot.all()[0];
if (pot) {
  CookPot.setEnabled(pot.guid, false);
  CookPot.refill(pot.guid, 12);
  CookPot.setEnabled(pot.guid, true);
}

refill replaces the count; it does not add to it. Decide in your game mode whether cooks, purchases or a timer should replenish meals.

Choose meals and refill from inventory

Pots serve lentil (porridge, 10 base nutrition), soup (vegetable stew, 15), and goulash (meat stew, 25). The meal’s native effects apply when eaten, subject to consumption decisions.

To refill a pot using the player’s ingredients, define the recipe in your server script:

const pot = CookPot.all(player.virtualWorld === 0xFFFFFFFF ? 0 : player.virtualWorld)[0];
if (pot) {
  const result = CookPot.refillFromInventory(player, pot.guid, {
    food: "soup",
    portions: 4,
    ingredients: [
      { item: "cabbageCooked", amount: 4 },
      { item: "carrotCooked", amount: 4 },
    ],
  });
  if (!result.ok) console.log(`Refill refused: ${result.code}`);
}

The call checks the player’s world, distance, ability to act and inventory readiness. It requires an empty enabled pot, skips spoiled ingredients and combines matching stacks. It removes all required ingredients or none of them. A recipe can make 1 to 1000 portions and list 1 to 16 ingredients, each with a positive amount. Keep ingredient costs and portion counts in the server script; do not accept them from the client. refill spends no ingredients.

Add poison and try the sample commands

CookPot.poisons() lists accepted poison classes. CookPot.poison(player, guid, rowId) consumes one dose from that inventory row and returns { ok, code }. It requires a nearby stocked, enabled pot without existing poison. A refused action changes nothing.

Added poison affects subsequent approved meals until a fresh refill clears it. setState preserves poison; changing the visible fullness is not a fresh batch. This does not poison NPCs or trigger the game’s witness and crime reactions.

The default game mode provides these chat commands:

Command	Result
/pot	Describe the nearest pot within four metres, without revealing poison.
/pot recipes	List the sample’s ingredient costs.
/pot refill porridge, /pot refill vegetable, /pot refill meat	Spend ingredients and fill an empty pot with four portions.
/pot poisons	List poison rows in your inventory.
/pot poison <row>	Spend a dose to poison the nearby pot.

The porridge recipe uses four bread rolls. Vegetable stew uses four cooked cabbages and four cooked carrots; meat stew uses four cooked beef items. Edit src/server/cook-pots.ts in the game mode to choose your own recipes.

Keep worlds separate

World 0 has stock from server startup. Another world gets its own supply when a player first enters it or a setter first names one of its pots. Before that, reading that world’s pots returns an empty list or null.

const known = CookPot.all(0)[0];
if (known) CookPot.refill(known.guid, 6, 12); // supply for virtual world 12

Players with global visibility use world 0’s stock. A player moved to a numbered virtual world uses that world’s supply. Global visibility does not grant permission to eat from every world’s pots.

Save and restore

Stock survives disconnects and resource restarts, but ends when the server stops. Save the fields your game mode needs in its database. At startup, restore remaining portions with refill and eating permission with setEnabled. There is no independent capacity setter: refilling with the saved remainder also makes that remainder the new capacity. Restore the meal with setFood. There is no administrative setter for poison, so saving a snapshot is not enough to restore a poisoned batch. Your game mode must decide how to handle those batches after a restart.

The server reserves a portion before the native meal applies. A native refusal can refund it; a disconnect or missing receipt can spend the reservation. Do not treat disconnecting as a way to cancel a meal.

Ordinary cooking at a fire and wine barrels keep their existing behavior. The native hold-to-poison prompt stays hidden; the sample uses /pot poison. The catalog covers base-level pots; unregistered stew triggers, including dynamically created pots, refuse eating. Placing a decorative cauldron in World Builder does not register a new CookPot.