Ingredients
Ingredient Flavor Hints
Known flavor-hint categories and how to reason about vague drink orders.
Official release date and demo availability: Planned release date: September 15, 2026. Steam currently lists a playable demo.
Confirmed developer, publisher, and platform facts: Developer: Rogue Duck Interactive. Publishers: Rogue Duck Interactive and Gamersky Games. Platforms: Windows, macOS, and Linux.
Public gameplay systems and current evidence boundary: Steam confirms custom drink mixing, ingredients, ice, glassware, decorations, garnishes, secret recipes, no-timer mode, and Happy Hour mode; full recipe formulas stay unconfirmed until release-build evidence is available.
Quick Answer
Steam examples show customers can ask with vague flavor hints such as sweet and a little bitter. Build drinks around the stated flavor target before optimizing presentation.
Confirmed Hint Types
The public Steam page mentions flavor language including sweet and bitter. Other attributes need release-build confirmation before they become table rows.
How To Use Hints
- Identify the dominant requested flavor.
- Add a secondary flavor only if the request asks for one.
- Avoid overfitting unknown secret recipes before the game confirms them.
- Save your results so the guide can separate reliable patterns from guesses.
Update Target
After release, this guide will grow into a row-level ingredient table with source, preparation method, and known matching requests.
Practical Next Action
Open the related page from the navigation, keep your own demo notes separate from full-release notes, and return after launch for row-level updates.
What This Page Will Add After Release
Once the release build can be checked, this guide will add exact values only where the source is clear: screenshots, direct gameplay observation, official update notes, or repeatable in-game results.
Player Checklist
- Confirm whether you are using the demo or full release.
- Record the wording you saw in game before acting on a recipe or shop assumption.
- Keep uncertain findings out of your main recipe log until they repeat.
- Prefer confirmed system behavior over copied forum guesses.
Flavor Decision Examples
| Customer wording | First thing to test | What to record |
|---|---|---|
| Sweet | Sweet or fruit-like ingredients | Ingredient, amount, accepted result |
| Bitter | Bitter bases or mixers | Whether the customer accepts the taste profile |
| Spicy | Spicy ingredients or garnish | Whether spice is ingredient-only or presentation-linked |
| Relaxing | Milder ingredients and calm presentation | Whether mood words map to taste, look, or both |
| Fancy | Glassware, decoration, and garnish | Whether presentation changes acceptance or reward |
Hint Tracking Steps
Create one note for customer language and another for ingredient behavior. If a customer asks for something sweet, bitter, spicy, relaxing, cold, fancy, or refreshing, write that exact phrase down. Then record which ingredients seemed to satisfy it. Keep presentation details separate until the game proves that glassware, ice, decoration, or garnish affects the request.
Failure Modes
Do not collapse similar words too early. A cozy bartending game may treat mood words, taste words, and visual presentation as different systems. Do not assume every ingredient has a single fixed tag before release-build testing. If a hint comes from the demo, keep it marked as demo evidence.
FAQ
Does Steam confirm flavor-hint play? Steam describes hint-based orders and custom drinks, which supports this page topic.
Can this page list exact ingredient stats yet? Not responsibly. The public sources do not expose final row-level ingredient values.
What changes after launch? This page will add tested hint words, matching ingredients, contradictions, and screenshots where useful.
Verification Notes
This page separates three kinds of information: confirmed public facts, demo observations, and release-build findings that still need checking. Confirmed public facts can be used immediately when planning whether to wishlist, download the demo, or prepare a notes template. Demo observations are useful for practice, but they should be retested because balance, unlocks, and recipe requirements can change. Release-build findings need a reproducible path before they become guide data.
When checking this topic yourself, keep a short note with the date, the build or store state, and the exact wording you saw. For recipe-adjacent information, include the customer request, ingredients selected, glass or garnish choices, and the accepted result. For shop-adjacent information, include the item name, cost, unlock timing, and effect. For mode or timing information, include the trigger condition, timer behavior, reward, and what happens on failure.
Update Policy
After the planned 15 September 2026 release, this page should be updated only from direct gameplay, official patch notes, Steam news, or clearly reproducible community reports. If two sources disagree, the page should preserve the conflict instead of silently choosing the more convenient answer. Rows that cannot be reproduced should stay in a testing section until another source confirms them.
Practical Use
For now, use the page as a launch notebook. It tells you what is known, what to test first, and what not to trust yet. That makes it useful before the full data exists: you can enter launch day with categories ready, then fill in exact values without mixing guesses into confirmed advice.
If You Need A Fast Choice
If the request names a flavor, test ingredients before presentation. If the request sounds like a mood, test mild ingredients and then adjust glassware or garnish. If the request sounds visual, such as fancy or decorated, test presentation after you have a drink base that works. This keeps each experiment narrow enough to learn from.
Links To Use Next
Use the beginner guide before testing hints in a live shift. Use the recipe discovery guide when a hint produces a repeatable named drink. Use the shop guide when a missing ingredient or garnish blocks the next test.
Search Phrases This Page Answers
Use this page for searches like “sweet order,” “bitter drink,” “spicy hint,” “relaxing customer request,” and “which ingredient matches a vague order.” The answer is not a final ingredient table yet; it is a testing method for turning customer language into verified rows.