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
Fix validation to handle double respawn edge case #5
Conversation
If you mean two moves for "A", this is incorrect. "A" will have only one move in the second maze (that is moving down). "A" is still in the re-spawn zone so it cannot move up. Please let me know if I'm misinterpreting. |
When both bots are on the respawn point, moving up or down into the empty squares treated as invalid. The maze on the left is the input that the bot is sent. |
Hey guys, I'm also having trouble with this bug, especially when playing my bot against itself. Will this change make it into the final version? |
Hi, I have looked at it again, it seems that you're under the impression that it is the responsibility of the bot to regenerate B if it doesn't exist? The test harness will handle this if you move from the centre and leave the centre blank. |
Hi, I've confirmed that this is working as expected. You will not need to generate the opponent bot. You simply move "A" up or down, and the test harness will generate the opponent bot in the next turn. Please let me know if you come right so that I can close this issue. |
It doesn't work. Validation fails on the 5th move i.e.
The input that the bot gets from the harness on that turn is
and not
|
I'm rage quitting the challenge this year so this isn't an issue for me anymore. |
No you can't quit! Eish, is still a problem. Sad to see you go dude. Entellect, please don't ignore this log, it will still result in a valid move being declared invalid. |
This issue has been resolved. |
The harness incorrectly validates the situtation where both bots are on the respawn point.
(This situation can happen when the bots respawn on consecutive turns.)
This is what it can look like from a bot's prespective.
Currenlty the harness regards the only two valid moves as invalid.
This pull request fixes that.