MTG farm volunteer client v23

Superseded by client-v24, which adds the 2.0.14+0bf85e6d53c engine row. The farm runs that engine as of 2026-09-19, and a v23 client cannot install it -- Install Forge refuses it by name and every claim comes back empty. The notes below stay true for the v23 asset, which is still downloadable.

One-zip Windows volunteer client for the MTG sim farm. Unzip, double-click run-client.bat, enter the farm URL and your runner credential on the first-run page, click Add, pick your work, and go.

New in v23: a game no longer depends on how fast your machine is. Forge used to give up on any AI decision that took longer than 5 seconds, so the same game could play out differently on a slower or busier machine than on a faster one. The farm's harness now lets every decision finish, and this client carries that harness's pin. Start (which syncs first) fetches the new harness on its own -- only the harness, a few tens of KB, no Forge re-download -- so update, then press Start. Older clients keep playing the harness they already have, and their Install Forge button now reports that the farm's harness is not the one they expect: that means update. Nothing else about how the client plays changed.

From v22: the 2.0.14+6747f05e908 engine row. From v21: the bundle is GPLv3 (LICENSE and NOTICE.txt travel in the zip). From v20: a stopped worker starts from its own row. From v19: a candidate's own named derived card order. From v17: the 2.0.14+139b268b780 engine row. From v16: workers persist -- add, start, stop and delete are separate, and rows and their game counts survive a restart. From v12: the client updates itself.

Headless: farmrunner.py --mode backfill --decks REF[,REF...] [--scope within].

Ships Windows embeddable Python 3.12.10; the Forge engine (~205 MB) is downloaded on demand. Needs a farm that advertises active_engine on /hello (any farm since de63260).

sha256(mtg-farm-client-v23.zip) = ab599771cc58600f4ac0b044758c08cd8fc8d0d36f26d187d1b97e139f55d427