How barnslab/bridge works
This repository is a modular Godot bridge-game engine. Its principal workflow is mediated by GameManager: it coordinates dealing and player input, keeps private hands outside the referee state, and passes hands to rule validation; GameCore owns public match state and delegates rule checks. The graph also preserves the documented driver and presentation boundaries. Relationships are based on README.md because no source excerpts were supplied; deck variants and network cryptography are described capabilities, but their implementations are not present in the tree.
Main entry points: game_manager.gd Game manager · player_driver.gd Player driver · base_ruleset.gd Base ruleset · game_core.gd Game core
Components 13
Match orchestration
- Game manager
core/game_manager.gd - Deck management
deck/base_deck_manager.gd
Rules and state
- Game core
core/game_core.gd - Base ruleset
core/rules/base_ruleset.gd - Standard bridge rules
core/rules/standard_bridge_ruleset.gd
Shared game data
- Action payloads
core/data/action_params.gd - Event payloads
core/data/game_event_params.gd - Bridge vocabulary
core/data/bridge_enums.gd - Card values
core/data/card_resource.gd - Game data types
core/data/game_data_types.gd
Player and presentation
- Player driver
drivers/player_driver.gd - UI manager
io/ui/base_ui_manager.gd - Renderer
io/renderers/base_renderer.gd
Connections 9
- Game manager → Game core: owns and configures
README.md - Game manager → Deck management: requests deal
README.md - Game manager → Player driver: assigns hands, prompts
README.md - Game core → Base ruleset: delegates rule checks
README.md - Game manager → Base ruleset: passes hand for validation
README.md - Standard bridge rules → Base ruleset: implements strategy
README.md - Player driver → Game manager: submits actions
README.md - UI manager → Player driver: emits user input
README.md - Game manager → Player driver: routes events
README.md