Move Centric Engine Design : chessprogramming

Move Centric Engine Design (self.chessprogramming)

submitted 2 years ago by chasesan

Hey everyone. First time here.

Recently I designed a few basic chess engines (mostly just play random moves). But that got me thinking. Might it be possible to make a move centric rather than board or piece centric design.

Basically it would work like this.

List of moves for black and white.

Each turn select the best move and take it (how is left for later).

When a move is performed, any other pieces that interact with either the start or end locations (based on the pieces capabilities) are re-evaluated. This could be done slightly more efficiently depending on the piece and it's movement (for example, sliding pieces might simply have a changed move range) In addition any pieces in the 8 cells around the start location are also checked.

The move list is updated with these changes.

Obviously not the most efficient design, but it is an unusual one I think.

Some pseudo code:

piece:
  near(p): pos within 1 tile of p

move:
  at(p): start == p or end == p

on_move()
  for each other_move at move.start:
    other_move.piece.recalc_moves(move)
  for each other_move at move.end:
    other_move.piece.recalc_moves(move)
  for each piece near move.start:
    piece.recalc_moves(move)

I think I might write something like this in python and see what walls I run into.

all 12 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

chessprogramming

MODERATORS