tamari-moto/tollroad

Purpose and Runtime

TollRoad is a Godot 4.7.1+ economic-simulation game prototype. Godot loads project settings from project.godot and starts the main gameplay scene at scenes/main/Main.tscn. It is a local client game; the repository indicates no backend, network service, or third-party API integration.

Application Composition

The main scene and its controller assemble gameplay UI and route player actions into game systems:

• scenes/main/Main.tscn

• scenes/main/main.gd

The scene-oriented design separates reusable UI layouts under scenes/ui/ from their behavior scripts under scripts/ui/.

Global State and Session Lifecycle

GameState is the autoload-level global coordination boundary, likely exposing shared state to scene/UI code. Session orchestration owns the active run, progression, and scenario setup; saving is isolated from gameplay logic:

• scripts/autoload/game_state.gd

• scripts/systems/game_session.gd

• scripts/systems/save_manager.gd

Flow: startup initializes global/session state, selects or starts a scenario, then UI commands mutate the session through systems rather than owning core simulation state.

Economic Domain Model

Game data and pricing are distinct system layers. Static/domain definitions are centralized in game_data.gd; price evaluation is isolated in price_table.gd, enabling market UI and scenario logic to consume common pricing results:

• scripts/systems/game_data.gd

• scripts/systems/price_table.gd

• data/

This boundary is the core economic flow: game/session state plus scenario conditions feed pricing, which drives buying, selling, cargo, and outcome evaluation.

Scenario Engine

A base scenario abstraction supports a catalog of mission/month-specific scenarios, with an aggregate selector/runner:

• scripts/systems/scenario_base.gd

• scripts/systems/scenario_all.gd

• scripts/systems/scenario_m1.gd

• scripts/systems/scenario_m19.gd

Scenarios define the controlled variation layer over shared simulation systems: briefing/objectives, starting conditions, progression constraints, and success/failure results.

Player-Facing Interaction Surfaces

Panel scenes represent the primary transaction and planning workflows: inspect cargo, choose islands/routes, view markets, operate workshops, and read objectives. Their scripts are the presentation adapter layer over session/economy APIs:

• scenes/ui/CargoPanel.tscn, scripts/ui/cargo_panel.gd

• scenes/ui/MarketPanel.tscn, scripts/ui/market_panel.gd

• scenes/ui/WorkshopPanel.tscn, scripts/ui/workshop_panel.gd

• scenes/ui/IslandPanel.tscn, scripts/ui/island_panel.gd

• scenes/ui/MemoPanel.tscn, scripts/ui/memo_panel.gd

Map, Feedback, and Results

Map controls/rendering are separate from market/session logic, while dialogs frame scenario start and completion. Shared visual/audio feedback utilities support UI without becoming domain dependencies:

• scenes/ui/MapPanel.tscn, scripts/ui/map_panel.gd, scripts/ui/map_view_3d.gd

• scenes/ui/BriefingDialog.tscn, scripts/ui/briefing_dialog.gd

• scenes/ui/ResultDialog.tscn, scripts/ui/result_dialog.gd

• scripts/ui/fx_layer.gd, scripts/ui/sfx.gd

Visual content is packaged as Godot-imported assets, notably city, island, item, and mount sprites under assets/sprites/.