The Remake Strategy Decider

What you’re building

You’ve built three tools so far: a source availability scanner that tells you what technical material exists, a rights map that shows who owns BloodRayne and how, and a deal structure advisor that recommends how to approach the negotiation. Each one answers a piece of the puzzle. But right now those pieces live in separate folders on your machine. To make a real decision — should I actually pursue BloodRayne? — you need all of those inputs feeding into one assessment.

That’s what this tool does. You type an IP name and it pulls together everything: source code availability, rights holder, recommended deal structure, risk score across multiple dimensions, estimated total cost (rights + development), and a clear go or no-go with the reasoning spelled out. It’s the business case generator you’d use before committing real money and months of your life to any IP on your target list.

And here’s the part that makes it actually useful: it’s pre-loaded with BloodRayne, Legacy of Kain, Oni, and Darkwatch so you can compare them side by side and see which one has the best risk-adjusted opportunity. Because maybe BloodRayne isn’t the best first project. Maybe one of the others has a shorter path to market. The data should drive that decision, not nostalgia.

ℹSoftware pattern: Multi-source decision engine

Aggregated data + risk scoring + recommendation logic = decision tool. This pattern works anywhere you need to combine research from multiple sources into a single go/no-go: product launches, investment decisions, vendor evaluations, hiring. The underlying approach is the same.

The showcase

Here’s what the finished app does:

IP selector: Dropdown with pre-loaded IPs (BloodRayne, Legacy of Kain: Soul Reaver, Oni, Darkwatch) plus a text input for adding new ones manually
Source availability panel: Pulled from your L1 scanner data — source status, community projects, engine info, rebuild difficulty rating
Deal structure recommendation: Embedded scoring from your L3 advisor — recommended approach, cost range, timeline estimate
Risk scorecard: Five dimensions rated 1-10 with color-coded bars — Rights Complexity, Source Availability, Market Viability, Development Difficulty, Financial Risk
Estimated total cost: Combined range covering rights acquisition + development, broken into line items (rights fee, legal costs, prototype, full development, QA/launch)
Go/No-Go verdict: A clear recommendation with confidence level (Strong Go, Conditional Go, Proceed with Caution, No-Go) and 3-5 bullet points of reasoning
Comparison mode: Select 2-3 IPs side by side to see which one has the best opportunity profile
Export: Download the full assessment as a Markdown document

The prompt

Open your terminal, create a project folder, start your AI CLI tool, and paste this prompt:

Build a React application called remake-decider that provides go/no-go
recommendations for retro game IP remake projects. It integrates source
availability data and deal structure analysis into a single decision
dashboard. Use Vite as the bundler and plain CSS.

PROJECT STRUCTURE:
remake-decider/
  package.json
  index.html
  src/
    main.jsx
    App.jsx
    components/
      IPSelector.jsx          (dropdown + manual entry)
      SourcePanel.jsx         (source availability display)
      DealPanel.jsx           (deal structure recommendation)
      RiskScorecard.jsx       (5-dimension risk display)
      CostEstimator.jsx       (total cost breakdown)
      Verdict.jsx             (go/no-go recommendation)
      ComparisonView.jsx      (side-by-side IP comparison)
      ExportButton.jsx        (Markdown download)
    data/
      ips.js                  (pre-loaded IP database)
      scoring.js              (risk scoring algorithms)
    styles/
      app.css

REQUIREMENTS:

1. PRE-LOADED IP DATABASE (data/ips.js)
   Each IP entry contains integrated data:

   a. BloodRayne
      sourceStatus: "nothing"
      sourceDetail: "No source code, no decompilation project, no mod SDK. Terminal Reality's Infernal Engine is completely closed. Terminal Cut editions by Ziggurat appear to be binary-level modifications, not source-based. Clean-room rebuild required."
      rightsHolder: "Ziggurat Interactive"
      rightsClarity: 7  (out of 10 -- confirmed owner, but derivative works scope unverified)
      dealRecommendation: "License"
      dealReasoning: "Ziggurat's business model is built around licensing retro IPs. They're predisposed to deal. Buying outright unlikely as they want to retain the portfolio. Revenue share possible as fallback."
      estimatedRightsCost: { low: 75000, high: 200000, currency: "USD" }
      estimatedDevCost: { low: 300000, high: 1500000, currency: "USD" }
      marketViability: 7  (established franchise, nostalgia factor, Terminal Cut sales data)
      developmentDifficulty: 8  (no source = full rebuild of combat, camera, AI systems)
      financialRisk: 6  (moderate -- known IP reduces marketing risk, but rebuild cost is high)
      brandStrength: 7  (recognizable name in action-game community, two films increased awareness)
      communityProjects: []
      platforms: ["PS2", "Xbox", "GameCube", "PC"]
      releaseYear: 2002
      genre: "Third-person action"

   b. Legacy of Kain: Soul Reaver
      sourceStatus: "decompilation"
      sourceDetail: "Active community decompilation project provides technical reference for engine internals, level formats, and game logic. Cannot use decompiled code directly but it serves as an engineering roadmap."
      rightsHolder: "Crystal Dynamics / Embracer Group"
      rightsClarity: 4  (Embracer restructuring creates uncertainty about who makes licensing decisions)
      dealRecommendation: "Wait or Spiritual Successor"
      dealReasoning: "Embracer Group's ongoing restructuring makes licensing negotiations unpredictable. Crystal Dynamics was part of the Square Enix sale to Embracer in 2022. Until Embracer's corporate structure stabilizes, pursuing rights is risky."
      estimatedRightsCost: { low: 150000, high: 500000, currency: "USD" }
      estimatedDevCost: { low: 200000, high: 800000, currency: "USD" }
      marketViability: 9  (beloved franchise, massive fan demand, no modern remake)
      developmentDifficulty: 5  (decompilation project significantly reduces reverse-engineering)
      financialRisk: 7  (high market demand offset by uncertain rights situation)
      brandStrength: 9  (one of the most requested remakes in gaming forums)
      communityProjects: [{ name: "Soul Reaver Decomp", url: "https://github.com/Flavor-of-Code/soul-reaver-decomp", status: "active" }]
      platforms: ["PS1", "Dreamcast", "PC"]
      releaseYear: 1999
      genre: "Action-adventure"

   c. Oni
      sourceStatus: "decompilation"
      sourceDetail: "Partial source reconstruction by dedicated community. Oni Community Edition has maintained mods and patches for 20+ years. Technical reference available but incomplete."
      rightsHolder: "Take-Two (publishing) / Bungie (IP, unclear)"
      rightsClarity: 3  (rights split between publisher and developer, Bungie's post-Microsoft independence complicates things)
      dealRecommendation: "Spiritual Successor"
      dealReasoning: "Rights chain is tangled between Take-Two and Bungie. Bungie's recent independence from Sony (after partial acquisition) adds another layer. Neither company is likely to prioritize licensing a dormant 2001 title. A spiritual successor captures the gameplay without the legal complexity."
      estimatedRightsCost: { low: 200000, high: 800000, currency: "USD" }
      estimatedDevCost: { low: 250000, high: 900000, currency: "USD" }
      marketViability: 5  (cult following but limited mainstream recognition)
      developmentDifficulty: 6  (partial community source helps, melee+shooter hybrid is complex)
      financialRisk: 8  (high rights cost + moderate market = poor risk-adjusted return)
      brandStrength: 4  (cult classic but low general awareness)
      communityProjects: [{ name: "Oni Community Edition", url: "https://wiki.oni2.net", status: "active" }]
      platforms: ["PS2", "Mac", "PC"]
      releaseYear: 2001
      genre: "Third-person action"

   d. Darkwatch
      sourceStatus: "nothing"
      sourceDetail: "No source code, no decompilation, no modding tools. High Moon Studios' proprietary engine is completely closed. Studio now part of Microsoft via Activision acquisition."
      rightsHolder: "Microsoft (via Activision Blizzard King acquisition of High Moon Studios)"
      rightsClarity: 2  (rights chain complicated by multiple acquisitions; publishing split between Capcom NA and Ubisoft PAL adds territory complexity)
      dealRecommendation: "Spiritual Successor"
      dealReasoning: "Microsoft's legal apparatus makes licensing a single dormant IP from a subsidiary studio impractical for an indie developer. The publishing rights split between Capcom and Ubisoft creates additional territory complications. A spiritual successor with original vampire-western IP is the only realistic path."
      estimatedRightsCost: { low: 500000, high: 2000000, currency: "USD" }
      estimatedDevCost: { low: 400000, high: 1500000, currency: "USD" }
      marketViability: 4  (cult following, single platform, limited exposure)
      developmentDifficulty: 8  (no source, FPS+melee hybrid, period setting needs extensive asset work)
      financialRisk: 9  (high acquisition cost + low brand recognition = poor economics)
      brandStrength: 3  (PS2/Xbox exclusive, never ported, limited audience)
      communityProjects: []
      platforms: ["PS2", "Xbox"]
      releaseYear: 2005
      genre: "First-person shooter"

2. RISK SCORECARD (RiskScorecard.jsx)
   Display 5 risk dimensions as horizontal bars (1-10 scale):
   - Rights Complexity (inverted from rightsClarity -- lower clarity = higher risk)
   - Source Availability (derived from sourceStatus: nothing=9, mod-sdk=6, decompilation=4, official-release=1)
   - Market Viability (inverted -- high viability = low risk)
   - Development Difficulty (direct)
   - Financial Risk (direct)

   Calculate an overall risk score as the weighted average:
   - Rights Complexity: 25% weight
   - Source Availability: 20% weight
   - Market Viability: 20% weight
   - Development Difficulty: 15% weight
   - Financial Risk: 20% weight

   Color code bars: 1-3 green, 4-6 yellow, 7-10 red

3. COST ESTIMATOR (CostEstimator.jsx)
   Break down total cost into line items:
   - Rights acquisition (from estimatedRightsCost)
   - Legal counsel: flat $30K-$60K estimate
   - Prototype development: 15% of estimatedDevCost
   - Full development: estimatedDevCost
   - QA and launch: 10% of estimatedDevCost
   - Show low/high range and a midpoint total
   - Format as a table with a total row

4. VERDICT (Verdict.jsx)
   Based on overall risk score:
   - Score 1-3: "Strong Go" (green badge) -- low risk, clear path forward
   - Score 3.1-5: "Conditional Go" (yellow badge) -- viable but address specific risks
   - Score 5.1-7: "Proceed with Caution" (orange badge) -- significant obstacles
   - Score 7.1-10: "No-Go" (red badge) -- too risky given current conditions

   Below the verdict, show 3-5 bullet points explaining the key factors.
   These should reference specific data: "Source availability is rated 9/10
   risk because no source code, decompilation, or mod SDK exists."

5. COMPARISON VIEW (ComparisonView.jsx)
   Allow selecting 2-3 IPs for side-by-side comparison.
   Show a summary table: IP | Verdict | Risk Score | Cost Range | Deal Type | Key Advantage | Key Risk
   Below the table, generate a 2-paragraph recommendation of which IP
   represents the best opportunity and why.

6. EXPORT (ExportButton.jsx)
   Download button generates a Markdown file containing:
   - Title: "Remake Strategy Assessment: [IP Name]"
   - Date
   - Source availability summary
   - Deal structure recommendation
   - Risk scorecard (as a Markdown table)
   - Cost estimate breakdown
   - Verdict with reasoning
   - Next steps

7. STYLING (styles/app.css)
   Dark theme:
   - Background: #09090b body, #18181b cards, #1e1e2a hover
   - Text: #e4e4e7 primary, #a1a1aa secondary
   - Accent: #8B5CF6
   - Risk bars use CSS gradients: green (#22c55e) to yellow (#eab308) to red (#ef4444)
   - Verdict badges: large, centered, with glow effect matching color
   - Responsive: single column mobile, two-column desktop
   - Max-width: 1280px

DEPENDENCIES: react, react-dom, vite, @vitejs/plugin-react

💡Copy-paste ready

That entire block is the prompt. Every risk score, cost estimate, and deal recommendation is pre-calibrated based on the research from your previous tools. The data is consistent across all four IPs so comparisons are meaningful.

What you get

After the AI finishes generating:

remake-decider/
  package.json
  index.html
  src/
    main.jsx
    App.jsx
    components/
      IPSelector.jsx
      SourcePanel.jsx
      DealPanel.jsx
      RiskScorecard.jsx
      CostEstimator.jsx
      Verdict.jsx
      ComparisonView.jsx
      ExportButton.jsx
    data/
      ips.js
      scoring.js
    styles/
      app.css

Fire it up

cd remake-decider
npm install
npm run dev

Open the URL. You’ll see the IP selector at the top. Pick BloodRayne from the dropdown.

The dashboard populates immediately: source availability shows red (nothing — clean-room rebuild), the deal panel recommends License, the risk scorecard lights up with a mix of yellow and red bars, the cost estimator shows a range of roughly $400K-$1.8M total, and the verdict badge appears.

For BloodRayne, you should see something like “Conditional Go” — the brand strength and Ziggurat’s licensing-friendly model create a viable path, but the lack of source code and the resulting development cost push the risk into cautionary territory.

Compare IPs

Click into comparison mode and select BloodRayne, Legacy of Kain, and Darkwatch. The comparison table reveals the landscape immediately:

Legacy of Kain has the best market viability (9/10) and source availability (decompilation exists), but the Embracer restructuring makes rights acquisition unpredictable
BloodRayne has the clearest path to a deal (Ziggurat is built for this), but the highest development cost due to no source
Darkwatch is effectively a no-go — Microsoft rights chain, split publishing, no source, weak brand recognition

The generated recommendation should point to BloodRayne as the best first project: the rights path is the clearest, the brand is strong enough, and the development difficulty — while high — is at least a known quantity. Legacy of Kain is the better IP to acquire if Embracer’s situation resolves, but you can’t plan a business around “if.”

If something is off

Problem	Follow-up prompt
Risk bars not rendering	`The RiskScorecard should use div elements with dynamic width set via inline style: width of (score * 10)%. Background color should be calculated from score: under 4 is #22c55e, 4-6 is #eab308, over 6 is #ef4444.`
Comparison view only shows one IP	`The ComparisonView component needs a multi-select state (array of selected IP keys). Use checkboxes next to each IP name. Only render the comparison table when 2 or more IPs are selected.`
Cost estimates showing NaN	`Make sure ips.js exports numeric values for estimatedRightsCost and estimatedDevCost, not strings. The CostEstimator should receive these as props and calculate derived costs (legal, prototype, QA) using multiplication.`

Deep dive

Here’s what makes this tool more than a spreadsheet:

Integrated assessment beats separate analyses. Your source scanner, rights map, and deal advisor each answered one question. This tool answers the only question that matters: should you do this? By combining source availability, rights complexity, market viability, development difficulty, and financial risk into a single weighted score, you get a decision, not a pile of data.
The risk weighting reflects reality. Rights complexity is weighted highest (25%) because it’s the hardest risk to mitigate. You can solve development difficulty with time and money. You can solve financial risk with funding. You cannot solve a rights holder who won’t deal. Source availability and market viability each get 20% because they’re the next-biggest swings — no source triples your development budget, and low market viability means even a perfect product might not sell.
Pre-loaded data makes comparisons instant. The four IPs aren’t random — they represent four different scenarios: BloodRayne (clear rights, no source), Legacy of Kain (unclear rights, has source), Oni (tangled rights, some source), Darkwatch (impossible rights, no source). Comparing them teaches you how these variables interact. Darkwatch is the cautionary tale: even if the game is interesting, impossible rights + no source + weak brand = no-go.
The verdict is binary on purpose. Go or no-go. Not “it depends.” The nuance lives in the reasoning bullets and the risk scorecard, but the verdict forces a decision. In practice, “Proceed with Caution” means “go, but address these specific risks first.” “No-Go” means “spend your time on a different IP.” Indecision is more expensive than a wrong decision at this stage.
Cost estimates are ranges, not numbers. Nobody knows what a BloodRayne license costs until Ziggurat quotes you. Nobody knows what development costs until you’ve prototyped. The ranges ($400K-$1.8M total for BloodRayne) give you order-of-magnitude guidance for fundraising conversations without pretending precision that doesn’t exist.

🔍Why BloodRayne is your best first project

Comparing the four IPs with this tool surfaces something important: BloodRayne has the most actionable path forward. Not the best IP in the abstract — Legacy of Kain has better market viability and easier development (decompilation exists). But Legacy of Kain’s rights situation is in flux due to Embracer’s restructuring, and you can’t start a company on “maybe.”

BloodRayne’s advantages are practical:

Ziggurat will take your call. Their business model is licensing. This is not a cold pitch to a company that doesn’t know what to do with the IP.
The cost range is indie-accessible. $75K-$200K for rights is within reach of a focused Kickstarter or a small angel round. You don’t need Series A funding.
The brand has built-in awareness. Two films (bad films, but awareness is awareness), recent Terminal Cut editions, and a dedicated fan community mean your marketing isn’t starting from zero.
The development difficulty is known. No source means clean-room rebuild, which is hard but plannable. You’re not waiting for someone to release source code or for a rights situation to resolve.

Start with BloodRayne because you can actually start. Revisit Legacy of Kain when Embracer sorts itself out.

Customize it

Your decider works for four IPs. Extend it for real portfolio management:

Add a manual IP entry form

Add an "Add New IP" button that opens a form with all the required
fields: name, source status, rights holder, rights clarity (1-10),
deal recommendation, cost estimates, and all five risk dimension
scores. When submitted, add the new IP to the selector dropdown and
persist it in localStorage. This lets Lora evaluate IPs not in the
pre-loaded set.

Add a portfolio priority ranker

Add a "Rank Portfolio" button that takes all IPs in the database,
runs them through the scoring engine, and displays a ranked list
from best opportunity to worst. Show a stacked bar chart where each
bar is color-coded by the five risk dimensions. The IP at the top
is your recommended first project.

Add a timeline simulator

Add a timeline view that shows the estimated path to launch for the
selected IP: Month 1-2 rights negotiation, Month 3-4 prototyping,
Month 5-18 development, Month 19-20 QA/launch. Adjust durations
based on the IP's risk scores -- higher source availability risk
extends development, higher rights complexity extends negotiation.
Show the total estimated time to market.

What’s next

You now have the full decision stack: source availability, rights mapping, deal structure, and go/no-go recommendation. BloodRayne has a “Conditional Go” — the path is clear enough to pursue, with specific risks to manage. In the next lesson, you’ll build the Retro Remake Market Tracker, a dashboard that analyzes successful and failed game remakes by budget, price, platform, and review scores. That’s the market evidence that turns your “Conditional Go” into a pitch deck slide. You’ll see exactly where BloodRayne-scale remakes land in the market and what separates the ones that succeeded from the ones that didn’t.

What you'll learn