How nowath/text-or-death works
Project type and purpose
• This is a small networked Python game (“Text or death”) with a clear client-server separation.
• The client hosts the UI and game-loop logic; the server holds game rules, persistent state (in database.json), and orchestrates multiplayer or stateful interactions.
File structure
• Top-level folders:
• assets/ ← all art, sprites, font files
• client/ ← entry point for the player’s game client
• server/ ← game server logic
• ui/ ← user-interface components (buttons, screens, character widgets)
• utils/ ← shared utilities (word checking, spritesheet loading)
• Config:
• config.json ← game or network settings
• database.json ← simple file-based persistence
• requirements.txt declares Python dependencies.
README
• Only project title “Text or death” is present; rely on file structure for architectural intent.