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

[Runt] Change our handling of Stalemates #92

Open
GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Open

[Runt] Change our handling of Stalemates #92

GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Labels
auto-migrated Milestone-Release_Next Priority-High Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Change our handling of Stalemates. If we're losing significantly, then
value a stalemate highly. If we're winning, then value a stalemate low.

Original issue reported on code.google.com by [email protected] on 29 Apr 2008 at 2:01
@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 14 May 2008 at 6:27

  • Changed title: [Runt] Change our handling of Stalemates
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 8 Aug 2008 at 6:50

  • Added labels: Milestone-Release_Next
  • Removed labels: ****

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 Milestone-Release_Next Priority-High Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter