Checked 30 Sep 2026 with tools/sources/check.js on GitHub's runners (.github/workflows/sources-check.yml, run by hand; our container's proxy blocks these sites). A source is switched on in tools/sources.json only once its terms allow it (Jordan, 30 Sep: direct readers yes wherever robots.txt and terms allow; T3's don't). Never Best Coast Pairings directly (its EULA; Jordan won't email them). Stat Check, Goonhammer, Listhammer's /stats and GW's Metawatch: a monthly cross-check only (T-332, reports/crosscheck.md), never copied into our data, never shown or linked on the site (Jordan, 30 Sep).
| Source | robots.txt | Terms | What's public | Verdict |
|---|---|---|---|---|
| grimstat-corpus (MiniHeadQuarters) | n/a (GitHub) | CC BY 4.0 for the top-level files | lists with placings, event links | on |
Listhammer (corpus listhammer/) | disallows /api/, /events/, /players/, /list/ | not under the corpus's licence | via the corpus: X-0/X-1 lists and every event's results (BCP and Tabletop Herald events) | off until Listhammer says yes (T-411; email below) |
| Longshanks (warhammer40k.longshanks.org) | allows all but admin paths, crawl-delay 20 s | no terms page found (About: copyright contact only) | /results/: players' records and armies, filterable (3+ wins, 1 loss or fewer); event pages (size, format); per-event faction stats need a login; deeper analytics are paid (Longshanks Plus) | 30 Sep 03:46Z: answered our runner with a bot challenge (captcha), so not open to machines: email first (below); no reader, no workaround |
| Tabletop Herald (tabletop-herald.com) | Allow: / for all | none (privacy and imprint only; code-b agile websolutions GmbH, Berlin) | tournament pages embed their data (size, rounds, country, each player's army; players' names, which we'd drop); army lists need a login; standings come from an undocumented API | a reader would need its private API: email first for an API or export (below); its events reach us through Listhammer |
| T3 (tabletopturniere.de) | allows all but players, privacy, cookies | §8: reproduction and use of content needs prior written consent | results, army rankings, RSS/XML feeds | permission needed (email below) |
| tabletop.to | none | none | domain parked (a registrar's renewal page) | dropped |
| List Engine (listengine.online) | no rules | none; one developer, reachable on Discord | its own backend API | permission needed (message below) |
| Hutber (hutber.com, stats.hutber.com) | not readable: a Vercel bot checkpoint (HTTP 429) | not readable | nothing to machines | permission needed (message below) |
Internal-use acquisition (Jordan, 6 Oct; T-735)
Jordan, 6 Oct: "ignore 30/sept rule and just acquire as much anonymized data as you can, for building our model, not publishing". For the model only, any publicly readable 11th-edition tournament data may be acquired, anonymized (no player names or identifiers), into the git-ignored build/tournaments/: never committed, never in docs/, never shown or linked on the site, and fed to no ledger, popularity file or yardstick until Jordan says how it's used. Publishing is unchanged: only grimstat-corpus's top-level files (CC BY 4.0, credited) reach the site, and the drafts below still stand for anything we'd want to show. Limits kept: no bypassing captchas or bot checks, no logins or anyone's account, nothing from Best Coast Pairings' app or API directly, robots.txt Disallow and crawl delays respected, about one request a second per host, Gemini only to find sources (never its numbers). One more limit applied in T-735: a source whose own terms forbid copying its content into a database (Spikey Bits) or reproducing it (shop blogs) was skipped too, as Best Coast Pairings is for its terms.
Found 6 Oct (Gemini with search, 15 grounded calls, every source then fetched and read here; full table and counts in reports/tiers/2026-10-06-tournament-sources-internal.md):
| Source | robots.txt | Terms | What's public (11th edition) | Verdict (internal use) |
|---|---|---|---|---|
| grimstat-corpus, top level | n/a (GitHub) | CC BY 4.0 | MiniHQ lists with placings | acquired (the baseline; also the only source published) |
| grimstat-corpus, listhammer/ | n/a (GitHub) | not under the corpus's licence | BCP and Tabletop Herald X-0/X-1 lists and results | acquired for internal use (T-738): Jordan, 6 Oct, "Yes, internal use"; read by tools/sources/listhammer.js into build/tournaments/ only, list names dropped; still off for publishing (needs Listhammer's OK, T-411) |
| MiniHeadQuarters, direct | no rules, no content signal | /tcu: nothing on machines, no licence | ended events: standings (faction, W/L/D), public lists | acquired (tools/sources/mhqsite.js) |
| Tabletop Herald, public pages | allows all | none | each event's field (army and detachment per player) in the page; standings and lists only through its undocumented API | acquired, field only (tools/sources/tabletopherald.js); the API not called |
| Lexmechanic Meta Merge | allows | none found | Listhammer's GT winners | not read: Listhammer's data by another route; goes with the listhammer/ decision |
| Longshanks, Hutber, Goonhammer | — | — | bot checks answer machines | skipped (no bypassing) |
| Best Coast Pairings (WTC 2026, Global Rankings) | — | EULA | lists behind an account | excluded |
| 40kdc-meta (github.com/wn-mitch/40k-list-extension) | n/a | MIT code | BCP lists captured by users' browser extension; its API needs an issued key | skipped (a key, and BCP's data) |
| Reddit r/WarhammerCompetitive | disallows everything | Data API terms | threads, lists in posts | skipped (robots.txt) |
| Spikey Bits | allows, crawl-delay 10 | forbids copying content into a database | "Undefeated lists" articles (a few lists a week, US GTs) | skipped (its terms) |
| Frontline Gaming, Flipside Gaming, Mighty Melee | allow | shop terms forbid reproducing content | a few event reports | skipped (terms; a handful of lists) |
| UKTC (uktc.events) | allows | t&cs read, nothing on machines | podiums and faction breakdowns in prose | not read (prose, a few results; a candidate if Jordan wants UK podiums) |
| TourneyKeeper | allows | none | a frozen archive of 2024 | nothing from 11th edition |
| New Recruit | disallows /app/ (where tournaments live) | — | client-side app | skipped (robots.txt) |
| Ecksen, ChampionsHub | none / no rules | none | client-side apps, no readable pages | skipped (only private APIs) |
| GrimSlate | disallows /api/ | forbids scraping that circumvents controls | a list builder's shared rosters, not results | not a tournament source |
| Warp Friends, Woehammer | allow | WordPress | weekly stats from BCP; top lists on video | cross-check only (aggregates) |
| Stat Check, Tabletop Battles, Metawatch | — | — | faction win rates | cross-check only (unchanged) |
| T3, List Engine | — | T3 §8: consent first | — | permission first (unchanged; drafts below) |
| GitHub, Hugging Face, Zenodo, Kaggle | — | — | searched 6 Oct: no 11th-edition tournament dataset besides grimstat-corpus (one 10th-edition tracker; one organiser's repo with 7 lists, no placings; Kaggle needs an account to search) | none found |
Drafts for Jordan (his wording, 30 Sep; send from hello@tacticalreroll.com)
Addresses: see "Where to send them" below.
Listhammer
Hi there, I'm Jordan, and I run Tactical Reroll, a free mathhammer calculator for 40k: you pick a unit and a target and it works out the damage, with a little pixel battle on top. I've been a fan of Listhammer for a while; the site is the best read on the competitive scene I know. I'm writing to ask a favour. I'd love to use your event results (which armies played and how they did, nothing about individual players) to give our unit rankings a 'what's actually winning' column and a fairer sense of where each army stands. We're not a lists or results site and don't want to be one: anywhere we showed a number from your data we'd credit Listhammer by name and send people to you for the lists and the events themselves. The corpus on GitHub (grimstat-corpus) already relays your feed, so reading it there would be the least work for you, but whatever route or terms you're comfortable with is fine by me, including none at all. If our own numbers (per-unit damage, loadout comparisons) would ever be useful to Listhammer, they're yours. Thanks for reading, and for the site. Jordan
Listhammer, revised as a GitHub issue on grimstat-corpus (5 Oct) (Listhammer publishes no address; the corpus's maintainer relays its feed. Post at https://github.com/N041M/grimstat-corpus/issues/new from Jordan's account; an issue is public, so it stays short and points to email for details.)
Title: Permission to use the listhammer/ results for unit-tier research (Tactical Reroll)
Hi! I'm Jordan, and I run Tactical Reroll, a free mathhammer site for 40k. First, thank you for grimstat-corpus: we already use the top-level files under CC BY 4.0 and credit the corpus wherever its numbers appear.
I noticed the
listhammer/folder isn't covered by the corpus's licence, so we've left it alone. I'd like to ask whether we could use it, and if it isn't yours to grant, whether you could pass this to Listhammer or point me to the right contact (I couldn't find one on their site).What for: we're building unit tier lists that explain themselves (damage, durability, objectives and so on), and we test them against real tournament results: how lists with a unit actually finish. The top-level files have about 490 lists since 11th edition launched, which is thin per unit; the results in
listhammer/would make that check far more reliable.What we'd do and not do:
- Use only aggregates: per army and per unit counts, win rates and finishing positions. Never player names, list text, or anything that identifies a person.
- We aren't a lists or results site and won't become one. Wherever a number from this data appeared, we'd credit Listhammer (and the corpus) by name and link to them for the lists and events.
- Happy to follow any terms you or Listhammer prefer, including a "no", and to share our own per-unit numbers back if they'd ever be useful.
Thanks for reading! For details I'm at hello@tacticalreroll.com. Jordan
Longshanks
Hi there, I'm Jordan, and I run Tactical Reroll, a free mathhammer calculator for Warhammer 40,000 (pick a unit and a target, see the odds). I'd like to ask permission to read the public results of ended 40k events on Longshanks once a day (each player's army and record, no names), at the 20-second spacing your robots.txt asks for, so our unit rankings can show which armies are doing well in the UK and Australia rather than only the French events we read today. We're a calculator, not a results site: anywhere we showed a figure from your data we'd credit Longshanks and link to the event page on your site. If you'd rather we used an export or an API, or would rather we didn't at all, just say. Thanks for your time, Jordan
Tabletop Herald
Hi there, I'm Jordan, and I run Tactical Reroll, a free mathhammer calculator for Warhammer 40,000 (pick a unit and a target, see the odds). Tabletop Herald is clearly growing in Europe and I'd love to include the results of ended 40k events on your platform in our army and unit rankings: each player's army and record, no names, and a credit and link to the event on Tabletop Herald wherever we showed the numbers. We're a calculator, not a results or lists site, so we'd be sending people to you for the events themselves. Is there an API or an export you'd be comfortable with us using, and are you happy for us to show the counts? If not, no hard feelings. Thanks, Jordan
T3 (German, with the English underneath)
Hallo, mein Name ist Jordan und ich betreibe Tactical Reroll, einen kostenlosen Mathhammer-Rechner für Warhammer 40.000 (Einheit und Ziel wählen, die Wahrscheinlichkeiten sehen). Da Ihre Nutzungsbedingungen (§8) für die Weiterverwendung von Inhalten eine schriftliche Zustimmung verlangen, frage ich hiermit an: Dürften wir die Ergebnisse beendeter 40k-Turniere auf T³ (Armee und Platzierung, keine Spielernamen) einmal täglich auslesen, um in unseren Armee- und Einheiten-Rankings zu zeigen, was in Deutschland gut läuft? Wir sind ein Rechner, keine Ergebnis- oder Listenseite; überall, wo eine Zahl aus Ihren Daten erscheint, würden wir T³ nennen und auf die Turnierseite verlinken. Falls Ihnen das nicht recht ist, habe ich dafür volles Verständnis. Vielen Dank und viele Grüße, Jordan
Hello, my name is Jordan and I run Tactical Reroll, a free mathhammer calculator for Warhammer 40,000 (pick a unit and a target, see the odds). Since your terms of use (§8) ask for written consent before content is reused, I'm asking here: may we read the results of ended 40k tournaments on T³ (army and placing, no player names) once a day, to show in our army and unit rankings what's doing well in Germany? We're a calculator, not a results or lists site; anywhere a number from your data appears, we'd name T³ and link to the tournament page. If you'd rather we didn't, I completely understand. Many thanks and best regards, Jordan
Sending them (Jordan, 30 Sep): each email links the site twice and attaches nothing. Plain-text mail writes the two addresses out (https://tacticalreroll.com and https://tacticalreroll.com/rankings/); no GIF or image attachments (spam filters, and it reads as marketing); a shared matchup link may stand in if Jordan wants to show the pixel battle.
List Engine (the developer on Discord) and Hutber: the Longshanks draft, naming their site.
Where to send them
Read 30 Sep 04:56Z with tools/sources/check.js --contacts on GitHub's runner:
| Platform | Where to send it | Found on |
|---|---|---|
| Listhammer | No address published. Its about, privacy and home pages and footer hold no email, contact form or Discord invite (the footer is only About · Privacy). Two routes: ask grimstat-corpus's maintainer (github.com/N041M, who relays Listhammer's feed and so has a contact) through an issue on github.com/N041M/grimstat-corpus, or Listhammer's Discord bot, whose support server (if it lists one) is on its Discord app page | listhammer.info/about, /privacy, / (read in full, 04:56–04:58Z) |
| Longshanks | admin@longshanks.org (also their Discord, discord.gg/2CjNkGHpYa) | longshanks.org/help/ and /about/ (a mailto link) |
| Tabletop Herald | info@code-b.com (confirmed; also their Discord, discord.gg/MqNmSuxVmn) | tabletop-herald.com/imprint (a mailto link) |
| T3 | the contact form on tabletopturniere.de/impressum: click the operator's name, Matthias "Blackhawk" Althaus (the form opens for registered users only, so Jordan needs a free T3 account); no address is printed. A general feedback site also exists: feedback.tabletoptournaments.net | tabletopturniere.de/impressum |