v0.0.1 Pre Release 3

What's Changed

Implemented Stories

• Initialize Game Components

  • The Game Loop initializes the Interpreter and View.
  • The Pydispatch bus is set up to mediate events between components.

• Manage Game Flow

  • The Game Loop invokes the Interpreter to perform game steps.
  • The Game Loop checks for Exit_Game events after each step.
  • The Game Loop terminates the game if an Exit_Game event is received.

• Choices Flow

  • The Interpreter sends Put_Choice events with options.
  • The View receives Put_Choice events and presents the options to the player.
  • The View captures user input when a Put_Choice event is active.
  • The View sends a Make_Choice event with the player's choice to the Interpreter.
  • The Interpreter receives the Make_Choice event and processes the choice.

• Exit Flow

  • The View allows the player to trigger an exit command.
  • The Interpreter processes the exit command and dispatches an Exit_Game event.
  • The Game Loop receives the Exit_Game event, performs cleanup, and shuts down the game.

• CLI Entrypoint

  • The CLI Supports manual testing of implemented stories
  • The CLI runs from terminal via IFEngine or python -m engine.main

• Logging Story

  • Debug Log traces entry and decision points for Interpereter, View, and Game
  • Log messages clearly indicate module of origin: [View] User picked choice north"
  • Log is configured via pyproject.toml

Full Changelog: 0.0.1.pre-2...0.0.1.pre-3