Author: Robert Hyatt
Date: 06:26:30 08/16/98
Go up one level in this thread
On August 16, 1998 at 08:49:20, Stuart Cracraft wrote: >On August 15, 1998 at 22:18:24, Jeff Anderson wrote: > >>Can someone perhaps give me a rundown of the piece values used by different >>chess programs? How do small changes piece values in programs affect their >>play? >>Thanks, >>Jeff > >Urk! Tabs in this CCC gui.... ahem. > >Currently, I use these > > pawn 1000 > knight 3000 > bishop 3000 > rook 5000 > queen 11000 > king 12000 (but can be zero without affecting program) > this is going to lose you lots of games at upper levels. A queen is not worth two rooks and a pawn. Or a rook + two minor pieces. Try a few games giving your program a queen vs RBB for example and watch yourself get skewered. The traditional piece values have evolved over hundreds of years. Even going to 10 pawns for the queen has caused me problems in the past when I played around with this. I have no idea how well your program plays yet, but if it has reached 2500 on a server, it will find things very difficult if it will really trade two rooks and a pawn for a queen, because everyone will certainly allow that to happen... just an opinion, of course, but it looks dangerous... against 1800 players, probably ok. Against GM's? definitely not ok. >Mobility generally values bishops and knights appropriately based on the >demands of the position (square control bonus.) > >I keep two rooks lower than a queen since the program got into trouble >trading defending against a marauding enemy queen. > >Also, two minors are generally worth more than a rook and pawn also >based on the demands of the position (also square control bonus.) > >I don't change piece values during the game (and wouldn't!) > >--Stuart
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.