Skip to content

Commit a7d10b0

Browse files
authored
Update README.md
1 parent 97152ae commit a7d10b0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -223,10 +223,10 @@ Currently `mchess` supports up to two concurrent UCI chess engines. Each engine
223223
The mandatory fields in `<engine-name>.json` are:
224224

225225
| Field | Default | Description |
226-
| -------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
226+
| -------- | --------------------------------- | ---------------- |
227227
| `name` | e.g. `"stockfish"` | Name of executable of the engine, e.g. `stockfish`. Unfortunately this name must be precisely equal to the name of the json file, and must be referenced in `preferences.json` as either `computer_player_name` or `computer_player2_name` and within `active_agents`. That is subject to improvement in the future. |
228228
| `path` | e.g. `"/usr/local/bin/stockfish"` | Path to the engine executable. Windows users must either use `\\` or `/` in json files as path separators. |
229-
| `engine_params` | `["--backend=cuda"]` | Optional list of additional parameters for the engine that are given on start. This entry should be ommited, if no parameter are necessary. |
229+
| `engine_params` | _entry not used_ | Optional list of additional parameters for the engine that are given on start. This entry should be ommited, if no parameter are necessary. |
230230
| `active` | `true` | `mchess.py` currently uses only the first two active engines. If more engines are configured, the unused ones should be set to `false` |
231231

232232
Once the UCI engine is started for the first time, the UCI-options of the engine are enumerated and added to the `<engine-name>.json` config file. That allows further customization of each engine. Some commonly used options are:

0 commit comments

Comments
 (0)