+ * #### SyzygyProbeDepth
+ Minimum remaining search depth for which a position is probed. Set this option
+ to a higher value to probe less agressively if you experience too much slowdown
+ (in terms of nps) due to TB probing.
+
+ * #### Syzygy50MoveRule
+ Disable to let fifty-move rule draws detected by Syzygy tablebase probes count
+ as wins or losses. This is useful for ICCF correspondence games.
+
+ * #### SyzygyProbeLimit
+ Limit Syzygy tablebase probing to positions with at most this many pieces left
+ (including kings and pawns).
+
+
+## What to expect from Syzygybases?
+
+If the engine is searching a position that is not in the tablebases (e.g.
+a position with 8 pieces), it will access the tablebases during the search.
+If the engine reports a very large score (typically 153.xx), this means
+that it has found a winning line into a tablebase position.
+
+If the engine is given a position to search that is in the tablebases, it
+will use the tablebases at the beginning of the search to preselect all
+good moves, i.e. all moves that preserve the win or preserve the draw while
+taking into account the 50-move rule.
+It will then perform a search only on those moves. **The engine will not move
+immediately**, unless there is only a single good move. **The engine likely
+will not report a mate score even if the position is known to be won.**
+
+It is therefore clear that this behaviour is not identical to what one might
+be used to with Nalimov tablebases. There are technical reasons for this
+difference, the main technical reason being that Nalimov tablebases use the
+DTM metric (distance-to-mate), while Syzygybases use a variation of the
+DTZ metric (distance-to-zero, zero meaning any move that resets the 50-move
+counter). This special metric is one of the reasons that Syzygybases are
+more compact than Nalimov tablebases, while still storing all information
+needed for optimal play and in addition being able to take into account
+the 50-move rule.
+
+
+## Compiling Stockfish yourself from the sources