market research 2026 q1
Guide for market research 2026 q1
Market Research Synthesis: Q1 2026 MMORPG Gamer Survey
Survey Date: January 2026
GPM Analysis Date: 2026-01-18
Document Type: Strategic Product Decision Document
Executive Summary
Related: See ip_strategy.md for detailed Trademark & Copyright protection strategy.
Survey data reveals a core tension between two player archetypes:
- "The Purists" — Value the journey, manual effort, and social friction
- "The Modernists" — Value efficiency, lifestyle integration, and convenience
Key Finding: High resistance to "Auto-play" but clear appetite for "Management-style" progression.
🔴 Critical Product Risks
1. The "Desolate World" Paradox
CAUTION If players can progress without being "in-world," the social fabric that makes MMORPGs sticky will collapse. This is an existential risk.
2. Terminology Toxicity
Terms that trigger immediate rejection from the core MMORPG audience:
- ❌ "AFK" — Implies disengagement
- ❌ "Passive" — Implies low-skill/no-effort
- ❌ "Auto-play" — Implies mobile gacha/botting
- ❌ "Grinding" — Negative connotation despite being acceptable mechanic
Approved Rebrand Terminology:
3. The "Clone" Label
WARNING Users are already identifying the mechanical loop as "Literally RuneScape," which risks devaluing the Nandaka Interactive IP.
Differentiation Requirements:
- Astra System must be functionally distinct, not just a reskin
- Deity Boons must grant Active-Only buffs during specific windows
- Visual Fidelity must contrast against low-poly competition
- Vedic Mythology must be mechanical, not cosmetic
4. Mobile Control Frustration
✅ Strategic Decisions (GPM Directives)
Decision 1: Mobile Companion App (Full-Featured)
Directive: Mobile app provides full gameplay option with optimized management features.
Core Philosophy: Player's choice. If they want to manage, they manage. If they want to play, they play.
Implementation:
Key Differentiator:
Mobile players can interact with Citizens' Exchange without physically traveling to the location. This is a lifestyle convenience feature while PC players would travel in-world.
Technical Sync (Online Mode Only):
- Real-time state sync via WebSocket
- REST API fallback for low-connectivity
- Exclusive Sessions: If logged in on PC, cannot log in on mobile (and vice versa). One device at a time.
IMPORTANT Offline vs Online Profiles: The offline gaming profile has nothing to do with the online account. They are completely separate game states. Offline profiles are local-only saves with no server sync or connection to online accounts.
Decision 2: Tapasya System (Conversion + Drop Trade-offs)
Directive: Each method has unique advantages. Active is efficient, AFK yields more Bijas.
Reference: Implementation intapasya.rs
Sphatika → Bija Conversion:
Equipment Effects:
NOTE AFK mode yield is affected by equipment tier (bonus_yield based on multiplier), and higher tiers increase the speed of conversion (chance to reduce ticks).
Drop Rate Bonuses:
Trade-off Summary:
Design Rationale:
- Active = Speed + Scrolls — Grinders get faster XP and better scroll odds
- AFK = Bijas + Weapons — Passive players get more Bijas per Sphatika + weapon lottery
- Equipment matters — Tier progression affects both modes
Decision 3: Active-Only Milestones (Expansion)
Directive: Major progression gates cannot be achieved through Tapasya or passive means.
🏛️ Astra Unlocks
Unlocked via deity-specific Trials (e.g., Trial of Flame).
🦅 Skill Cloaks (Level 99)
Directive: Level 99 capes must offer special benefits and QoL (e.g., ammo saving, teleportation), not just cosmetics.
Future Research (Pinned)
Note: The following concepts (Zone Unlocks, Social Milestones, Visual Badges) are "pinned" for future research as they are currently too farfetched or don't fit the current vision.
- Zone Unlocks: Region-locking based on active play.
- Social Milestones: Mandatory grouping requirements.
- Visual Badges: Prestige icons.
- Lore Reveals: Major story beats, cutscenes, sacred texts.
Decision 4: Brand Language Overhaul (Full Glossary)
Directive: Replace ALL Western MMO/mobile terminology with Vedic-themed alternatives that emphasize player agency and discipline.
Complete Terminology Mapping
Progression Language
Combat Language
Economy Language
UI/UX Language
Marketing Copy Transformations
Before → After Examples:
- "Train skills while AFK!"
+ "Set your Tapasya discipline. The gods observe your dedication."
- "Passive income while you sleep"
+ "Your Ashram generates yields even as you rest."
- "Daily login rewards"
+ "Receive your Dawn Blessing at the temple each sunrise."
- "Grind to level 99"
+ "Walk the path of Sadhana to mastery."
- "Auto-combat makes it easy"
+ [NEVER SAY THIS - DELETE FROM ALL COPY]Decision 5: Astra Combat System (Full Specification)
Directive: Astras are divine projectiles fired from Greatbows, creating a unique hybrid combat system.
Acquisition
IMPORTANT Astras are rare drops, obtainable through Tapasya (skilling) activities.
Mechanics & Restrictions
Stat Scaling (Hybrid)
Astra Damage = Base_Damage × (Magic_Level × 0.5 + Ranged_Level × 0.5) × Greatbow_ModifierDesign Rationale: Forces hybrid builds, differentiates from pure Ranged or pure Magic playstyles.
Combat Interface
┌─────────────────────────────────────────────────────────┐
│ COMBAT HUD │
├─────────────────────────────────────────────────────────┤
│ [Greatbow Equipped] │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Agneya │ │ Varuna │ │ Brahma │ │ Pashupa │ │
│ │ 🔥 x12 │ │ 💧 x8 │ │ ✨ x3 │ │ 💀 x1 │ │
│ └─────────┘ └─────────┘ └─────────┘ └─────────┘ │
│ ↑ Selected Astra │
│ │
│ [Between combat ticks: Open Mantra Book to switch] │
└─────────────────────────────────────────────────────────┘Astra Selection
Bija Requirements
Reference: Official Bija types frommantras.json
Available Bija Types
Astra Bija Costs
WARNING Astras are incredibly powerful (nuclear option). Costs are massive (~150 Bijas/shot).
Greatbow Tiers
Visual & Audio Distinction
📊 Technical Validation Requirements
Priority 1: Astra Combat Demo (Engine: Bevy/Rust)
Objective: Prove tactical depth with hybrid Magic/Ranged + Greatbow system.
Deliverables:
- Prototype 3 Astras (Agneyastra, Varunastra, Brahmastra)
- Greatbow equip requirement enforcement
- Bija consumption system
- Mantra Book UI for mid-combat switching
- Hybrid stat scaling implementation
- Video capture for marketing materials
Success Criteria:
- Players must make meaningful choices about which Astra to use
- Combat feels distinct from "just Ranged/just Magic"
- Cannot be described as "just like RuneScape special attacks"
Priority 2: Tapasya Altar System
Objective: Implement 5-minute decay cycle with re-engagement requirement.
Deliverables:
- Altar interaction system
- Decay timer (25% → 1% over 5 minutes)
- Re-click to reset mechanic
- Visual/audio feedback for decay warning
- Server-side rate enforcement (no client manipulation)
Priority 3: Anti-Botting Infrastructure
Objective: Server-side verification for all Tapasya/passive loops.
Deliverables:
- Rate limiting on all XP gain endpoints
- Heuristic detection for inhuman patterns
- Session token rotation during passive gains
- Economy monitoring dashboard (already in progress: Mission OPS-CONTENT)
Success Criteria: Economy team can detect and flag anomalous gold/XP generation within 10 minutes.
Priority 4: Mobile Companion App
Objective: Full-featured mobile client with Citizens' Exchange remote access.
Deliverables:
- Full gameplay client (React Native / Flutter / Unity)
- Citizens' Exchange remote access (no travel required)
- Touch-optimized UI for management features
- Real-time sync with PC client
- Seamless session handoff
Priority 5: Social Hub Architecture
Objective: Physical Markets to prevent "desolate world" feeling.
Proposed Hubs:
Design Rule: Banking, high-value trades, and GE collection require physical presence in-world (on PC). Mobile gets remote access as lifestyle convenience.
🎯 Integration with Current Roadmap
Immediate Actions (Next Sprint)
- Update Mission WORLD-ACHIEVEMENTS:
- Add "Tapasya Altar System" with 5-minute decay mechanics
- Add "Active-Only Milestone" gates to Achievement Diaries
- Create New Mission: MOBILE-COMPANION:
- Scope: Full gameplay + management mobile app
- Tech: React Native or Flutter or Unity Mobile
- Priority: Medium (after core combat loop)
- Create New Mission: ASTRA-COMBAT:
- Scope: Full Astra system implementation
- Include Greatbow requirement, Bija costs, hybrid scaling
- Priority: High (core differentiation)
- Create New Mission: ANTI-BOT-INFRASTRUCTURE:
- Server-side rate limiting
- Heuristic detection system
- Economy anomaly alerting (builds on ITEM-INTEGRITY)
Terminology Updates Required
Update all player-facing documentation:
-
knowledge-base/onboarding.md— Replace "AFK" terminology -
loh-website/— Marketing copy refresh -
loh-data/dialogues/— NPC dialogue audit for terminology
📈 Success Metrics
Appendix: Survey Direct Quotes
"If I can progress without logging in, why would I ever log in? The world will be empty."
"Auto-play is for trash mobile games. Don't make this a garbage phone game."
"RuneScape but Indian. Okay, but what's actually different?"
"I would manage my bank on my phone. I would never fight on my phone."
"The journey IS the game. If I skip to the end, I didn't play."
Document prepared by GPM Agent. Approved by Product Lead 2026-01-18.