MTG farm volunteer client v19

Superseded by client-v20, which fixes stopped workers you could not start again: on this release, after Stop All or a restart, a row's start button is greyed out until you Add a worker. Press Update on your client's page to get it. Everything below remains true for this release.

Unzip anywhere and double-click run-client.bat -- no Python, no JDK, no checkout needed. On first run it asks for the farm URL and the credential your operator gives you; the harness pin is baked in, so there is nothing to paste. Then click Install Forge, pick a work mode, and start.

New in v19: two fixes to the card order a game is actually played from.

The client can now play a walk candidate's own derived card order. An evolve walk compares a champion deck against a candidate differing by one card, at matched random seeds -- and for that comparison to reduce variance the candidate has to play the champion's exact card order with the one card substituted in place. A candidate's lease now names those bytes and this client plays them.

The client also claims its cached decks by their CONTENT digest instead of by the deck's hash. A deck hash is order-blind by design, so a deck file rewritten into a different card order kept the same hash -- and any client that had cached it went on playing the old order for ever, because the server never re-sent the file and no digest was ever compared. Measured against a live walk: every anchor played by a remote volunteer disagreed with its locally-played counterpart on the opening hand, while every locally-played anchor matched exactly. If you have been running an older bundle, the farm will re-send your decks on the next claim either way -- no action needed.

Requires a farm advertising active_engine (post-de63260).

sha256(mtg-farm-client-v19.zip) = 6d5021c2084c886a4f6a5681b3089906a9d6e36fb8dbfaf4ad20f9dbe65c2b54