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

(Bug) SimpleAgent - Bombs itself on the 1st move #144

Closed
PixelyIon opened this issue Sep 7, 2018 · 5 comments
Closed

(Bug) SimpleAgent - Bombs itself on the 1st move #144

PixelyIon opened this issue Sep 7, 2018 · 5 comments

Comments

@PixelyIon
Copy link
Contributor

PixelyIon commented Sep 7, 2018

This behavior is extremely common when I'm collecting data from a vast variety of matches. However I cannot produce data of it due to saving in an unconventional format.

@suphoff
Copy link
Contributor

suphoff commented Sep 7, 2018

_directions_in_range_of_bomb looks sketchy

@cinjon
Copy link
Collaborator

cinjon commented Sep 18, 2018

What is the format that would be helpful for debugging this? Definitely interested in solving these kinds of concerns.

@suphoff
Copy link
Contributor

suphoff commented Sep 18, 2018

My working theory is that SimpleAgent regard the direction away from a bomb as a safe direction - then can't go far enough away from the bomb and backs itself into a dead end still in range of the bomb. Would just use Dijkstra's for bomb avoidance ...

@PixelyIon
Copy link
Contributor Author

What is the format that would be helpful for debugging this? Definitely interested in solving these kinds of concerns.

Write a while loop or something of the sort to run matches till it finds one that ends in less than 20 steps (A bit of leeway, just in case) and save that match as JSON. That should be enough to reproduce the bug.

@PixelyIon
Copy link
Contributor Author

Refer to #169 for further discussion.

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

3 participants