Orion Resurgence · Design Note
Online Play Considerations
Which of these 4X designs would work on a turn-based online platform like Board Game Arena — and what that implies for a game targeting both a TUI and async multiplayer.
Compiled August 2026 · third in a series with Board Game References and Ship Progression Models
The four axes
Async online play fails in specific, nameable ways. Three of these come straight from observed experience on the 18RoyalGorge BGA implementation; the fourth is the one that tends to go unnoticed.
Turn density
How much you decide per activation. A turn that is "bid one card" is thin; a turn that is "spend your whole economy" is thick.
Wait ratio
How many other activations pass between yours. Scales with player count × activations per round — a 6-player game with one action per turn is brutal.
Plan stability
Whether thinking during someone else's turn is wasted. High-interaction games change the board before your turn arrives, so pre-planning is thrown away. Async punishes them twice: once for the waiting, again for the wasted planning.
Real-time dependency
Whether the game's content requires live human back-and-forth. Negotiation and open trading do not survive a days-per-turn format at all.
Fixing low density: reactive vs structural
The 18RoyalGorge fixes — auto-bid, auto-pass, auto-buy-stock — treated thin turns reactively, after the structure was already set. There are structural alternatives, and they are cheaper if chosen up front.
Auto-actions
Detect the obvious move and take it for the player. Works, but each one is a patch, and retrofitting them means retrofitting the UI too.
Simultaneity
Everyone commits at once, then reveal. Wait ratio drops to zero. The strongest fix available, and only available online.
Batching
Collect many small decisions into one dense phase — a single shopping trip instead of five purchase prompts.
Standing orders
Let the player declare a conditional default in advance ("pass unless X") rather than being pinged for it. Auto-actions the player chose.
Ranking the games
| Game | Density | Wait ratio | Plan stability | Verdict |
|---|---|---|---|---|
| Galactic Era | High | None — simultaneous | High | Best structural fit |
| Voidfall | Very high | Low (1–4p) | Very high | Best async fit |
| Space Empires 4X | Bursty | Low (1–4p) | Medium | Strong — already on BGA |
| Stellar Conquest | Medium | None — written orders | Medium | Online-native by accident |
| Beyond the Sun | Low — one worker | Medium | Medium | The 18RoyalGorge pattern |
| Eclipse | Low–medium | High — 1 action, then pass | Low | Great live, |
| Twilight Imperium 4e | Medium | Very high — 5 players | Very low | |
| Sidereal Confluence | n/a — real-time | None | n/a | Live-only |
Case studies
Galactic Era Best structural fit
Its Growth phase is simultaneous hidden selection of two actions from five — everyone commits at once, then reveals. Nobody waits for anybody. This is the structural version of the 18RoyalGorge fix, built in rather than patched on: there is no pass to automate because there is no passing.
Its combat is equally well-suited. Deterministic resolution (ships × combat value, higher total wins) removes the other async killer — dice rolls that require a prompt, a reveal, and a defender response. A whole battle resolves server-side and appears in the log as arithmetic.
Hidden fleet strength via dummy tokens is free online, where at a table it is the fiddliest part of the game.
Voidfall Best async fit
Not simultaneous — it wins on plan stability. Interaction is low enough that you can work out your entire turn while waiting, so a twelve-hour gap between turns costs nothing but wall-clock. Turns themselves are dense puzzles, and combat is deterministic, so there is nothing to wait through once you commit.
The cost is implementation weight: it is the most mechanically elaborate game on the list.
Space Empires 4X Proven
Already implemented on Board Game Arena, so there is a working reference for exactly the structure of interest: hidden movement plus a bursty economy. Economic phases are genuine shopping trips — high density — while movement rounds are lighter but genuinely private, so there is nothing to watch and no reason to feel excluded. At 1–4 players the wait ratio stays low.
Combat is the weak point: round-by-round resolution with tactics ordering is the one place it bogs down.
Eclipse Cautionary case
Instructive precisely because it is the best-designed game on the list. One action per turn, then pass — with six players that is five people doing a ten-second thing between each of your ten-second things. At a table this is fine; the actions are fast and you are watching. In turn-based async it is dozens of round-trips per round.
And it is not fixable with auto-actions, because the interleaving is the strategy — you take Explore now specifically because the player after you might take that tile. There is no obvious default to automate. Great table game, wrong shape for async.
Twilight Imperium 4e Worst fit
The problem is not the turns — it is that the game is the table talk. The agenda phase is a negotiation; strip out live conversation and you have removed the thing people play it for. Six players at eight hours also produces the worst wait ratio on the list. It works in live online play, which is why it lives on virtual-tabletop platforms rather than async ones.
Implications for Orion Resurgence
- Make phases simultaneous by default, sequential only where the interleaving is genuinely strategic. Galactic Era's two-of-five commit is the template.
- Deterministic combat is an async necessity, not just a TUI convenience. Every dice roll is a potential prompt, and every prompt is a round-trip. This reinforces the conclusion reached in Ship Progression Models from a completely different direction — which is a good sign the conclusion is right.
- Batch the economy into one dense phase rather than dribbling out single purchases. Space Empires' periodic economic phase is the model: a real shopping trip, and exactly the "lots to do on your turn" that makes async enjoyable.
- Design standing orders from day one. Any decision point where a player will usually do the obvious thing needs a declarable default from the start — retrofitting them means retrofitting the UI too.
- Lean into hidden information. It is simultaneously the thing tabletop handles worst, the thing a TUI handles natively, and the thing that makes simultaneous turns meaningful. All three design targets point the same way.
A tension to resolve
The paid refit recommended in Ship Progression Models is a density risk. If refitting pings the player as its own small prompt — "3rd Fleet can refit, yes/no?" — it has reinvented the 18RoyalGorge bidding problem exactly: a thin turn that makes everyone else wait for a decision that is usually obvious.
Resolution: refit belongs inside the batched economic phase, as one line on a build screen alongside everything else being purchased that turn. Same decision, same strategic weight, no extra round-trip. If a standalone refit prompt ever appears in the design, that is a signal the economy phase is not batched tightly enough.