Show a recipe card with undiscovered parts hidden, and reveal a little more on request
A recipe book that shows everything has nothing left to discover, and one that shows nothing is just frustrating. The middle way is a card where known parts are named and unknown ones are question marks, with a hint button that gives a little more each time. The catch is that the question marks must not give the answer away by themselves.
Why this works
Discovery is the fun, so a card should tease without spoiling. Giving away a little at a time lets the player decide how much of the surprise they will trade for help. Marking unknown parts by position, not by name, keeps each hint from leaking more than it says.
When not to use it
Do not hide recipes in a game about planning ahead, where the player needs the full list to shop and prepare. Hiding it there is only friction. Show it in full and keep the mystery for the dishes' results instead.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 4 common mistakes and the fix
- 21 lines of example code with 5 checks that pass
- How your AI shows you that it works
Say this to your AI
Use the Spielerando entry "Show a recipe card with undiscovered parts hidden, and reveal a little more on request" (read_entry casual-recipe-card-hidden-parts) 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