Repository navigation
MakaMek MVP PRD
github-actions[bot] edited this page May 27, 2026
·
1 revision
MakaMek is a cross-platform implementation of the classic BattleTech tabletop game. The MVP is targeting simplified 3025-era combat mechanics and focuses on core turn-based tactical combat featuring BattleMechs on hex-based maps with essential game mechanics including movement, combat, heat management, and critical damage systems.
Primary Objectives:
- Deliver a playable BattleTech experience with simplified rules (Level 1)
- Support cross-platform deployment (Desktop, Web, Mobile)
- Provide multiplayer capabilities (local and LAN)
- Maintain compatibility with standard BattleTech community data formats (MTF)
Scope: Single-player and multiplayer tactical combat with up to 4 players using bipedal BattleMechs on hex maps with basic terrain types.
- Turn-based gameplay
-
Phase-based turn structure:
- Initiative Phase
- Movement Phase
- Weapon Attack Phase
- Heat Phase
- End Phase
- Victory conditions: Eliminate all opposing BattleMechs
- Light 'Mechs: 20-35 tons (reconnaissance, speed)
- Medium 'Mechs: 40-55 tons (workhorses, core units)
- Heavy 'Mechs: 60-75 tons (commanders, damage dealers)
- Assault 'Mechs: 80-100 tons (battlefield dominance)
- Chassis type: Bipedal only (no quad 'Mechs in MVP)
- Piloting Skill: Controls movement and fall avoidance (lower = better)
- Gunnery Skill: Controls weapon accuracy (lower = better)
- Health: 5 damage points maximum (6th point is fatal)
- Hex grid: 6-sided hexagons representing 30m areas
- Coordinate system: Standard hex addressing
- Clear Terrain: No movement penalty, no cover
- Light Woods: +1 MP cost, +1 to-hit modifier, line of sight allowed
- Heavy Woods: +2 MP cost, +2 to-hit modifier, provides cover
- Walking: Standard movement, +1 to-hit modifier when attacking
- Running: Increased speed, +2 to-hit modifier when attacking
- Jumping: Ignore terrain penalties, +3 to-hit modifier when attacking
- Standing Still: No movement, +0 to-hit modifier
- Movement Points (MP): 1 MP per hex entered
- Terrain costs: Clear (+0), Light Woods (+1), Heavy Woods (+2)
- Facing changes: 1 MP per 60-degree turn
- Target Movement Modifier (TMM): Based on hexes moved (0-2: +0, 3-4: +1, 5-6: +2, etc.)
- Triggers: Heavy damage (20+ points), gyro hits, leg actuator damage
- Modifiers: Gyro hit (+3), gyro destroyed (+6), leg actuator hit (+1), heavy damage (+1)
- Failure consequences: 'Mech falls, takes damage, MechWarrior may be injured
- Declaration phase: All attacks declared before resolution
- Line of Sight (LOS): Required between attacker and target
- Firing arcs: Forward, Left Side, Right Side, Rear
- Torso twist: Allows shifting upper body firing arc
- Base number: Attacker's Gunnery Skill
-
Cumulative modifiers:
- Attacker movement: Walk (+1), Run (+2), Jump (+3)
- Target movement: Based on hexes moved
- Range: Short (+0), Medium (+2), Long (+4)
- Minimum range: Penalty if within weapon minimum
- Terrain: Light woods (+1), Heavy woods (+2)
- Heat effects: Various penalties at different heat levels
- Hit location tables: 2D6 roll determines hit location by attack direction
- Damage resolution: Armor first, then internal structure
- Damage transfer: From destroyed locations to adjacent areas
- Critical hits: When internal structure damaged, roll for component damage
- Aimed shots: Ability to aim a specific target location of immobile units
- Cockpit: Destroys 'Mech, kills MechWarrior
- Engine: 3 hits destroy 'Mech, each hit increases heat
- Gyro: Adds PSR modifiers, destroyed = automatic fall + immobile
- Heat sinks: Each hit reduces heat dissipation
- Sensors: Adds to-hit penalties, 2 hits prevent weapon fire
- Movement heat: Walk (+1), Run (+2), Jump (+3 minimum or MP spent)
- Weapon heat: Variable per weapon type
- Heat tracking: On 'Mech record sheet heat scale
- Movement penalties: Reduced Walking MP at heat levels 5, 10, 15, 20, 25
- Weapon penalties: To-hit modifiers at heat levels 8, 13, 17 and 24
- Shutdown risks: Automatic shutdown attempts at heat 14, 18, 22, 26, 30
- Ammunition explosions: Risk at heat 19, 23, 28
- MechWarrior damage: If life support hit, damage at heat 15+
- MechWarrior death: Any cause
- Engine destruction: 3 critical hits
- Location/component destruction: Head/cockpit, or center torso destroyed
- .NET 9
- Client-Server architecture with reactive communication
- Cross-platform UI using AvaloniaUI
- Modular design separating Core, Presentation, and UI layers
- Desktop: Windows, Linux, macOS
- Web: WebAssembly (WASM)
- Mobile: Android, iOS
- Local play: Single device, up to 4 players
- LAN multiplayer: SignalR communication
- 'Mech definitions: MTF (MegaMek) format compatibility
- Game state: JSON serialization
- Map data: Custom format with MegaMek asset compatibility
- Initiative Phase: 2D6 roll determines turn order
- Movement Phase: Alternating movement with proper MP costs
- Attack Phase: Weapon targeting and to-hit calculation
- Heat Phase: Heat accumulation and effect application
- End Phase: Turn cleanup and victory condition checks
- GATOR system: Accurate to-hit calculation with all modifiers
- Hit location: Proper 2D6 tables for front/side/rear attacks
- Critical hits: Component damage with correct effects
- Damage transfer: Proper armor/structure/location destruction
- Terrain costs: Correct MP expenditure for terrain types
- Piloting rolls: Triggered by appropriate conditions
- Fall mechanics: Damage calculation and facing changes
- Jump mechanics: Proper heat and to-hit effects
- Heat tracking: Accurate accumulation from movement/weapons
- Performance effects: Movement/accuracy penalties at thresholds
- Shutdown mechanics: Automatic attempts at heat levels
- Critical effects: Ammunition/life support interactions
- Core game phases and turn structure
- Basic movement (walk/run) with terrain costs
- Weapon attack resolution with GATOR system
- Heat generation and basic effects
- Hit location and damage resolution
- Critical hit system for major components
- Victory/defeat conditions
- Jump movement mechanics
- Piloting skill rolls and fall system
- Advanced heat effects (shutdown, ammo explosion)
- Torso twist mechanics
- Multiple terrain types
- LAN multiplayer support
- Advanced critical hit effects
- Detailed component damage modeling
- Enhanced UI/UX features
- Additional 'Mech variants
- AvaloniaUI framework for cross-platform UI
- SignalR for multiplayer communication
- .NET 9 runtime availability on target platforms
- MTF format specification for 'Mech data
- Players familiar with basic BattleTech concepts
- Simplified rules sufficient for engaging gameplay
- Cross-platform deployment feasible with chosen tech stack
- Performance acceptable on mobile devices
- BattleTech IP usage within fair use/fan project guidelines
- Community 'Mech data availability in MTF format
- Asset compatibility with MegaMek resources
- Game completion rate: >90% of started games reach victory condition
- Rule accuracy: compliance with specified BattleTech mechanics
- Cross-platform compatibility: Successful deployment on all target platforms
- Multiplayer stability: <1% disconnection rate in LAN games
This PRD serves as the foundation for implementing the MakaMek MVP, providing clear requirements for an LLM-based AI agent to understand scope, prioritize features, and generate specific implementation plans.