[RFE] House Commands for StratCon.

[HammerGS]

Prerequisites and Pre-Issue Checklist

• [X] I'm reporting the RFE to the correct repository:

• MegaMek

• MegaMekLab

• MekHQ

• [X] Does this conform with our Content Policy linked above?

• [X] I've searched the GitHub tracker and haven't found a similar feature request listed

RFE Details *

This is a new feature

Brief Description *

This RFE is meant as a Framework for a future House Command model. This Framework is NOT final and only meant as a starting point. The Dev team has no timeline for implementation for this, but felt it was time to centralize the discussions. We'll also be opening a discussion channel on the Discord for this.

House Commands Implementation

Orders System

The contract market needs rework for House Commands. Players see one mission representing their orders instead of choosing from multiple contracts.

Core Changes

• One mission at a time in contract market:

  • Represents direct orders from House command
  • Must be structured with House as employer
  • Can't be refused without penalty
  • Uses existing mission generation system

• Opponents and missions:

  • Pulled from faction_hints.xml for logical opponents
  • Matches current House conflicts and relationships
  • Ensures realistic strategic objectives
  • No inappropriate or illogical matchups

• Unit quality impacts:

  • Elite units get 2-3 mission choices
  • Green units limited to single option
  • No mismatched fights (prevents elite vs green)
  • Mission difficulty matches unit experience

• Battalion+ sized units:

  • Multiple scenarios per mission
  • Commanders allocate forces across objectives
  • Each scenario contributes to overall success
  • Uses existing scenario connection system

Victory Points

Binary system that tracks unit success:

• Win = +1 point:

  • Complete mission objectives
  • Hold ground in defensive operations
  • Achieve strategic goals

• Draw = 0 points:

  • Partial mission success
  • Mutual withdrawal
  • Incomplete objectives

• Loss = -1 point:

  • Mission failure
  • Forced withdrawal
  • Refusing orders (automatic loss)
  • Major unit casualties

Logistics

House Commands receive supplies through House logistics rather than purchasing them.

Monthly Supply

• Automated delivery system:

  • Uses new logistics tools
  • Monthly schedule
  • No direct financial management
  • Represents House support structure

• Quality and quantity based on:

  • Unit's current performance
  • Victory point totals
  • Active mission status
  • Current operational needs

Salvage

• Roll-based retention system:

  • Higher victory points improve chances
  • Elite units get better odds
  • All equipment types use same roll
  • No automatic House claims

• Unit equipment handling:

  • Own damaged/destroyed units always stay
  • Captured equipment needs retention roll
  • No compensation for House-claimed salvage
  • Standard repair rules apply

Emergency Supply

• Request system:

  • Uses commander's Admin/Command skill
  • Success brings additional supplies
  • Failure means waiting for monthly delivery
  • Simple check system

• Victory point influence:

  • More points = more request chances
  • Better units get more flexibility
  • Winning record improves odds
  • Player feedback needed for exact thresholds

Personnel

Getting New Personnel

House Commands use two recruitment methods:

• Command Request:

  • Admin/Command skill check required
  • Difficulty scales with personnel quality
  • Elite personnel need highest difficulty checks
  • Failed request cooldown (needs player feedback)

• Victory Point Expenditure:

  • Guaranteed personnel acquisition
  • No skill check needed
  • Works for any quality level
  • Costs based on personnel value

Combat Replacements

Quality system based on unit status:

• During active missions:

  • Highly randomized quality
  • Wider variance in capabilities
  • Immediate combat replacements
  • Specialist positions follow same rules

• Between missions:

  • Quality matches unit level (+/- one step)
  • More consistent replacement level
  • Standard integration time
  • Better control over quality

• Victory point influence:

  • Higher points improve replacement quality
  • Low points reduce average quality
  • Losing units get lower quality replacements
  • Winning record brings better personnel

Transfers

Uses existing systems with modifications:

• Standard retirement system handles transfers
• Victory points reduce unwanted transfers
• Regular personnel turnover continues
• Normal retention mechanics apply

Garrison Duty

Units serve garrison duty between active missions.

Basic System

• Random location assignment:

  • Any House-controlled world
  • No distance restrictions
  • Immediate transfer after mission
  • Represents standard military rotation

• Uses existing garrison mechanics:

  • Standard garrison contract system
  • Full range of possible events
  • Can be quiet or heavy combat
  • Normal risk generation

Duration Control

• Time limits:

  • Minimum: 3 months
  • Maximum: 18 months
  • No extensions beyond maximum
  • Early release possible

• Monthly check for early release:

  • Based on commander's skill
  • Unit's current rating matters
  • Reputation affects chances
  • Victory points influence odds

Technical Implementation

Primary system modifications needed:

1. Contract market adaptation for orders
2. Integration with logistics tools
3. Personnel system modifications
4. Garrison duty rotation system
5. Victory point tracking and effects

Player Feedback Requirements

Need testing to determine:

• Victory point thresholds
• Garrison duty timing
• Combat replacement delays
• Request system limits
• Mission frequency balance

MekHQ Suite Version *

v0.50.01

Attach Files

No response

Final Checklist

• [X] I've checked to make sure that this RFE has not already been filed
• [X] I am requesting implementation of only one relevant set of features in this ticket for clarity and focus

[repligator]

Would this apply to Clans as well?

[IllianiCBT]

My gut tells me to implement for IS factions, then Clans, then ComStar / WoB.

We’d probably see some cross utility, but past modules have taught me not to try and tackle everything at once.