kishanpujari/wallom

Purpose and Runtime

Wallom is a Windows terminal grid-survival game implemented in PowerShell 5.1+. It runs a turn-based loop: the player moves, places mines or permanent wall bombs, collects points, and attempts to eliminate an AI enemy. ANSI terminal output provides the UI; JSON files persist game and settings state.

Launch and Composition

Wallom.bat is the Windows entry point and launches the PowerShell game. The engine is modularized as dot-sourced PowerShell scripts under bin/, with the central coordinator in bin/engine.ps1.

Key entry paths:

• Wallom.bat

• bin/engine.ps1

• bin/splash.ps1

Engine and Game Lifecycle

bin/engine.ps1 owns high-level control flow: initialize/load a game, accept command input, advance game state, redraw the terminal, and exit or save. It composes domain modules rather than exposing a separate service or networked API.

Lifecycle boundaries:

1. Start/menu and settings selection.

2. Create or restore state.

3. Repeated player-command and enemy-update turns.

4. Persist state and return/quit.

Related UI modules:

• bin/splash.ps1

• bin/ui_settings.ps1

• bin/ui_help.ps1

Grid World and Rendering

bin/grid.ps1 defines the playable map behavior: procedural grid setup, placement and representation of walls, player, enemy, bombs, and collectibles, plus movement/blocking constraints. It is the primary shared spatial model used by player actions, enemy movement, and bomb effects.

Terminal presentation is separated into reusable color and menu/logo views:

• bin/grid.ps1

• bin/colors.ps1

• bin/ui_logo.ps1

Enemy and Combat Systems

bin/enemy.ps1 implements AI-driven enemy movement against the current grid state. The enemy’s turn depends on obstacle and mine placement, and it can be killed by stepping on a mine.

bin/bomb.ps1 manages player-deployed hazards: X1 mines with configurable lifetime/radius behavior and X2 wall bombs that create durable map obstacles. This module changes grid state and supplies the combat outcome that can end a session.

Core paths:

• bin/enemy.ps1

• bin/bomb.ps1

• bin/grid.ps1

Persistence and Settings

bin/db.ps1 is the persistence boundary for JSON game saves, including session/game ID, player and enemy positions, score, walls, bombs, and collectibles. It isolates saved-state serialization from turn logic.

bin/config.ps1 separately manages persistent gameplay configuration, notably maximum mine count and mine lifetime; settings UI updates this configuration rather than requiring source edits.

Core paths:

• bin/db.ps1

• bin/config.ps1

• bin/ui_settings.ps1

Infrastructure and External Dependencies

The repository has no web server, database service, package runtime, or external API dependency. Required infrastructure is a Windows console with PowerShell and ANSI-capable terminal rendering. Batch is used only as the launcher; JSON files are the sole durable storage mechanism.