RUN DIFF Compare two seeded run logs in your browser. The page pairs each run by its scenario, its seed and its setup. A shared seed is not enough when the scenario or the setup differs. Build names stay as notes. They are not used to pair runs. Your logs stay in this browser. Nothing is sent away. HOW TO COMPARE 1. Drop or paste the earlier log on the left and the later log on the right. 2. Use JSON lines (one run on each line) or a CSV table with a header row. 3. Choose Exact when any change should count. Choose Summary for a pass rate and the average or middle value of the numbers, by scenario. 4. Read the seeds whose result changed. Read the runs that appear in only one log. Read crashed, errored, queued, interrupted and timed-out runs in their own lists. Those stopped runs are not counted as losses. 5. Save the comparison as JSON or CSV if you want a copy. The file downloads on this computer. WHAT EACH RUN NEEDS scenario The matchup or encounter. Also accepted: matchup, encounter. seed The seed for that run. config Optional setup. Also accepted: fixture, config_hash, rules_hash, setup. result What happened. Also accepted: winner, outcome, ending. status Optional. Use this when a run was queued, interrupted, crashed, errored or timed out. numbers Optional tallies, such as stock, turns, or a ledger of goods in and out. Nested stats, ledger and numbers objects are read too. A person can paste a log by hand. A Sprout can save a log from a run, and you can drop that file here. EXAMPLE LINE {"scenario":"grove-duel","seed":7,"config":"rules-a","winner":"Wren","turns":12,"stats":{"dmg_a":40,"dmg_b":30},"ledger":{"gold_in":120,"gold_out":95}} EXAMPLE TABLE scenario,seed,config,winner,status,turns,stock grove-duel,7,rules-a,Wren,ok,12,10 SAMPLE LOGS sample/before.jsonl and sample/after.jsonl are a small made-up pair. sample/before.csv and sample/after.csv are the same pair as a table. The Load sample logs button reads the JSON lines. WHAT THE SAMPLE SHOWS Seed 7 in grove-duel changes from Wren to foe. Seed 11 stays Wren, with the same numbers. Seed 19 finishes in the earlier log and times out in the later log. The timeout is not a loss. Seed 3 is only in the earlier log, and it was interrupted. Seed 4 crashed, then errored. It is not a changed result. Seed 5 is only in the later log. Seed 7 in market-day is a different scenario, so it is not paired with the duel. Seed 21 uses a different setup in each log, so the two runs stay unpaired. Seed 8 keeps Wren, while gold_in changes. EXACT AND SUMMARY Exact lists a seed when the result changed, or when a number changed by more than the limits you set. Leave both limits at 0 to count every change. Raise the percent limit when a one-point move should stay off the list. Summary shows, for each scenario, how often each result appeared and the average or middle value of each number. Rates and averages use finished pairs only. If the earlier value was 0, the page says so instead of inventing a percent. A rough range appears only when a scenario has enough finished pairs. Until then you get the raw change and the count. If the logs include a tick and a state hash on more than one line for the same seed, Exact also shows the first tick that differs and up to five earlier lines from each log. Open this page from the Game tools list: https://oddsprig.com/tools/game-tools/