Change one variable at a time
The official loop is explicit: experiment with ingredients to discover recipes. A clean test therefore starts with one combination and one expected observation. Avoid changing the ingredients, preparation, and serving setup in the same run; you will not know which change affected the result.
This is a player method, not a hidden game formula. It helps you learn your own restaurant state while the public source set remains too small for a complete database.
Keep a notebook that answers three questions
Every entry should answer: what went in, what came out, and how confident are you? Open the Recipe Discovery Tracker, use consistent ingredient names, choose Confirmed only when you saw the result clearly, and add a brief note when a repeat is still needed.
Do not add invented values such as rarity, sale price, yield, or universal success rate. Those fields are not part of the verified public description and would make the notebook look more precise than the evidence supports.
Repeat before sharing
When a combination produces a dish, repeat it before calling it reliable. Share the observation with friends using its exact wording and test context. “This produced this dish in our restaurant” is a useful handoff; “this is the best recipe” needs a comparison set and a source.
Once reliable public data exists, personal records can be compared against it without losing the original observation that made the discovery useful.
How should I test recipes in Automate a Restaurant?
Start from ingredients you personally observed, change one combination at a time, and record the dish result. The game confirms recipe discovery through experimentation, but the official listing does not publish a complete recipe table.
Is there an official best recipe?
No verified best recipe is available. Without named entries, comparable output data, and a source, a best-recipe ranking would be speculation.
What should a recipe experiment record include?
Record the exact ingredients, dish result, confidence status, and one short note about the test context. The local tracker is designed for those fields.