Product Brief: Unity Old-School Strategy Game PoC

Executive Summary

This deliberately small Unity fantasy strategy PoC tests one thesis before full game development: small, understandable production chains can make combat and quest decisions more meaningful when their outputs have immediate, visible tactical effects. Production is the implementation spine; combat proves whether its outputs matter, and quests create reasons to choose between immediate aggression and longer-term investment.

This is a learning product, not a vertical slice or commercial launch candidate. It must produce credible evidence about player enjoyment, strategic choice, and the creator’s appetite to continue.

Decision Rule

Continue toward a small standalone game only if most suitable testers can complete the chain without coaching, identify its combat benefit, perceive a meaningful aggression-versus-investment choice, and want another loop—and if creator iteration remains sustainable and motivating. Exact thresholds remain [ASSUMPTION] until an initial internal cohort establishes realistic baselines.

Who This Serves

The primary stakeholder is the solo creator, who is testing whether the game is enjoyable and tractable enough to continue. The primary test player enjoys readable old-school strategy, building economies, and gaining tactical advantage through preparation without requiring deep logistics simulation. Success means the player can complete and explain the loop while the creator can modify it quickly enough to learn.

Core Player Experience

The intended first playable loop is:

1. Place resource and processing buildings.
2. Watch resources accumulate in a clear global overview.
3. Select a recipe and inspect its requirements.
4. Start a timed craft with visible progress.
5. Receive a completion notification and find the item in inventory.
6. Equip or use the item, then observe its effect in combat or a quest.
7. Decide whether to invest in another production step or pursue immediate military progress.

The emotional arc should move from comprehension (“I know what this chain needs”) to anticipation (“my item is nearly ready”), agency (“I chose this investment”), and payoff (“that item changed what happened”).

Proof-of-Concept Scope

The PoC preserves three core elements: production chains, combat, and questing. Production is built first because it supplies the outputs that give the other two meaning.

In scope:

• Simple resource, processing, and crafting buildings.
• Passive resource generation and instantaneous magical transfer into a shared global pool.
• Recipe requirements, timed crafting, visible progress, completion feedback, and inventory.
• An iron sword chain: iron ore to ingots to steel blade, plus trees to planks to hilt.
• Tier-one leather armor upgraded with iron ingots into tier-two metal armor that visibly improves soldier survivability.
• Deer hunting as a leather source, linking armor and morale production to one economy.
• A morale flag crafted from leather and one plank, with a visible area of effect and duration; it disappears without salvage when it expires.
• A fantasy combat sandbox with at least a melee hero, a spellcasting hero, regular soldiers, and monsters.
• Monster-dropped scrolls that teach heroes skills they can equip.
• One or two quests that support offensive and defensive approaches and reinforce the chosen play style.
• Progression that reuses earlier resources or crafted outputs rather than making them immediately obsolete.

Explicitly out of scope:

• Workers, warehouses, transport routes, and fuller logistics.
• Automation, large-scale throughput optimization, and complex production networks.
• Profession ranks or gathering restrictions.
• Magical armor production, enchantment systems, deep combat statistics, or expanded morale penalties.
• Content breadth, polished art, extensive animation, multiplayer, and commercial-launch systems.

Implementation guardrails: start with small chains, prefer readable feedback over polish, keep the shared pool, make morale a positive reward, reuse early materials in later recipes, and treat explainable failed experiments as useful evidence.

Strategic Choice to Validate

Players should face a legible tradeoff rather than a solved build order:

• Aggressive play invests in early troops, exploration, offensive quests, loot, and immediate combat power.
• Production-focused play invests in essential chains, resource growth, defensive quests, and delayed military advantage through better equipment.

Neither style should be universally correct. Quest rewards should strengthen the chosen approach, and production should offer more than one useful destination: heroes, regular units, defenses, or tactical structures. The PoC only needs enough content to reveal whether this tension feels genuine.

Validation Plan

Begin with creator playthroughs, then—if a stable loop exists—run approximately 5–10 observed think-aloud sessions with suitable strategy players. Record lightweight telemetry only when it informs a decision; Unity supports custom events and funnels for analyzing design intent and drop-off in its Analytics documentation.

Collect evidence in five areas:

• Loop clarity: Can testers move from building placement through crafting and item use without coaching? Where do they hesitate, abandon, or require help?
• Payoff causality: Can they explain what the sword, armor, or flag changed? Do combat outcomes, losses, time-to-win, or hero survival visibly differ?
• Strategic choice: Do first investments and quest choices vary for understandable reasons, or does one sequence dominate?
• Desire to continue: After one full loop, do testers voluntarily want another chain or scenario? Why or why not?
• Creator viability: Is iteration time acceptable, does each system yield useful learning, and does building the production spine remain motivating?

If the PoC Succeeds

The next step is a small standalone fantasy strategy game centered on production choices that visibly shape combat and quest outcomes. Only after proving that payoff should the design expand. Its identity should remain compact and consequence-rich rather than chase the scale of larger settlement games.