Verify native zero-marker battle continuation
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
7e3d745807
commit
4aecf8eb9c
4 files changed
+42
-4
No files matched your search
@@ -170,6 +170,18 @@ now have connected development prototypes. The linked contracts supersede the
|
||||
historical runtime-absence statements above within their explicit boundaries.
|
||||
Reinforcements and complete combined-module acceptance remain unfinished.
|
||||
|
||||
## Reinforcements Traitor source recheck — 29 October 2026
|
||||
|
||||
The [publisher-authored base rulebook](https://cdn.1j1ju.com/medias/37/57/71-dune-rulebook.pdf#page=11)
|
||||
states that a successful Traitor caller loses nothing regardless of battle
|
||||
plans. The later printed Reinforcements face requires three reserves moved to
|
||||
Tanks; the Ecaz & Moritani rulebook's Treachery FAQ discusses Harass, without a
|
||||
direct Reinforcements/Traitor clarification found in the reviewed material.
|
||||
Both precedence readings remain plausible. The existing all-outcome charge is
|
||||
still provisional; this recheck does not establish a publisher ruling or a
|
||||
user decision. The older designer-linked April 2020 FAQ could not be inspected:
|
||||
the publisher server returned HTTP 403, and its date predates the expansion.
|
||||
|
||||
## 14 September Reinforcements cost review
|
||||
|
||||
The printed close-up at [4:24](https://www.youtube.com/watch?v=P9ZTV1uZqsM&t=264s)
|
||||
|
||||
Reference in new issue
Block a user