简体中文

Discord

ORPHEUS is an open-source server reimplementation for Overwatch 1 retail 1.74.0.0.104319. It is an independent, unofficial research and game preservation project. The long-term goal is to reproduce the server behavior and client-facing events for this build across its heroes, maps and modes. The server is still in development, with Soldier: 76 in the Practice Range as the first end-to-end target.

Test skills in the local Practice Range · Join an existing server

Contribute · Roadmap · Rust branch · Verification record · Changelog · Open issues

The main branch contains the community-maintained Python server and Windows launcher. Native server development continues on the separate rust branch.

Each tester runs ORPHEUS and the original client on the same Windows PC. Install 64-bit Python 3.12 and use your authorized 1.74.0.0.104319 installation and prepared Practice Range runtime. Download the Python source ZIP

Extract ORPHEUS and put the prepared pack under runtime-data/ in the extracted checkout. Put data/, bnet/ and collision/ directly inside runtime-data/.

ORPHEUS/
  runtime-data/
    manifest.json
    data/
    bnet/descriptors.pb
    collision/0688.col

ORPHEUS detects this directory when it contains manifest.json or data/. An explicit ORPHEUS_RUNTIME_DIR takes precedence, and the legacy checkout layout remains the fallback. From the ORPHEUS directory, run the startup preflight. It lists missing startup inputs and checks the signing input length. Map collision is checked when a scene loads.

.\scripts\START.bat --check-runtime

If you need a local relay/owwfd_relay.dll build, install the x64 MSVC Build Tools. Open the x64 Native Tools Command Prompt and run this from the ORPHEUS directory.

.\relay\build.bat

Pass the game installation directory or its _retail_\Overwatch.exe to the launcher. With no path argument, the launcher uses its saved client path or opens a file picker.

.\scripts\START_LOCAL.cmd --game-exe 'C:\path\to\Overwatch'

The launcher creates a Python environment if needed and remembers the selected installation for future launches and collision preparation. Enter the Practice Range, pick the hero you are testing, and record the exact input and outcome for one skill at a time. Original-client verification

A complete authorized runtime includes protocol data, signing input, gameplay graphs and map collision. The runtime guide lists the source and preparation route for each required file. Preparing the entire runtime from a game folder alone remains open. Runtime guide

• tools/prepare_client_catalogs.py generates four catalog JSON files locally from the target game installation with pinned DataTool. Generate client catalogs
• tools/prepare_server_runtime.py assembles the runtime and writes a manifest. Optional game and DataTool arguments generate missing catalogs, gameplay data and map caches from local inputs. The remaining authorized files must be ready in the source checkout. Generate missing data while packing

For a new Practice Range pack in the default location, run this from the ORPHEUS directory with an authorized prepared source checkout.

py -3.12 -B tools/prepare_server_runtime.py --source 'C:\path\to\prepared-checkout' --destination .\runtime-data --map 0688

With the runtime in place, run scripts/START_SERVER_LOCAL.cmd to start the loopback services and dashboard at http://127.0.0.1:3725. This entry needs the Python environment and prepared runtime.

On Windows, use the 1.74.0.0.104319 client and 64-bit Python 3.12. Ask the host for the address of their running, compatible ORPHEUS server. The host runs the service with its authorized runtime. The player launcher needs the game folder and host address and runs without a local server runtime or Windows relay.

Open scripts/JOIN_SERVER.cmd from the same checkout. Enter the address as host:port, then select the client if prompted. You can also pass the address and game folder directly in PowerShell.

.\scripts\JOIN_SERVER.cmd --server 'HOST:3724' --game-exe 'C:\path\to\Overwatch'

The launcher requests the client's simpler tournament menu. Original-client verification is pending.

Use Windows with 64-bit Python 3.12. The source tests below use synthetic fixtures. Node.js 24 is used for the separate dashboard test.

py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\.venv\Scripts\python.exe -B -m unittest discover

Python discovery runs the public suite. See contributor checks for the dashboard suite and the separate local runtime tests.

An automated result covers the fixture or replay named in its evidence. A manual observation covers the build, commit and steps that were actually tried. No complete original-client acceptance pass has been recorded for the first target scenario. See the verification record and changelog.

• Developers and AI-assisted contributors can start with the public source tests. The guide covers Codex, Claude Code and the same review requirements for all submissions. Contribution guide
• Reverse engineers can help pin a single field, state transition, event or timing rule to build 104319. Start with the relevant evidence and report uncertainty explicitly. Research evidence
• Players can run the local Practice Range and report a short, repeatable gameplay result. Reports of working behavior are welcome alongside bugs. Gameplay verification
• New contributors can look for tasks that use the public checkout and synthetic data. Good first issues

The roadmap tracks the full build scope. CREDITS.md records the original 1.74 lobby project, research sources and upstream authors. The public source retains the original MIT license notice. Overwatch and its assets belong to their respective rights holders. Keep game clients, commercial assets, keys, private logs, raw captures and dumps out of public submissions.