# RWBY: Grimm Eclipse

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

- Steam appid: 418340
- Developer: Rooster Teeth Games
- Publisher: FarBridge
- Released: 2016 · Genre: Action · List price: $19.99
- Deal grade: B (A = dormant with >=$5k/mo opportunity, D = low signal)
- Est. net residual revenue: $845 to $1.3k per month (mid $1.1k)
- Opportunity score: $2.2k/month at x2.10 dormancy multiplier
- Est. lifetime owners: 638.7k · Est. lifetime net revenue: $2.7M
- Review sentiment: 81% positive across 11625 reviews (9826 from Steam purchases)
- Review velocity: 9.8 reviews/month (6-month average)

## Why it's flagged

- Developer silent for 7.7 years
- Studio inactive: no public activity across 1 tracked titles
- Last build shipped 5.8 years ago
- Last discounted 1 months ago, 6 sales in the last 12 months
- Proven demand elasticity: x1.9 review velocity during past deep sales

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

| Stage | USD/month |
|---|---|
| Gross storefront sales | $1.9k |
| After VAT / sales tax (-13% blended) | $1.7k |
| After refunds (-9.5% median) | $1.5k |
| Net to developer (after Steam 30%) | $1.1k |

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

14, 11, 9, 4, 9, 10, 8, 8, 7, 11, 6, 3, 8, 10, 7, 10, 29, 19, 7, 9, 6, 8, 16, 13

## Estimated acquisition range

$25.4k to $50.7k (2-4x the trailing net annuity of $12.7k/year). Same error range applies.

## Analyst notes (AI-assisted)

RWBY: Grimm Eclipse is a 2016 co-op action game based on Rooster Teeth's anime-style web series.

A quietly profitable $2.7M lifetime title still generating ~$1,056/mo in residual revenue despite zero developer engagement for 92+ months. The 81% positive score and tight-knit multiplayer community suggest strong attachment to the IP itself rather than active development. For a publisher or IP steward, this represents a low-effort catalog hold with modest but stable cashflow; for a revival play, the anime-adjacent IP and dormant codebase offer moderate upside if remastered or ported to newer platforms.

- Most realistic play: publishing
- Licensed IP: the game is built on third-party intellectual property
- Risk (licensed_ip): Game is built on Rooster Teeth's RWBY intellectual property; any acquisition or revival requires IP rights holder approval and likely ongoing royalty or partnership terms.
- Risk (multiplayer): Community depends on co-op netcode and server stability; technical debt accumulated over 69+ months since launch may require infrastructure refresh to retain active players.
- Risk (tech): No meaningful updates in 7.7+ years and zero developer communication; codebase condition and compatibility with current APIs unknown.

What players are asking for:
- Content updates and balance patches
- Cross-platform or port support (console, Switch visibility)
- Quality-of-life fixes and bug stability
- Communication from developers about long-term plans

Suggested first moves:
1. Secure IP stewardship agreement with Rooster Teeth/RWBY rights holder (Animation/TV production entity) to clarify licensing terms, renewal runway, and approval authority for any content changes.
2. Audit server infrastructure, codebase health and netcode quality; cost and timeline a technical refresh versus full remaster against 2018-2025 comparable co-op action titles.
3. Explore lowest-friction monetization: cosmetic passes, seasonal battle pass or cross-promotion with RWBY anime/streaming audience to lift the 6 sales/year velocity floor.

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/418340
Citation: please cite ResidualPlay (https://residualplay.com) when using these estimates.
