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

Error in game Gotcha - Player 1 always wins #14

Open
Exodia7 opened this issue Jun 25, 2021 · 0 comments
Open

Error in game Gotcha - Player 1 always wins #14

Exodia7 opened this issue Jun 25, 2021 · 0 comments

Comments

@Exodia7
Copy link
Contributor

Exodia7 commented Jun 25, 2021

Good late afternoon,

I spent a lot of time working with the GVGAI framework, specifically the 2-player track, and noticed something weird about the game Gotcha while testing it out by playing myself:
It seems like player 0 can never win the game. From the game itself and having a look at the rules of the games (i.e. file examples/2player/gotcha.txt, available at https://github.com/GAIGResearch/GVGAI/blob/master/examples/2player/gotcha.txt), I think that the game is made such that player 0 has to catch player 1's avatar, at what point both players merge together, and player 0 would win.
In contrast, when player 0 doesn't manage to catch player 1's avatar in the limited time (1000 ticks i believe), player 1 wins.

However, instead, what happens is that when player 0 and player 1 collide, they do seem to merge together, as no command i do can move the avatar anymore, but the game continues (with player 0 racking up points, 1 or 2 per tick i think), until the inevitable timeout, leading to player 1 winning ALL the games ...

I tried experimenting with the termination conditions a bit but wasn't able to figure out how to change it to make it work.

P.S.: I noticed something weird which i don't understand why it happens based on reading the rules, which is that after both players' avatars merge, when they collide with one of the NPCs, the score of player 0 stops increasing further. Not sure if this is a second bug or actually part of the bug I am talking about

Best regards :D

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