Applied The Lora Playbook

The Remake Strategy Decider

Last reviewed

Beginner

What you'll learn

~30 min
  • Work with an AI agent in plan mode to build a React application that integrates data from previous tools
  • Input an IP name and receive a go/no-go recommendation with reasoning
  • Display risk scores, estimated cost ranges, and source availability
  • Pre-load BloodRayne and 3-4 comparable IPs for instant analysis

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 Source Availability Scanner data — source status, community projects, engine info, rebuild difficulty rating
  • Deal structure recommendation: Embedded scoring from your Remake Deal Structure 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

Before you start

If your agent is still open from the previous lesson, exit that session first (/exit or Ctrl+D). Create a clean folder for this lesson and open it:

Terminal window
mkdir -p ~/retro-remake/04-remake-decider && cd ~/retro-remake/04-remake-decider

In Windows PowerShell:

Terminal window
mkdir ~/retro-remake/04-remake-decider; cd ~/retro-remake/04-remake-decider

Or open the folder directly in your desktop agent app. Start your agent the way Workbench Setup showed.

Switch to plan mode

Switch to Plan mode inside your session (Shift+Tab, /plan, or the mode picker) so the agent reviews your risk weights, unverified-status handling, and cost breakdown before writing code.

The conversation

Say what you want

Ask for the multi-source go/no-go decision dashboard in plain English:

I am choosing a retro IP to remake. Help me build an interactive web dashboard called remake-decider that combines source status, deal structure, risk scores, and cost ranges into a go/no-go verdict. Ask me what you need first.

Answer its questions

Guide the agent’s questions with the four pre-loaded IPs, risk weights, and gating rules:

If it asksYou might say
Which IPs should be pre-loaded in the database?BloodRayne, Legacy of Kain: Soul Reaver, Oni, and Darkwatch, with side-by-side comparison mode for 2 to 3 IPs.
What are the five risk scorecard dimensions and weights?Rights Complexity 25%, Source Availability 20%, Market Viability 20%, Development Difficulty 15%, and Financial Risk 20%.
How should an unverified (“unknown”) source status behave?Display “Unverified” on Source Availability and block the overall risk score and verdict until the source status is verified.
How are the total cost estimate and verdict bands calculated?Sum rights, $30K-$60K legal, 15% prototype, dev cost, and 10% QA; map risk score to Strong Go through No-Go.
What export and visual style should it include?A Markdown export button and a dark theme (#09090b background, #18181b cards) with purple accent #8B5CF6.
ℹReference notes to hand the agent (or check against)click to expand
  1. Pre-loaded IP Database (data/ips.js):

    • BloodRayne (2002, Third-person action, PS2/Xbox/GameCube/PC):
      • sourceStatus: "nothing" (No source code, no decompilation project, no mod SDK. Terminal Reality’s Infernal Engine has no public source release. Ziggurat made the Terminal Cut editions with Terminal Reality, but what source material either holds is not public, so this scenario assumes a clean-room rebuild.)
      • rightsHolder: "Ziggurat Interactive", rightsClarity: 7 (reported owner, derivative works scope unverified)
      • dealRecommendation: "License" (Ziggurat reportedly bought the BloodRayne rights in 2020; its appetite for licensing is unverified, so approach it first for a licensing or co-publishing conversation. Buying outright is unlikely if they want to retain the portfolio; revenue share is a possible fallback.)
      • estimatedRightsCost: $75,000-$200,000, estimatedDevCost: $300,000-$1,500,000
      • Scores: marketViability: 7, developmentDifficulty: 8, financialRisk: 6, brandStrength: 7
    • Legacy of Kain: Soul Reaver (1999, Action-adventure, PS1/Dreamcast/PC):
      • sourceStatus: "unknown" (A reported community decompilation project, unlinked; verify it exists before relying on it as a technical roadmap.)
      • rightsHolder: "Crystal Dynamics / Embracer Group", rightsClarity: 4 (the 2022 sale from Square Enix to Embracer changed studio ownership; verify current decision-makers before pursuing rights)
      • dealRecommendation: "Wait or Spiritual Successor"
      • estimatedRightsCost: $150,000-$500,000, estimatedDevCost: $200,000-$800,000
      • Scores: marketViability: 9, developmentDifficulty: 5, financialRisk: 7, brandStrength: 9
    • Oni (2001, Third-person action, PS2/Mac/PC):
      • sourceStatus: "decompilation" (Scenario assumption: partial source reconstruction; no public source reconstruction was found as of November 2026, kept so the four-way comparison has a partial-source case. The real community project, Oni Anniversary Edition at https://wiki.oni2.net/Anniversary_Edition, has maintained mods and patches for a retail copy for 20+ years; verify whether any source exists before relying on it.)
      • rightsHolder: "Take-Two (publishing) / Bungie (IP, unclear)", rightsClarity: 3 (historical rights split between Take-Two and Bungie, later acquired by Sony; verify current rights ownership before approaching either party)
      • dealRecommendation: "Spiritual Successor"
      • estimatedRightsCost: $200,000-$800,000, estimatedDevCost: $250,000-$900,000
      • Scores: marketViability: 5, developmentDifficulty: 6, financialRisk: 8, brandStrength: 4
    • Darkwatch (2005, First-person shooter, PS2/Xbox):
      • sourceStatus: "nothing" (No source code, no decompilation, no modding tools; High Moon Studios’ proprietary engine is closed; studio now part of Microsoft via Activision Blizzard King acquisition.)
      • rightsHolder: "Microsoft (via Activision Blizzard King acquisition of High Moon Studios)", rightsClarity: 2 (publishing split between Capcom NA and Ubisoft PAL adds territory complexity)
      • dealRecommendation: "Spiritual Successor"
      • estimatedRightsCost: $500,000-$2,000,000, estimatedDevCost: $400,000-$1,500,000
      • Scores: marketViability: 4, developmentDifficulty: 8, financialRisk: 9, brandStrength: 3
  2. Risk Scorecard & Verdict Rules:

    • 5 Risk Dimensions (1-10 scale): Rights Complexity (inverted from rightsClarity, weight 25%), Source Availability (nothing=9, mod-sdk=6, decompilation=4, official-release=1; unknown displays "Unverified" and blocks the overall score and verdict until verified; weight 20%), Market Viability (inverted, weight 20%), Development Difficulty (direct, weight 15%), Financial Risk (direct, weight 20%).
    • Cost Estimator: Rights acquisition + Legal counsel ($30K-$60K placeholder) + Prototype (15% of dev cost) + Full development (100% of dev cost) + QA and launch (10% of dev cost). For BloodRayne, total range is $480K-$2.135M.
    • Verdict Bands: 1-3 = "Strong Go" (green), 3.1-5 = "Conditional Go" (yellow), 5.1-7 = "Proceed with Caution" (orange), 7.1-10 = "No-Go" (red).

Read the plan

Before approving the agent’s plan, check four details:

  1. Unverified source blocks the verdict: When an IP’s sourceStatus is "unknown" (like Legacy of Kain: Soul Reaver), the scorecard shows "Unverified" and withholds the overall risk score and go/no-go verdict until verified.
  2. Weighted 5-dimension risk math: Rights Complexity (25%) and Market Viability (20%) invert their clarity/viability inputs so higher risk scores higher, alongside Source Availability (20%), Development Difficulty (15%), and Financial Risk (20%).
  3. Full cost breakdown: The Cost Estimator adds rights acquisition, $30K-$60K legal placeholder, 15% prototype, 100% full development, and 10% QA/launch ($480K-$2.135M total for BloodRayne).
  4. Side-by-side comparison and Markdown export: Users can compare 2-3 IPs side by side and download a full Markdown assessment for the selected IP.

If the plan computes a numeric risk score for "unknown" source status instead of blocking the verdict, steer it first:

When an IP has an unknown source status, display Unverified and withhold its overall risk score and verdict until verified.

Approve the plan once all four items are in place, and ask the agent to save a Git checkpoint after the app builds cleanly.

💡About the pre-loaded numbers

Every risk score, cost estimate, and deal recommendation is pre-calibrated to match the research from Lessons 1-3 so comparisons across the four IPs stay consistent.


What you get

After the AI finishes generating, the project folder structure looks like this:

REFERENCE PROJECT LAYOUT remake-decider/ generated React project folder tree open reference hide reference Reference example of the folder layout your agent creates. Open to inspect the components and data files; you do not create these files by hand.
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

Ask your agent to install what is needed and start the app:

Install everything needed, start the decision dashboard, and share the local URL so I can compare the IPs.

If you prefer to run the commands yourself in a terminal:

Terminal window
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 $480K-$2.135M total, and the verdict badge appears.

For BloodRayne, the supplied inputs produce “Proceed with Caution” — the brand strength and a publisher worth approaching create a viable path, but the lack of source code and the resulting development cost keep the score above the Conditional Go band.

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), but its source status shows “Unverified”, so the tool withholds its overall score and verdict; its post-2022 rights decision-makers also need verifying
  • BloodRayne has the clearest path to a deal (Ziggurat is worth approaching), 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 could be the stronger IP if its source status and rights chain check out, but you can’t plan a business around “if.”

If something is off

ProblemFollow-up prompt
Risk bars not renderingThe risk scorecard shows numbers, not visual bars. Add horizontal progress bars scaled from 1 to 10, colored green under 4, yellow from 4 to 6, and red over 6.
Comparison view only shows one IPIn comparison mode I can only pick one IP at a time. Let me select 2 or 3 IPs with checkboxes so their scores, costs, and verdicts appear side by side.
Cost estimates showing NaNThe cost estimator shows NaN instead of dollar ranges. Make sure rights and development costs are stored as numbers so the prototype, QA, and total cost math calculates cleanly.

Deep dive

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

  1. 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.

  2. The risk weighting is a planning default. 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 — a missing source can increase development effort substantially, and low market viability means even a perfect product might not sell.

  3. Pre-loaded data makes comparisons instant. The four IPs aren’t random — they represent four different scenarios: BloodRayne (a reported owner worth approaching, derivative-rights scope unverified, no source), Legacy of Kain (unclear rights, source availability unverified), Oni (tangled rights; partial source is this lesson’s scenario assumption, which the real community project does not provide), 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.

  4. 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.

  5. 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 ($480K-$2.135M 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 projectclick to expand

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, but its source status is unverified, so the tool withholds its score. But Legacy of Kain’s corporate ownership changed hands in the 2022 Square Enix to Embracer sale, and you can’t start a company on an unverified rights chain.

BloodRayne’s advantages are practical:

  • Ziggurat is worth approaching. It reportedly holds the rights (acquired 2020); whether it will license is unverified.
  • The cost range is indie-accessible. $75K-$200K (placeholder) 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 once you confirm current licensing contacts.


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 form for name, source status, rights holder, rights clarity (1-10), deal recommendation, cost ranges, and risk scores, saving new IPs to the dropdown in the browser.

Add a portfolio priority ranker

Add a Rank Portfolio button that scores all IPs in the database, ranks them from best opportunity to worst, and renders a stacked bar chart color-coded by the five risk dimensions.

Add a timeline simulator

Add a timeline view showing estimated months for rights negotiation, prototyping, full development, and QA/launch, extending negotiation or development duration based on the selected IP's rights and source risk scores.

What’s next

You now have the full decision stack: source availability, rights mapping, deal structure, and go/no-go recommendation. BloodRayne has a “Proceed with Caution” — the path is clear enough to pursue, with specific risks to manage first. 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 “Proceed with Caution” 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.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons