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.

Sign up for GitHub

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

Jump to bottom

Impossible AI can be beaten in specific condition #2

Closed
GoogleCodeExporter opened this issue Mar 17, 2015 · 2 comments
Closed

Impossible AI can be beaten in specific condition #2

GoogleCodeExporter opened this issue Mar 17, 2015 · 2 comments
Labels
auto-migrated Priority-Critical Type-Defect

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 17, 2015 •
edited by avindra
Loading

The original issue was reported on code.google.com:

  • User: aavindraa
  • Date: 6 Jan 2011 at 5:49
It can beaten like this


2|4|3
_|_|1
_|_|_

The proper response for the AI is to play in spot 3 when spot 2 is taken.
@GoogleCodeExporter
Copy link
Author 

Problem figured out.

You are X, computer is O

X|_|_
_|O|X
_|_|_

Computer plays:

X|_|_
O|O|X
_|_|_


Why? Because you could've done this to fork, and win where "W" is indicated:

X|_|_
X|W|X
W|_|_

BUT! There is an O at the first W:

X|_|_
X|O|X
W|_|_

So that fails. Forking needs to be checked against an additional spot, as 
clearly indicated by this.

Original comment by aavindraa on 6 Jan 2011 at 6:25

@avindra avindra changed the title Impossible Mode Failure Again Impossible AI can be beaten in specific condition Nov 17, 2020
avindra added a commit that referenced this issue Nov 18, 2020
@avindra
🔄 Fix Issue #2
ea9222f 
 * now correctly rotating over each check,
   and even eagerly testing over
   permutations (might be overkill)
 * some redunant checks can probably be
   removed. it has been noted that:
   e = f, b = c and d = g
 * block forking and forking paths merged
   to one data structure (identical)
@avindra
Copy link
Owner

avindra commented Nov 18, 2020

Solved by implementing rotation loops in the correct order.

@avindra avindra closed this as completed Nov 18, 2020
@avindra avindra mentioned this issue Nov 22, 2020
Closed
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Critical Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@avindra @GoogleCodeExporter