Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Balance] [AtB/StratCon] Base Attack (Defender) Objective Changes #3889

Merged
merged 1 commit into from
Mar 23, 2024

Conversation

IllianiCBT
Copy link
Collaborator

@IllianiCBT IllianiCBT commented Mar 18, 2024

Current Implementation

Currently, when the players' base comes under attack (usually due to a difficult contract) they are presented with a special scenario. The failure of which results in a Contract Defeat.

Current objectives task players with keeping allied units alive, including their own. For each allied unit that is defeated the contract Victory Points (not Scenario) are reduced by 1. As allied losses are inevitable, contract loss is almost a given, even if the player plays well.

Modification

This patch removes the Victory Point loss from allied defeats, but leaves all other objectives untouched. These are as follows:

  • Ensure that at least 3 base units (turrets/civilians) survive
  • Destroy, cripple or force the withdrawal of at least 50% of opposing forces
  • Ensure that at least 50% of friendly forces survive

This still leaves margin for defeat, but removes the likelihood of suffering a 'failure in victory'.

Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 10.64%. Comparing base (fbbf4d8) to head (1f9b789).

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #3889   +/-   ##
=========================================
  Coverage     10.64%   10.64%           
  Complexity     5487     5487           
=========================================
  Files           834      834           
  Lines        113856   113853    -3     
  Branches      17193    17192    -1     
=========================================
  Hits          12119    12119           
+ Misses       100528   100525    -3     
  Partials       1209     1209           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@HammerGS
Copy link
Member

Given our crazy implementation of turrets, and based on what I see in conversations on the Discord. I wonder if turrets should be modified in someway.

@IllianiCBT
Copy link
Collaborator Author

Given our crazy implementation of turrets, and based on what I see in conversations on the Discord. I wonder if turrets should be modified in someway.

As it stands, I believe the 'turrets need to survive' victory condition exists as a way to determine whether the base itself has been destroyed.

Changing that victory condition wouldn't be hard, though. Did you have something in mind?

@HammerGS
Copy link
Member

I would suggest taking the victory conditions conversation to the Discord, and see if the community has any ideas. Full support the PR in it's current form but wondering if more expansive options should be discussed.

@IllianiCBT
Copy link
Collaborator Author

Discussed it with Discord. I'm going to keep this patch as is - leaving turrets alone. With a mind to revisiting them later, once potential turret RAT changes (from Thom) have a bit of play time. My thinking is that if the turret RAT is improved, it would remove the need for the civilian units and would improve overall scenario play-feel without the need for further Victory Condition changes.

If Thom's RAT change isn't accepted, I'll do another balance PR.

@HammerGS
Copy link
Member

After the chat on Discord, I don't see any issues with the Turret RAT frequencies being tweaked.

@HammerGS HammerGS merged commit ec0731d into MegaMek:master Mar 23, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants