Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Scoppio
Copy link
Collaborator

@Scoppio Scoppio commented Jan 15, 2025

Experiment - using ACAR to resolve refused scenarios.

If there is team 1 in the scenario in the form of attached allies, it will run a game and see what happens, otherwise it follows the normal ways.

@Scoppio Scoppio self-assigned this Jan 15, 2025
@Scoppio Scoppio requested a review from IllianiBird January 15, 2025 22:16
@Scoppio Scoppio added StratCon Bugs relating strictly to StratCon ACAR Any Issues related to the ACAR (Abstract Combat Auto Resolve) System labels Jan 15, 2025
Copy link
Collaborator

@IllianiBird IllianiBird left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks fine, insofar as I can see. Just some minor suggested changes.

I do have a question, though: how many iterations of ACAR do we run here to get our result; just the one, or is it defined by the campaign option?

public Color getBelowContractMinimumForeground() {
return new Color(userPreferences.node(MHQConstants.DISPLAY_NODE)
.getInt(MHQConstants.BELOW_CONTRACT_MINIMUM_FOREGROUND, Color.RED.getRGB()));
.getInt(MHQConstants.BELOW_CONTRACT_MINIMUM_FOREGROUND, CRIMSON_RED.getRGB()));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're updating this, it would be better to use the negative or warning event color, so users can configure it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe, but I dont know what you are referencing here

if (stub) {
if (getCampaignOptions().isUseStratCon() && (scenario instanceof AtBDynamicScenario atBDynamicScenario)) {

// if (processIgnoredScenario(atBDynamicScenario, contract.getStratconCampaignState())) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're confident we're making this move, we probably want to remove the code rather than commenting it out.

if (scenario.isTurningPoint()) {
campaignState.updateVictoryPoints(-1);
}
// this is already processed in the simulateTheResultsOfIgnoredScenario
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, too. If we're removing this functionality let's remove the dead code instead of just commenting it out.

@Scoppio Scoppio marked this pull request as draft January 16, 2025 02:34
@Scoppio
Copy link
Collaborator Author

Scoppio commented Jan 16, 2025

Everything looks fine, insofar as I can see. Just some minor suggested changes.

I do have a question, though: how many iterations of ACAR do we run here to get our result; just the one, or is it defined by the campaign option?

It would run ACAR for each refused scenario, I would still add a campaign option for it to be activated (I guess people could dislike the fact that the auto resolve is a homebrew system).

For some reason it went up as a normal PR and not as a draft, its not by any means ready, so there is some things missing that I want to add before calling that a feature.

@codecov-commenter
Copy link

codecov-commenter commented Jan 17, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@3a5530c). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5792   +/-   ##
=======================================
  Coverage        ?   10.29%           
  Complexity      ?     6124           
=======================================
  Files           ?     1038           
  Lines           ?   139120           
  Branches        ?    20600           
=======================================
  Hits            ?    14327           
  Misses          ?   123398           
  Partials        ?     1395           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Scoppio
Copy link
Collaborator Author

Scoppio commented Jan 20, 2025

I will leave this PR open as a Draft. It is small enough that can be picked up again in the future, however it has too many small problems, and I don't know how it can "actually" give anything to us unless we have persistent OpFor. Otherwise it will be as random as just disappearing with a scenario by rolling a dice

@HammerGS HammerGS added the Draft Work in Progress label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ACAR Any Issues related to the ACAR (Abstract Combat Auto Resolve) System Draft Work in Progress StratCon Bugs relating strictly to StratCon

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants