Use a dependency check
If a dish is unavailable, inspect each dependency separately. A missing unlock and a missing ingredient are different problems. Record the message or disabled control the game shows rather than assuming a cooking bug.
- Is the recipe available at this venue?
- Are the required quantities in the correct inventory?
- Is the named equipment installed and usable?
Record a repeatable preparation
For a useful cooking observation, note the selected recipe, inputs before preparation and the resulting output. If the system supports customization, change one option at a time and record whether the recipe, price or stock use changes. Do not infer a statistical bonus from the name of an option.
- Recipe available?
- Ingredients in stock?
- Right equipment?
- Observe service
Recipe, ingredient and equipment dependencies are official; the checking sequence is ours.
Bring the result back to the menu
Once a serving can be prepared, compare its cost and selling price in the menu planner. Keep unmeasured preparation time as a note, not a hidden penalty in a formula. This makes the difference between known cash contribution and a broader personal assessment of effort visible.
What we’ll check at launch
- Cooking controls and preparation sequence
- Batch versus per-serving quantities
- Customization effects
Compare dishes, serving contribution and a revenue-weighted menu margin.
Follow the evidence
Checked Fri, 11 Sep 2026 04:27:05 GMT · No released build verified. Official previews can change before launch.
- What's on the menu in Nivalis Nights? 2026-08-14
- COMMUNITY Q&A 2026-03-31
