Skip to content
Home » News » Collection of .bat files to run FastChess

Collection of .bat files to run FastChess

Collection of .bat files to run FastChess (ready-to-use)

Here’s a tidy, SEO-friendly toolkit of Windows .bat launchers for FastChess based on your own SPRT example and notes. I’ve kept your two Revolution builds as the base pair, and—when needed—added Stockfish 17.1 and Obsidian 16.40 exactly as you requested. The pack covers 180+2 and 900+15 time controls across SPRT1v1 matchesround-robingauntlet, and a Swiss-style harness (see note below).

Each script is self-contained, sets sane defaults for logging/PGN, and prints running output in Cutechess format for easier parsing. FastChess flags follow the current public docs and examples. (GitHubofficial-stockfish.github.io)


What’s included (engines & formats)

  • Two engines (from your doc):
    • Revolution_DEV → revolution_090925_v2.20_avx.exe
    • Revolution_BASE → revolution.exe
  • Three engines: add Stockfish 17.1.
  • Four engines: add Obsidian 16.40.
  • Time controls: 180+2 and 900+15.
  • Formats: 1v1 SPRT, 1v1 matchround-robin (3 & 4 engines), gauntlet (anchor A vs field), and a Swiss-style 4-engine harness.

Quick start (edit once, run forever)

  1. Edit paths at the top of any .bat (they’re the same in all files):
    • FASTCHESS → path to fastchess.exe
    • ENGINE_A … ENGINE_D → your engine EXEs
    • BOOK → I pre-filled your UHO_2024_8mvs_+085_+094.pgn
  2. Double-click a .bat or run it from cmd.
    Outputs go to a results folder next to the script: a timestamped .pgn and .log per run.
  3. Adjust CONCURRENCY to taste (e.g., higher for 180+2, lower for 900+15) and ROUNDS as needed.

Why these flags? They mirror the examples shown in the FastChess README and Stockfish Fishtest’s “Running Fastchess” page (e.g., -engine cmd=… name=…-each tc=…-rounds-repeat-concurrency-pgnout-log, and Cutechess-style -output). (GitHubofficial-stockfish.github.io)


Downloads — “cmd torneo fastchess”

Tip: click to download, then right-click → Properties → Unblock if Windows warns about internet files.


    What each launcher does (at a glance)

    • Common header: sets your engine paths, book, results folder, a timestamp, and -srand.
    • Logging & PGN: every run writes both a .log (info level, with engine streams enabled) and a .pgn for later analysis.
    • Output: -output cutechess for compatibility with your tooling. (GitHub)
    • Intervals: -ratinginterval-scoreinterval, and -autosaveinterval keep progress chatty and safe. (official-stockfish.github.io)
    • SPRT: default bounds are elo0=0elo1=5 with alpha=beta=0.05 (edit as you like).
    • Gauntlet: uses an anchor (A) vs field; you can change anchor="Revolution_DEV" if needed.
    • Round-robin: set ROUNDS=2 for a single RR, 4 for a double RR at classical, higher for blitz.

    Practical notes & pitfalls

    • No initstr. Your earlier FastChess error shows initstr isn’t a recognized engine option; these launchers avoid it and rely on standard -engine cmd=… name=… syntax instead. (This aligns with the README examples.) (GitHub)
    • Stockfish 17.1. The script names and comments use the current release tag (17.1). If your EXE is named differently, just adjust ENGINE_C. (GitHub)
    • Book usage. I pre-filled your UHO book path; feel free to swap in any PGN opening suite you prefer.
    • Concurrency. With your dual-Xeon box, 6–12 parallel games at 180+2 is often fine; for 900+15 keep it low (e.g., 2–4) to avoid time losses.
    • SPRT length. You can shorten or extend -rounds for SPRT; the test will stop once a boundary is crossed.

    Why FastChess for this?

    FastChess is a modern, efficient CLI tournament runner with straightforward flags (-engine cmd=…-each tc=…-rounds-repeat-concurrency) and clean output; it’s the same runner used in the Stockfish infrastructure, which keeps our scripts durable. (GitHubofficial-stockfish.github.io)


    Leave a Reply

    Your email address will not be published. Required fields are marked *