Show how many of each recipe you can make when they share materials

Three recipes all need wood. Each one says you can make several, but together you cannot. Players queue them and the last ones fail or the numbers on screen turn out wrong. This entry counts each recipe alone and then the whole queue in order.

Why this works

Each recipe's count answers a separate question, and the stock is only enough once. A queue has to spend as it goes, in the order the player chose, or the numbers on screen add up to more than the player owns.

When not to use it

Do not reserve materials for queued jobs when players change plans often or the queue is long. Locked stock then feels stolen. Let the queue run on what is there at the start of each job, and show a warning.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 24 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Show how many of each recipe you can make when they share materials" (read_entry craft-queue-shares-ingredients) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP