PUBLIC DOCUMENTATION REVIEW · 21 September 2026
A feature-and-workflow comparison, not a proven ranking. VRA is pre-release; the other column summarises the cited public product documentation. “Not established” means we have not substantiated an equivalent, not that the feature does not exist.
VRA’s focus is inspectable outcomes, deterministic boundaries and optional teacher-guided model improvement. That focus does not make every capability exclusive or establish universal superiority.
26 configurable Viking Rise actions
Rewards, research, construction, troop care, recruitment, resources, protection and exploration share one current workflow engine. Individual live passes do not mean every variant is accepted.Extensive Viking Rise action guides
Choose the order, options and assigned farm
Arrange supported actions and their settings in the customer interface. Each farm can use a different assigned routine instead of one blanket task list.Ordered actions and account configuration
Concurrency limits, staggered starts and rotation
Control how many farms are active, stagger startup and rotate eligible work. Full concurrent routine acceptance is still being qualified; no unlimited-capacity claim is made.Concurrency and separate worker queues
Assigned routines and next eligible work
The development interface exposes schedules and farm assignments. The full release target adds clearer routine-completeness warnings, timezone presentation and when pending edits take effect.Action edits next cycle; worker edits next Start
Farms, activity, schedules and evidence together
The Command Centre brings fleet readiness, active farms, the attention queue and recent outcomes into one interface, with dedicated reports and environment-health views.Overview, accounts, logs and tools
Completed · no work · unavailable · skipped · failed · attention
VRA separates completed effects, already-satisfied tasks, game blocks, configured skips, engineering failures and uncertainty. The operator can see why the action stopped.Activity outcomes and failure reasons documented
Relevant captures alongside action history
Review the observed screen, action result, timestamps and failure context together. Captures support inspection; they are not automatically public or a promise that every result is correct.Structured logs; equivalent evidence view unverified
Checkpoints tied to the farm and routine
Retain progress and unresolved outcomes across service interruptions. A changed identity or uncertain previous effect can block replay for review rather than treating the run as fresh.Continue from last completed account
Same engine, one selected farm, inspectable evidence
Run an individual action with its selected settings and inspect captured steps. The validation console and scheduled routines resolve through the same current engine—not separate demo logic.Equivalent not established
Uncertain spends and dispatches held for review
Keep the attempted input separate from a verified effect. If the outcome cannot be reconciled, automatic whole-action replay is suppressed and the uncertainty stays visible.Recovery documented; equivalent replay guard unverified
Workflow-specific caps and premium exclusions
Configure supported resource categories, quantities and risk permissions. Free recruitment and resource-priced shops exclude paid repeat summons and gem purchases from their normal scope.Resource and speed-up opt-ins for training
Check ready outputs and existing queues first
Training, research and healing distinguish ready output, an active queue and an eligible new task. Collection and assistance are recorded separately from starting new work.Busy training skipped unless speed-ups allowed
Report a locked requested tier; continue other types
A positively identified locked configured tier is a per-type game block, not permission to invent a lower target. Other configured troop types can still be evaluated. This branch needs broader live acceptance.Requested tier is a ceiling; lower unlocked tier allowed
Action deadlines, retry limits and recovery history
Separate action attempts, local recovery, device recovery and recovery time. Circuit state and stop reasons are available to the operator; shared recovery behaviour remains under qualification.Layered recovery and per-action retry budgets
Eligible gathering squads, not combat or support
The supported recall workflow identifies resource-gathering marches and checks their homeward transition. Unrecognised or excluded marches do not become eligible simply because Recall is visible.Recall guide listed; matching exclusions unverified
Supported mappings, exclusions and a backup
Review allowlisted configuration before confirming import. Credentials are not imported and migration does not automatically destroy or rebuild emulator instances. Compatibility still needs validation.Preview import; guide requires instance rebuild
Service and emulator readiness in the Command Centre
Review environment readiness without confusing a missing service or emulator problem with an in-game task outcome. Improved first-run configuration guidance remains a release target.Virtualization diagnostics and instance tools
Selected diagnostics; screenshots are optional
The development support-bundle builder limits diagnostic fields and includes screenshots only when selected. Review any screenshots before sharing because game screens can contain account information.Logs and support documented; bundle parity unverified
Public wiki, action settings and outcome explanations
Browse setup, operation, troubleshooting and action-specific references now. The seven-day free trial is planned for release; joining the interest list does not start it.Detailed game-action and setup guides
Separate outcome reporting and a published method
Development reports separate performed work, no-action, game blocks and failures. Public percentages remain withheld until the sample meets the published reliability gate; a no-crash rate is not a task-completion rate.Public crash-rate statistic; not the same metric
Comparison of the GnBots desktop/LDPlayer workflow, BotDaddy’s public product documentation and VRA’s development build and release targets. GnBots Auto/cloud is excluded. “Not established” means the cited public documentation does not establish the equivalent capability, not that it is absent. Shared capabilities are credited. This is not a speed, reliability or ban-safety ranking. VRA remains pre-release; built does not mean every game variant is qualified.