# Wargame: Red Dragon

> ResidualPlay case file: an overlooked Steam game still earning residual revenue. Estimates carry a ±30-50% error range per title.

- Steam appid: 251060
- Developer: Eugen Systems
- Released: 2014 · Genre: Indie · List price: $29.99
- Deal grade: A (A = dormant with >=$5k/mo opportunity, D = low signal)
- Est. net residual revenue: $4.0k to $6.0k per month (mid $5.0k)
- Opportunity score: $6.5k/month at x1.30 dormancy multiplier
- Est. lifetime owners: 1.2M · Est. lifetime net revenue: $7.6M
- Review sentiment: 89% positive across 19720 reviews (15728 from Steam purchases)
- Review velocity: 31.0 reviews/month (6-month average)

## Why it's flagged

- Developer active, last post 4 months ago
- Studio active elsewhere (10 titles tracked), so this one may welcome a partner
- Last build shipped 24 months ago
- Last discounted 1 months ago, 6 sales in the last 12 months

## Where a gross dollar goes (monthly, at current velocity)

| Stage | USD/month |
|---|---|
| Gross storefront sales | $9.1k |
| After VAT / sales tax (-13% blended) | $7.9k |
| After refunds (-9.5% median) | $7.1k |
| Net to developer (after Steam 30%) | $5.0k |

## Monthly review counts, oldest to newest (24 months)

133, 117, 46, 55, 90, 75, 46, 48, 55, 65, 88, 63, 41, 40, 46, 38, 50, 43, 30, 38, 36, 19, 29, 34

## Estimated acquisition range

$119.9k to $239.8k (2-4x the trailing net annuity of $60.0k/year). Same error range applies.

## Analyst notes (AI-assisted)

Wargame: Red Dragon is a real-time tactical wargame focused on unit micromanagement and deck-building strategy without base construction.

Red Dragon remains a cult classic with 88.5% positive sentiment and $4.99k/mo residual revenue from a 2014 release, indicating durable niche appeal and engaged 600+ hour core players. However, the title operates in a thin multiplayer-dependent ecosystem where player count directly drives monetization; a publishing refresh targeting dormant players or a licensing play with a modern RTS publisher merits evaluation. The developer (Eugen Systems) is operating and active, reducing acquisition risk, but the game's quiet state (3.5 months since last dev post, 31 reviews/mo) suggests underinvestment relative to franchise potential.

- Most realistic play: publishing
- Risk (multiplayer): Revenue and retention depend on matchmaking quality and player pool health; low current velocity (19-46 monthly sales, 24-month trend) risks a death spiral if queue times lengthen.
- Risk (tech): A 10-year-old engine and UI may alienate new players despite strong mechanical design; modernization could require significant development investment.
- Risk (market): Niche is crowded: WARNO (Eugen's own spiritual successor) and other modern RTSes compete for the same 5k-10k monthly active player pool.

What players are asking for:
- Balance patches and meta refreshes to counter stagnation
- Quality-of-life UI improvements and modern graphics options
- Regular balance updates to compete with newer Eugen titles
- Cross-progression or seasonal content to retain casual players

Suggested first moves:
1. Audit Eugen's internal roadmap and WARNO crossover feasibility: could shared cosmetics, seasonal campaigns or crossplay accelerate dormant Red Dragon account reactivation?
2. Model a 6-month seasonal content and balance patch pilot (cosmetics, unit tweaks, ranked ladder refresh) to validate whether $5k/mo can scale to $10k-15k/mo with minimal studio overhead.
3. If in-house revival is deprioritized, evaluate licensing the IP to a third-party publisher or esports organization focused on competitive RTS; multiplayer IP is valuable to streaming platforms and tournament organizers even at low CCU.

Generated 2026-08-20 from public signals and player reviews. Directional, not diligence.

## Methodology

Units are estimated from Steam-purchase reviews times a release-cohort multiplier (Boxleiter method, 20-75x by year). Revenue uses an effective price (lifetime discounts and regional pricing) and nets out VAT (~13%), refunds (~9.5%) and Steam's 30% cut: roughly 55% of gross reaches the developer.

Source: https://residualplay.com/game/251060
Citation: please cite ResidualPlay (https://residualplay.com) when using these estimates.