mirror of
https://github.com/HChaZZY/Stockfish.git
synced 2025-12-19 16:46:30 +08:00
Revert threat move ordering
Does not seem to improve anything. Anyhow idea is nice, maybe we still have to find correct recipe. Signed-off-by: Marco Costalba <mcostalba@gmail.com>
This commit is contained in:
@@ -72,7 +72,6 @@ MovePicker::MovePicker(const Position& p, bool pv, Move ttm,
|
||||
mateKiller = (ss.mateKiller == ttm)? MOVE_NONE : ss.mateKiller;
|
||||
killer1 = ss.killers[0];
|
||||
killer2 = ss.killers[1];
|
||||
threatMove = ss.threatMove;
|
||||
depth = d;
|
||||
movesPicked = 0;
|
||||
numOfMoves = 0;
|
||||
@@ -271,11 +270,6 @@ void MovePicker::score_noncaptures() {
|
||||
else
|
||||
hs = H.move_ordering_score(pos.piece_on(move_from(m)), m);
|
||||
|
||||
// If the null move was refuted by a capture then give a
|
||||
// bonus if we move away the captured piece.
|
||||
if (threatMove != MOVE_NONE && move_from(m) == move_to(threatMove))
|
||||
hs *= 3;
|
||||
|
||||
// Ensure history is always preferred to pst
|
||||
if (hs > 0)
|
||||
hs += 1000;
|
||||
|
||||
Reference in New Issue
Block a user