Data-Driven Tea System

(RecipeData, TeaBase, IngredientBase)

The core tea logic is fully data-driven. All teas are defined through RecipeData, a serializable structure that specifies tea name, base type, ingredient list, ideal temperature window, taste tags, effect tag, and a short description. It also exposes helper methods for grouping and filtering by initial, tea type, taste, effect, and ingredient “short names,” enabling rich queries without hardcoding UI logic. 

Interactive UI elements are thin wrappers around this data model. TeaBase represents selectable tea bases; IngredientBase represents optional underworld ingredients. Each prefab configures its own enum type and sprite, then routes click events into TeaSessionManager via a single AddTea / AddIngredient call. This separation cleanly decouples presentation from game logic and makes it trivial to add or rebalance teas and ingredients by editing inspector data instead of code.

Tea Session Manager

(TeaSessionManager)

TeaSessionManager is the central controller for a full brewing session: it tracks the selected tea base and ingredients, controls the boiling process, validates the final brew against a target recipe, and drives end-of-level flow. Each level specifies its required recipe via LevelManager (levelTargetRecipeName); on start, the session loads that recipe, initializes UI state, and wires core buttons (serve, trash, menu, next level) at runtime. 

The boiling mechanic is implemented with a coroutine that increments water temperature over time and syncs it to a slider, reinforcing a sense of timing and control instead of an instant “set value” action. Serving a tea performs three checks—correct base, correct ingredient set (order-agnostic), and temperature within tolerance—then provides immediate textual feedback and, on success, unlocks the end-level canvas and progression buttons.

Dynamic Tea Menu UI

(TeaMenuUIManager)

The recipe reference menu is fully dynamic. TeaMenuUIManager pulls from the same allRecipes list used by gameplay and auto-generates category buttons and recipe lists at runtime. Players can browse teas by Name, Type, Taste, or Effect; each filter uses a helper function on RecipeData to build the appropriate subsets without manual wiring. 

When a category is chosen, the system instantiates buttons for matching options, then builds a scrollable recipe list. Selecting a recipe opens a detail panel with title and description plus previous/next navigation. This helps with possible future development when more data (teas, ingredients) need to be added.

Level Flow

LevelManager defines, per scene, which recipe is the “correct” one and which scene comes next, letting designers script a narrative/learning progression without editing core logic. TeaSessionManager and the end-level UI read directly from it to load menus or advance levels. MenuScript provides simple, clean scene navigation hooks for UI buttons. Together, they form a small but clear level pipeline suitable for extending into a multi-chapter experience. 

Audio & Feedback

SoundManager centralizes BGM and SFX as a persistent singleton. It maintains a dictionary of named sound effects (boiling, success, fail, trash, selection, menu click) and exposes focused helpers like PlayOrResumeBoilSound, PauseBoilSound, and ResetBoilSound. TeaSessionManager calls these during boiling and serving, aligning audiovisual feedback with the player’s actions.