Issue 1 — ActionGroup AND continuation ordering: The old code prepended `all` (preceding AND-group actions) into ContinuationActionsJson, so resume ran [chosen, preceding, outer] instead of the correct [preceding, chosen, outer]. Fix: add PrecedingActionsJson to PendingActionGroupPick; AND-case stores preceding there (prepending to any inner-group preceding); ResumeActionGroupPick reads it and uses preceding.Concat(chosen).Concat(continuation) for final execution. Nested remaining-group pauses also accumulate preceding correctly. Issue 2 — Effect-level pause terminal contract: Documented as a design constraint: pausing effects (CloneSpiritAsToken TargetTile, ChannelCardFromZone TargetTile/Choice) must be last in their action's Effects list. Remaining effects / remaining targets are silently dropped on pause. No functional change; constraint is now explicit in code. Issue 3 — StackDeck pause loses continuation: PendingRevealChoicePick already had ContinuationActionsJson/RangeJson/ ForceDurationJson fields but StackDeckEffect never populated them and ResumeRevealChoicePick never executed them. Both are now fixed: pause stores ctx.ContinuationActions + ctx.ActivationRange + duration; resume runs ExecuteActions on the stored continuation after ordering the deck. Issue 4 — ResumeTargetPick ActionIndex=0 contract: Added a clear CONTRACT comment: the paused action replays at index 0, so the client must submit targets with ActionIndex=0 in its response. Generated with [Claude Code](https://claude.ai/code) via [Happy](https://happy.engineering) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Happy <yesreply@happy.engineering>
SOR
Resources
In addition to this gitea repository, the application's servers and webclient are deployed using containers using ArgoCD.
Installation Instructions
Visual Studio Code
Download any version of Visual Studio Code, from here:
Godot Version 4.5.x
Download a version of Godot 4.5.x, preferrably Godot 4.5.2-stable, from here:
The Godot executable doesn't require an installation. Just unzip the godot folder and run the 'Godot_v4.5.2-stable_win64' executable.
Clone Instructions
Only HTTPS clone to VSCode is supported at the moment.
- SSH Clone doesn't work since the repository root doesn't have a .git folder.
On the "Code" page for SOR, click the "Code" button and then click "Open with VS Code".
- Your browser may ask if you want to launch VS Code. Do so.
- VS Code will utilize your browser to authenticate. Do so.
The Client
The Client is a GUI created in Godot.
Modifying the Client in Godot
Once you've cloned the repository, Open Godot.
Then, select "Import".
Open the project.godot file in the Client/origin-client/ folder.
Building the Web Client
When you update the 'main' branch of the SOR Repository, a gitea action will automatically start, building the Godot Web Client.
Deploying the Web Client
After the Web Client is built, you need to restart (not sync) the Deployment object of the sor-webclient application in ArgoCD.
