The October confusion is now part of the official record
Games Workshop said on 29 October that October’s Warhammer 40,000 rules update reached the app as several downloads across a number of days rather than one clean release. It also announced that a dated Rules Update Log will accompany the next app version, with the next quarterly balance update planned for the week beginning 7 December. That is useful news, but it does not solve the tournament player’s immediate problem: which version is your event actually using? [1]
The unglamorous answer is that your tournament rules are a small evidence pack, not whatever your phone happened to refresh over breakfast. An app is convenient at the table. A dated event pack, the organiser’s cut-off and the official documents in force at that cut-off are what let two players begin round one from the same place.
This is not a reason to panic every time an update badge appears. Games Workshop says its aim is no more than monthly rules updates, with most of those dealing with clarifications and errors, while larger changes sit in quarterly balance updates. The sensible response is a repeatable check, not a Thursday-night demolition of the army case. [1]
Start with the organiser’s cut-off, not the newest file
Before changing a list, find three dates: list submission, the event’s rules cut-off and the date of the official document you are reading. If the pack does not state a rules cut-off, ask the organiser in writing. A newer Games Workshop file may be the current public rule, but that does not automatically make it the rule for an event whose lists were locked under an earlier version.
Games Workshop’s Event Companion describes an official event framework while making clear that organisers can adapt it. It also ties the submitted roster to a chosen Force Disposition, and that choice shapes the primary missions a player can meet. In other words, the version of your roster is not clerical trivia; it can affect what the army is expected to do across the weekend. [2] [3]
Write the answer at the top of your preparation notes in one line: event name, rules cut-off, Event Companion version and list version. If that sentence is difficult to complete, the list is not ready to be packed. It may be painted to within an inch of its life, but paperwork remains immune to edge highlighting.
Make a dated tournament rules pack
Keep one folder for the event. Save the organiser’s pack, your submitted roster, the official Event Companion and the official faction documents that apply to the list. Record the download or update date beside each one. Games Workshop’s downloads page is the live index for current material; when checked on 30 October, it identified the Munitorum Field Manual as updated on 14 October. That date tells you what the public index says now. It does not, by itself, tell you what your organiser has adopted. [4]
Your roster copy should include the choices that matter before a game begins: detachment combinations, Force Disposition, enhancements, unit options and anything else the event requires. Export it after the final legality check and give the file a version name you can recognise. ‘final-final-actually-final’ is a traditional system, but a date and event name tend to age better.
Then keep a short change sheet. It should not reproduce whole rulebooks. Note only the items that can alter a decision in your games, with a link or page reference back to the official source. The point is to reach the answer quickly and show where it came from, not to create a personal rules archive that nobody can audit.
Separate a clarification from a list-changing update
When something changes, read it in two passes. First ask whether the submitted roster is still legal under the event’s chosen rules. Check points, unit sizes, keywords, weapon options, detachment requirements and Force Disposition availability. This article does not quote a new points change because the 29 October announcement was about the update process, not a fresh balance release.
The second pass is about play. A clarification can leave the list legal while changing target priority, timing, movement or how confidently a unit performs its job. Mark the affected decision in plain English: ‘this unit no longer holds the lane alone’, ‘this sequence needs confirming before dice are rolled’, or ‘the reserve plan still works’. That is far more useful in round four than a yellow highlight across half a PDF.
If the change genuinely alters the army, return to the method in our September balance-update tournament plan: preserve the jobs the list must perform before swapping units simply because a new number looks attractive. A legal list can still be strategically broken if the repair removes its only screen, action piece or reliable answer to a common target.
Practise the locked version, not the rumour
Once the organiser confirms the cut-off, stop rehearsing every possible future. Play the version you are taking. Run one deployment, one opening exchange and one awkward mission decision with the exact roster. If a rule has changed, deliberately create the situation where it matters and resolve it from the saved official source.
Give the practice a finish point. Check the list, make the necessary adjustment, then leave it alone long enough to learn it. Constantly rebuilding in response to screenshots and second-hand summaries produces an army that is always current and never familiar. The five-round day still rewards clear decisions made at a reasonable pace; our tournament time guide is a useful companion to this rules check.
On the morning of the event, refresh only if the organiser has said later official material applies. Otherwise use the locked pack. That avoids the peculiar situation where one player has accepted an overnight app change and the other is correctly using the published event cut-off.
Handle the table conversation early
Before deployment, mention any rule or version issue that is likely to matter. Keep the explanation short, show the official source and agree how the event is treating it. If you cannot agree, call a judge before the disputed move happens. A two-minute question before round one is cheaper than reconstructing a turn after both armies have committed.
The same principle applies when an opponent shows you an update you have not seen. Check the document date and the event cut-off before debating the wording. They may have a newer public rule; you may still have the correct event rule. Those are different questions, and a judge can resolve the second one without either player needing to win a small courtroom drama beside objective three.
Games Workshop’s promised dated log should make future checks easier. Until it arrives, use the live downloads page and the organiser’s written decision together. When the December update is released, repeat the process: verify the source, compare it with the event deadline, change only what the list or plan actually requires, and practise that version. The clever part is not reading every update first. It is arriving with one coherent game in your bag.
