From 12cceb578f4644d57904c3797d0c52acf415c705 Mon Sep 17 00:00:00 2001 From: H.G.Muller Date: Tue, 8 Nov 2016 22:01:16 +0100 Subject: [PATCH] Update README file (changelog) and man page --- README.txt | 5 +++++ uci2wb.pod | 5 +++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/README.txt b/README.txt index 2de28a4..41e2d80 100644 --- a/README.txt +++ b/README.txt @@ -50,6 +50,11 @@ H.G.Muller Change log: +8/11/2016 2.3 +Implement handling of 'UCI_Variant' option for variant announcement and selection +Pass 'info string variant' line as 'setup' command to allow engine-defined variants +Set 'UCI_Opponent' option in accordance with CECP 'name' and 'computer' commands + 22/11/2016 2.2 Use USI gameover command to relay game result Handle USI win claims diff --git a/uci2wb.pod b/uci2wb.pod index 2ceb94c..5ccd18e 100644 --- a/uci2wb.pod +++ b/uci2wb.pod @@ -44,8 +44,9 @@ instead of the standard KxR notation. =item B<-var > Forces uci2wb to announce to the GUI it supports (only) the specified variant. -There is no standardized way for UxI engines to announce what they can play, -so if these are not the standard variants implied by the protocol choice, +Although a UCI_Variant option has been proposed as a way for UxI engines to announce what they can play, +(and is supported by uci2wb), not many engines implement this. +So if these are not the standard variants implied by the protocol choice, (but, f.e. seirawan or 6x6+6_shogi) it has to be configured on the uci2wb command line through this option. -- 1.7.0.4