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

Separate bot retreat and destination edges #1084

Merged

Conversation

@NickAragua
Copy link
Member

commented Aug 8, 2018

Configuration options (and actual behavior) that allows the bot to have a separate destination edge (for chase scenarios and such), and a retreat edge (when retreating under forced withdrawal rules).

"None" for the destination edge means the bot will follow its standard behavior of engaging the player on the board.

"Nearest" for the retreat edge means that the bot will evaluate each crippled unit's position and attempt to move towards the nearest board edge.

Companion changes to MekHQ will follow.

https://imgur.com/2oqVmud

@NickAragua

This comment has been minimized.

Copy link
Member Author

commented Aug 8, 2018

Not ready for prime time yet, need to fix failing unit tests.

@NickAragua

This comment has been minimized.

Copy link
Member Author

commented Aug 9, 2018

Fixed the unit tests, this should be ready to go.

@NickAragua NickAragua merged commit 0524848 into MegaMek:master Aug 11, 2018
@NickAragua NickAragua deleted the NickAragua:separte_bot_retreat_and_destination_edges branch Aug 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.