xboing 0.3.2

XBoing - A classic breakout-style game modernized with Python and Pygame

XBoing II (Python port)

A Python reimplementation of the classic XBoing game originally written for X11 in C. This modernized port maintains the gameplay and charm of the original while offering improved compatibility with modern systems.

🎮 For Players

What is XBoing?

XBoing is a fast-paced, blockout-style arcade game where you control a paddle to bounce a ball around the play area, destroying blocks and collecting power-ups. Inspired by the classic arcade genre, XBoing features:

• 80+ challenging levels with unique layouts and increasing difficulty
• A variety of colorful block types, including indestructible, counter, bomb, sticky, and death blocks
• Special power-ups and power-downs: multiball, extra ball, paddle expand/shrink, sticky paddle, and more
• Lively sound effects and vibrant graphics
• Classic arcade-style gameplay with modern conveniences
• Addictive, skill-based action that rewards quick reflexes and strategy

Originally developed for X11 in C, XBoing was designed for speed and fun, with a focus on colorful visuals and responsive controls. This Python port faithfully recreates the original experience while adding modern compatibility.

Installation & Playing

1. Install Hatch (if you don't have it)

pip install --user hatch
# or
pipx install hatch
# or
brew install hatch

2. Clone the repository

git clone https://github.com/jmf-pobox/xboing-python.git
cd xboing-python

3. Create and activate the environment

hatch shell

4. Run the game

hatch run game
# or, inside the hatch shell:
python -m xboing

Advanced: Manual pip install (not recommended)

If you prefer not to use Hatch, you can manually install runtime dependencies:

pip install pygame injector
python -m xboing

Game Controls

• Left/Right Arrow Keys: Move paddle
• Space: Launch ball / Pause game
• Esc: Quit game
• F: Toggle fullscreen

Special Blocks & Power-ups

• Multiball: Splits your ball into multiple balls
• Extra Ball: Gives you an additional ball
• Paddle Expander: Makes your paddle larger
• Paddle Shrinker: Makes your paddle smaller
• Counter Blocks: Require multiple hits to destroy
• Death Blocks: End your current life when hit
• Black Blocks: Indestructible, bounce balls away
• Bomb Blocks: Explode and destroy neighboring blocks
• Sticky Blocks: Make balls stick to paddle

Project Status

This Python port is under active development and is already playable. Current features include:

• ✅ Full conversion of all original XBoing assets (graphics, sounds, levels)
• ✅ Level loading system that reads and displays original level files
• ✅ Block implementation with correct behaviors and effects
• ✅ Ball physics and collision detection
• ✅ Paddle movement and control (keyboard and mouse)
• ✅ Audio system for event-driven sound effects
• ✅ Event-driven, component-based UI (score, lives, ammo, level, timer, messages)
• ✅ Paddle gun/ammo feature: ammo state, UI, collection, and sound (Phase 1 complete)
• 🚧 Special power-ups and effects (in progress)
• 🚧 Game state management and transitions (polished, but ongoing)
• 🚧 Score tracking and high scores (basic, more to come)
• 🚧 Machine gun mode and bullet logic (planned)

The game is fully playable, with most core features implemented and tested. Remaining work focuses on advanced power-ups, polish, and additional features to match and extend the original XBoing experience.

💻 For Developers

Project Structure

xboing-python/
├── assets/               # Game assets (images, sounds, levels)
│   ├── images/           # All game images (balls, blocks, backgrounds, etc.)
│   ├── sounds/           # Sound effects (WAV, AU)
│   └── levels/           # Level data files
├── docs/                 # Documentation and design docs
├── scripts/              # Utility scripts for asset conversion, etc.
├── src/                  # Source code
│   ├── app_coordinator.py# App entry coordination
│   ├── controllers/      # Controllers for game, window, UI, etc.
│   ├── di_module.py      # Dependency injection setup
│   ├── engine/           # Game engine (graphics, audio, input, window)
│   ├── game/             # Game logic (ball, blocks, paddle, collision, state)
│   ├── layout/           # Layout helpers and game layout logic
│   ├── main.py           # Main entry point
│   ├── renderers/        # Rendering helpers (digits, lives, etc.)
│   ├── ui/               # User interface components (views, displays)
│   └── utils/            # Utility functions and helpers
├── tests/                # Test scripts
│   ├── integration/      # Integration tests
│   └── unit/             # Unit tests
└── xboing2.4-clang/      # Original XBoing C source/assets (reference)

Asset Management

The game uses assets from the original XBoing converted to modern formats:

• Original XPM graphics → PNG format
• Original AU sound files → WAV format

Use scripts/sync_assets.py to synchronize assets from the original XBoing directory.

Asset Migration Tools

# Run tests
hatch run test

# Convert XPM to PNG (for new assets)
python scripts/convert_xpm_to_png.py path/to/image.xpm output.png

# Convert AU to WAV (for new sounds)
python scripts/convert_au_to_wav.py path/to/sound.au output.wav

# Normalize all audio files in the assets directory
python scripts/normalize_audio.py

# Fix background images (formatting, transparency, etc.)
python scripts/fix_background.py

# Fix ball lost sound or related assets
python scripts/fix_balllost.py

# Search dependencies in the codebase
python scripts/dep_grep.py <search_term>

Design Documentation

See the docs/ directory for detailed information:

• Audio Design – Audio system, event-driven sound playback, and sound asset management
• Block Design – How blocks work, their types, and behaviors
• Dependency Injection Design – Dependency injection and modularity
• GUI Design – Window layout, UI regions, and event-driven UI architecture
• Hatch Usage – Using Hatch for environment and dependency management
• Highscore Design – High score system design
• Levels Design – Level format, loading system, and level structure
• Logging Design – Logging system and best practices
• Project Paths – Directory structure and asset locations
• Scripts Design – Utility and asset conversion scripts

Contributing

Contributions are welcome! Areas that need work:

1. Complete implementation of all special block effects
2. High score system
3. Game state management and transitions
4. Enhanced visual effects
5. Additional sound effects
6. Level editor

Testing & Quality

• All major UI components (score, lives, level, timer, message window) are event-driven, component-based, and have dedicated unit tests.
• The test suite includes both unit and integration tests, covering game logic, event-driven UI updates, and core systems.
• Tests are run before and after each major change to ensure stability and catch regressions early.
• Type hints and docstrings are used throughout for clarity and static analysis.
• Logging is used for warnings and errors (no print statements in production code).
• The codebase is designed for maintainability, extensibility, and testability, following modern Python best practices.

License

This project is licensed under the same terms as the original XBoing - see the LICENSE file for details.

Original Source

The original source code is available at: https://www.techrescue.org/xboing/xboing2.4.tar.gz

Commit Message Standard

This project uses the Conventional Commits standard for all commit messages. This helps automate changelogs, semantic versioning, and improves code review clarity.

Format:

<type>(<scope>): <short summary>

• type: feat, fix, chore, refactor, test, docs, etc.
• scope: the area of the codebase affected (e.g., gun, ammo, ui)
• summary: a brief description of the change

Example:

feat(gun): implement ammo collection event, state, and UI update

See the Conventional Commits documentation for more details.