How femitun/pict-o-word works
Project type and purpose
• This is a stand-alone Python “pict-o-word” puzzle game (Dreamscapes competition entry).
• Users navigate menus (home, loading), play rounds of picture-based word puzzles across three difficulty levels, spend or earn coins, and trigger sounds/music.
File structure
Top-level components:
• Entry & navigation scripts: main1.py, home_page.py, loading_page.py
• In-game UI & logic: Ingame_ui.py, game_ui.py, coin_manager.py
• Puzzle definitions:
• Flat files games/Easy#.py, Medium#.py, Hard#.py (individual puzzle rounds)
• Organized subpackages games/easy/, games/medium/, games/hard/ (categories of puzzles)
• Assets: audio files (.wav, .mp3), Nerko_One font directory
• Misc: .gitignore, IDE settings, README
README
• Very brief; confirms project name (“pict-o-word”) and competition context.
Core components to model
a. Frontend/UI Layer
• main1.py (app entry)
• home_page.py (main menu)
• loading_page.py (pre-round loader)
• Ingame_ui.py & game_ui.py (render puzzles, accept input)
b. Game Logic Layer
• coin_manager.py (track coins, enforce spends/earnings)
• Puzzle modules (games/Easy#.py, Medium#.py, Hard#.py) + category packages
c. Asset Manager
• Audio subsystem for sound effects and background music
• Font loader (Nerko_One)
d. Data Store (if any persistent state)
• In-memory objects or simple file I/O (no database shown)
e. External Resources
• OS file system for assets
• Potential future API or high-score server (none present now)
Relationships & interactions
• Startup: main1.py → home_page.py
• User selects difficulty → loading_page.py → Ingame_ui.py
• Ingame_ui.py invokes game_ui.py to render puzzle
• game_ui.py pulls puzzle data from the appropriate games/Easy#.py (or Medium#/Hard#) module
• game_ui.py calls coin_manager.py to check/update coin balance
• UI triggers audio subsystem (play hint sound, win/lose sounds, background mp3)
• On round end: game_ui.py → home_page.py (or repeat cycle)
Architectural patterns & principles
• Layered separation: UI layer (presentation) vs. logic layer (game rules, coin management) vs. asset management
• Modular puzzle definitions (each round is a self-contained Python module)
• Package grouping by difficulty/category