Tiếng Việt · Svenska · 简体中文 · Deutsch · العربية · Español · 日本語 · Русский · ไทย · Türkçe · English
VERA20K is a new engine for Red Alert 2: Yuri's Revenge. It plays like the original, with the same units, maps and look, and runs on Windows, macOS and Linux. It's built for bigger battles, with up to 30 players and 20,000 units on one map.
VERA20K is made by gamers, for gamers, and gamers have the final say in where it goes.
- Install Red Alert 2: Yuri's Revenge from Steam or the EA app.
- Download VERA20K for your system from the releases page.
- Open the file you downloaded. It finds your game and sets up VERA20K in its own folder.
Stuck? See the help page.
It's in active development: skirmish is playable on Windows, macOS and Linux, campaigns partly work, and online multiplayer (experimental) is now available. Earlier versions and what changed in each are on the releases page.
To launch single-player YR skirmishes or campaigns from a CnCNet client, see the offline client setup.
- Keep the gameplay, visuals and atmosphere of the original Red Alert 2: Yuri's Revenge.
- Support bigger battles: up to 30 players and 20,000 units on 500×500 maps.
- Incorporate known RTS features and some never seen before.
- Integrated multiplayer client
See the roadmap for current priorities and future plans.
Contributors can take responsibility for engine areas, with broad freedom to make changes that move VERA20K forward.
Maintainers will help with review, integration and merging. You'll keep full credit for your contribution.
Discussion is on Discord and in the QQ group (1097193563).
The engine has three main parts:
- Simulation: Owns gameplay state and logic.
- Rendering: An absolutely new GPU rendering pipeline using the original game assets, built to preserve the original look.
- Application: Handles input, menus, audio, and platform integration, connecting the systems.
This separation supports deterministic gameplay.
Arrows show data flow:
You need:
- Rust and Git: Rust 1.97 or later, installed with rustup, and Git.
- Build tools: on Windows, the Visual Studio C++ build tools, which the Rust installer offers
to install; on macOS,
xcode-select --install; on Debian and Ubuntu,sudo apt install build-essential libasound2-dev libxkbcommon-x11-0 pkg-config.
git clone https://github.com/YuriPlanet/vera20k.git
cd vera20k
cp config.toml.example config.toml
# Edit config.toml and set ra2_dir to your game folder before running:
cargo run --release --bin vera20kMost of the code is written by AI coding agents. They use Ghidra to study the original engine, then port its behavior to Rust and check it with comparison tools and playtesting. Agents follow AGENTS.md.
VERA20K plays like the original game by default. New features, including extensions from mods such as Ares, stay off until they are turned on with one of:
- A VERA player option, in Options, saved under
[VERA]inVERA.INI. - A build option, such as
--features phobosfor the supported Phobos extensions. - An INI key, set by a mod or a map. Ares keys, or a mod that ships
ares.mix, turn on the supported Ares extensions.
Sound, graphics and controls are saved in VERA.INI. Gameplay rules come from lobby
settings, mods or maps.
The modding guide explains how to make your own mods.
All donations received are distributed to contributors according to the TIBTRE contribution ledger.
Payouts to contributors:
Thanks to OpenRA, XCC Mixer, the ModEnc wiki, Project Perfect Mod, EA's GPL source release of Command & Conquer and Red Alert, World-Altering Editor, Final Alert, YRpp, Ares, Phobos and many others.
Copyright © 2026 Halvor Nikolai Rusten and VERA20K contributors. Licensed under the GPLv3 with additional terms. This repository contains no game files. Command & Conquer and Red Alert are trademarks of Electronic Arts Inc., and the screenshots and the app icon, Red Alert 2's red star, show game art owned by Electronic Arts. VERA20K is not affiliated with or endorsed by Electronic Arts.
This product includes software developed by the Ares Contributors. This product includes software developed by the Phobos Developers.
Read the legal notice before you share, sell or fork VERA20K.
- WebAssembly preview: an opt-in single-player build that runs in a browser.
- Modding guide: what mods can and can't do, and how VERA20K differs from the original game.
- INI profiles: choosing rules, art and AI files.
- Ares, Phobos, NPatch and VeraX: extension support and limitations.
- Engine overview: code layout and how the engine fits together.
- Developer tools: builds, tests and asset inspection.
- Map testing: scripted scenarios, screenshots and match observations.
- Native comparisons: comparing behavior with the original game.
- Ghidra workflow: inspecting the original engine.


