# Swords & Souls: Neverseen

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

- Steam appid: 679900
- Developer: SoulGame Studio
- Publisher: Armor Games Studios
- Released: 2019 · Genre: Action · List price: $14.99
- Deal grade: A (A = dormant with >=$5k/mo opportunity, D = low signal)
- Est. net residual revenue: $3.8k to $5.8k per month (mid $4.8k)
- Opportunity score: $8.9k/month at x1.85 dormancy multiplier
- Est. lifetime owners: 241.6k · Est. lifetime net revenue: $778.4k
- Review sentiment: 93% positive across 6433 reviews (6040 from Steam purchases)
- Review velocity: 59.7 reviews/month (6-month average)

## Why it's flagged

- Developer silent for 13 months
- Studio active elsewhere (3 titles tracked), so this one may welcome a partner
- Last build shipped 6.9 years ago

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

| Stage | USD/month |
|---|---|
| Gross storefront sales | $8.7k |
| After VAT / sales tax (-13% blended) | $7.6k |
| After refunds (-9.5% median) | $6.9k |
| Net to developer (after Steam 30%) | $4.8k |

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

48, 30, 95, 44, 70, 67, 140, 88, 65, 63, 91, 160, 85, 81, 52, 75, 75, 71, 66, 67, 43, 57, 43, 82

## Estimated acquisition range

$115.3k to $230.7k (2-4x the trailing net annuity of $57.7k/year). Same error range applies.

## Analyst notes (AI-assisted)

A turn-based RPG hybrid with idle-battler mechanics and Paper Mario-inspired charm, built on a beloved Flash game franchise.

Swords & Souls: Neverseen is a quiet performer with genuine community attachment, 93% positive sentiment, and $4,806/mo residual revenue five years post-launch. The game carries nostalgia weight from its Flash origins and shows consistent 50-160 monthly sales across the trailing 24 months, suggesting a durable long-tail audience. For a publisher seeking to expand a proven casual-to-mid-core catalog or explore revival tactics, this title offers low risk, modest but stable cash flow, and a foundation for sequels or expanded IP play, though zero activity in the past year warrants conversation with the dev team about roadmap intent.

- Most realistic play: publishing
- Risk (other): Developer has posted no public updates in 13 months; unclear if team is actively maintaining or has other priorities.
- Risk (market): Indie idle-battler and nostalgia-driven categories are crowded; growth past current audience will require content, marketing, or platform distribution support.
- Risk (tech): Flash-to-Steam port may face long-term maintenance burden if underlying engine is not actively developed.

What players are asking for:
- More elaborate endgame content beyond the existing infinite mode
- Quality-of-life improvements to reduce repetitive grind (e.g., quest design like the coin-flip challenge cited in reviews)
- Balance adjustments for weapons and builds (e.g., bow and soul medal)

Suggested first moves:
1. Contact SoulGame Studio and Armor Games Studios to confirm development status, roadmap horizon, and openness to publishing partnership or acquisition of live-ops rights.
2. Conduct cohort analysis on the 241k lifetime purchasers: identify which regions, acquisition channels (e.g., bundle history, ITAD tracking absent), and price points retain the highest repeat engagement.
3. Test a limited seasonal content drop or cosmetic monetization experiment to validate whether the dormant audience will re-engage and spend beyond the base purchase, de-risking a larger revival campaign.

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