Learn a recipe from found pages and turn extra pages into scrap

An enemy drops a torn page of a plan. Three pages teach the recipe, but the player finds a fourth after learning it, or learns the same recipe another way first. Without rules the pages pile up uselessly or teach it twice. This entry handles each case and pays out scrap.

Why this works

Collecting becomes a goal when progress is visible and every find counts. Pages build toward something, and once the goal is met, extras turn into a smaller reward instead of nothing. Paying back pages when a recipe is learned another way respects effort already spent.

When not to use it

Skip page hunting when recipes should simply be given by the story or a teacher. A scavenger chore on top of a tutorial feels like padding. Also avoid it where drops are scarce and players may never see the third page.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 23 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 "Learn a recipe from found pages and turn extra pages into scrap" (read_entry blueprint-pages-and-duplicate-scrap) 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