footsies-gym 0.1.3

A reinforcement learning environment for HiFight's Footsies game

FootsiesGym

Implementation of HiFight's Footsies game as a reinforcement learning environment. This environment serves as a benchmark for multi-agent reinforcement learning in a (relatively) complex two-player zero-sum game.

The environment is derived from the open-source Unity implementation, which has been augmented to run a gRPC server that can be controlled through a Python harness. Training is implemented using Ray's RLlib.

System Architecture

sequenceDiagram
    participant RLlib as Ray RLlib
    participant Env as FootsiesEnv
    participant gRPC as gRPC Client
    participant Server as Unity Game Server
    participant Game as Footsies Game

    Note over RLlib,Env: Python Environment
    Note over gRPC: Communication Layer
    Note over Server,Game: Unity Game

    RLlib->>Env: step(action)
    Env->>gRPC: SendAction(action)
    gRPC->>Server: gRPC Request
    Server->>Game: Update Game State
    Game->>Server: Game State
    Server->>gRPC: gRPC Response
    gRPC->>Env: Game State
    Env->>RLlib: (obs., rews., terms., truncs., infos)

    Note over RLlib,Game: Training Loop

The diagram above shows how the different components interact during training:

1. RLlib sends actions to the FootsiesEnv
2. The environment converts these actions into gRPC requests
3. The Unity Game Server processes the actions and updates the game state
4. The game state is sent back through gRPC to the environment
5. The environment processes the observation and returns it to RLlib

Installation

conda create -n footsiesgym python=3.10
conda activate footsiesgym
pip install -r requirements.txt

On a Mac, you may need to ensure you have cmake installed. You can install it using Homebrew:

brew install cmake

Training

Game Servers

If you are on a Linux system, run setup.sh to unpack the binaries then run skip to the training procedure. Otherwise, follow the steps below.

Before training, you'll need to launch the headless game servers. Scripts are provided to do so in scripts/start_local_{mac, linux}_servers.sh, but you must first unpack the binaries that are included into the binaries/ directory (the launch scripts assume this location). Important! If you are launching game servers manually, be sure to set launch_binaries to False in the environment configuration.

./scripts/start_local_{mac, linux}_servers.sh <num-train-servers> <num-eval-servers>

The two arguments correspond to num_env_runners and evaluation_num_env_runners, which can be specified in the experiment configuration. You must launch a corresponding number of servers for each. If you are running local debugging (see below; python -m experiments.train --debug), just launch one of each. If you're launching a full experiment, you'll need to match the number specified in the experiment configuration (defaults to 40 training and 5 evaluation env runners).

The scripts will start:

• Training servers from port 50051 (incrementing for each server)
• Evaluation servers from port 40051 (incrementing for each server)

Importantly, we map environment runners to a single port, which means that you can only run a single environment per environment runner.

Training Configuration

The default training utilizes the APPO algorithm (see the corresponding IMPACT paper). We also utilize a vanilla LSTM newtwork with parameters described in the respective experiment files.

Training can utilize either the new RLModule stack or old-stack in RLlib. Some functionality has yet to be implemented in the new stack (see open issues).

Old Stack

python -m experiments.train --experiment-name <experiment-name>

New Stack

python -m experiments.train_rlmodule --experiment-name <experiment-name>

Add the --debug flag to use only a single env runner (and single evaluation env runner) and local mode. This will enable breakpoint usage for local debugging.

Visualizing a Policy

To visualize gameplay:

1. Unpack the windowed build binaries of your choice (Mac or Linux).

2. Add the trained policy specification to the ModuleRepository in components/module_repository.py:

FootsiesModuleSpec(
    module_name="<policy-nickname>",
    experiment_name="<experiment-name>",
    trial_id="<trial-id>",  # specify if experiment has multiple trials
    checkpoint_number=-1,  # -1 for latest, otherwise specify checkpoint number
)

3. Run the game with:

./footsies_linux_windowed_021725 --port 80051

4. Configure policies in scripts/local_inference.py using the MODULES variable. Set "p1" to "human" to play against the AI (must install pygame).

Project Architecture

Core Components

• Environment (footsies/): The main game environment implementation that interfaces with the Unity game through gRPC.
• Models (models/): Neural network architectures for the RL agents
• Experiments (experiments/): Training configurations and experiment management
• Callbacks (callbacks/): Custom RLlib callbacks for monitoring and evaluation
• Components (components/): Reusable components like the module repository for policy management
• Utils (utils/): Utility functions and helper classes
• Scripts (scripts/): Helper scripts for server management and visualization

Key Features

• Multi-agent reinforcement learning environment
• gRPC-based communication with Unity game server
• Support for both headless and windowed game modes
• Integration with Ray RLlib for distributed training
• Custom LSTM-based policy networks
• Support for self-play training
• Evaluation against baseline policies (random, noop, back)
• Wandb integration for experiment tracking

Development

gRPC / Protobuf Updates

If updating the proto definitions:

1. Generate C# files (Windows):

.\protoc\bin\protoc.exe --csharp_out=.\env\game\proto\ --grpc_out=.\env\game\proto\ --plugin=protoc-gen-grpc=.\plugins\grpc_csharp_plugin.exe .\env\game\proto\footsies_service.proto

2. Generate Python files:

python -m grpc_tools.protoc -I. --python_out=. --grpc_python_out=. .\env\game\proto\footsies_service.proto

Project Structure

FootsiesGym/
├── binaries/           # Game server binaries
├── callbacks/          # RLlib callbacks
├── components/         # Reusable components
├── experiments/        # Training configurations
├── footsies/          # Core environment
├── models/            # Neural network architectures
├── protoc/            # Protocol buffer tools
├── scripts/           # Helper scripts
├── testing/           # Test files
└── utils/             # Utility functions

Contributing

1. Install pre-commit hooks to maintain code quality
2. Follow the existing code style and architecture
3. Add tests for new features
4. Update documentation as needed

License

This project is based on the open-source Footsies game by HiFight. Please refer to the original game's license for more information.