How mittymatty/root_cafe works
This is a Godot cafe-making game. With no README or source excerpts, the graph uses exact paths from the tree to show the apparent player workflow and major gameplay/UI subsystems; connections are dashed and unverified rather than presenting inferred calls as inspected facts.
Main entry points: game.tscn Game scene · counter.gd Counter · base_dispenser.gd Ingredient dispensers · cup.gd Drink cup
Components 17
Cafe gameplay
- Game scene
scenes/game.tscn - Kitchen
scripts/kitchen.gd - Counter
scripts/counter.gd - Ingredient dispensers
scripts/base_dispenser.gd - Ingredients
scripts/base_ingredient.gd - Drink cup
scripts/cup.gd
Drink recipes
- Recipe data
scripts/resources/recipe_resource.gd - Recipe book
scripts/recipe_book.gd - Recipe collection
resources/recipes
Menus and feedback
- Main menu
scripts/main_menu.gd - Game UI
scripts/game_ui.gd - Pause menu
scenes/pause_menu/pause_menu.gd - End screen
scripts/end_screen.gd
Shared game state
- Cup contents
scripts/globals/CupContents.gd - Player status
scripts/globals/PlayerStatus.gd - Signal hub
scripts/globals/SignalHub.gd
Other components
- Player
Connections 16
- Player → Main menu: starts at
- Main menu → Game scene: starts game
- Game scene → Kitchen: loads
- Player → Ingredient dispensers: uses
- Ingredient dispensers → Ingredients: dispenses
- Player → Counter: prepares drink
- Counter → Drink cup: uses
- Drink cup → Cup contents: tracks
- Recipe book → Recipe collection: shows
- Recipe collection → Recipe data: defines
- Player → Recipe book: consults
- Game scene → Game UI: shows
- Player → Pause menu: opens
- Game scene → End screen: ends at
- Game scene → Player status: tracks
- Game scene → Signal hub: uses