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

[0.50.03-SNAPSHOT] Princess AI not closing in to engage and maintaining blocked LOS against inferior/equal forces #6473

Open
4 tasks done
PhoenixHeart512 opened this issue Jan 31, 2025 · 0 comments

Comments

@PhoenixHeart512
Copy link

Brief Description *

In this scenario, I have 2 tanks and 1 VTOL (arguably maybe the second) in engagement range of the 4 enemy mechs on the west half of the map. The enemy mechs are primarily close range brawler loadouts, and Princess is not moving them forward to engage, and instead just standing behind buildings to block LOS and avoid getting shot at.

Even with the Berserker v2 AI preset this is occurring. When I tested moving the aggression slider all the way to the left (in case they were reversed again) she full retreated back to her board edge and grouped up behind buildings.

Berserker v2 with Pangar mortar and enemy quickdraw not yet moved:

Image

With Pangar and quickdraw moved:

Image

With sliders set fully to Meek:

Image

3. Steps to Reproduce

In the attached save, the order I moved my units in as the test case is:

  1. Demolisher II -> Flank to 2616
  2. Kelswa ->Flank to 2616
  3. Pangar IS-Ph Mk II -> Flank to 1319
  4. Pangar IS-Ph Mk III Mortar -> Flank to 1319
  5. Press "next player" to force allied AI to move all units

Attached screenshots are movement results with my 2 VTOL's not yet moved

Attach Files

Gunshy Princess.zip

Severity *

High (Major Disruption): A major feature is broken or incorrect, but a workaround exists.

MegaMek Suite Version *

MegaMek v0.50.03-SNAPSHOT Build Date: 2025-01-31T03:18:49.847656595

Operating System *

Windows 10

Java Version *

Java Vendor: Eclipse Adoptium Java Version: 17.0.6

Final Verification

  • I confirm this is a single, unique issue that hasn't been reported before
  • I have included all necessary information and files to help reproduce this issue
  • I have asked on MegaMek Discord about this issue
  • I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ
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

No branches or pull requests

1 participant