Separate bot retreat and destination edges #1084
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Not ready for prime time yet, need to fix failing unit tests. |
|
Fixed the unit tests, this should be ready to go. |
neoancient
approved these changes
Aug 10, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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