Installation and first-run setup

Before installing#

• Check the VRA website’s Download status page for the official release location. No public installer is available today.
• Check the published version, release notes and signing information before opening an installer.
• Close unnecessary emulator instances and allow Windows updates to finish.
• Keep an existing backup of important LDPlayer profiles. Installing VRA should not be treated as an emulator backup.

Complete guided setup#

1. 1

   Open the first-run guide

   Read each environment check rather than clicking through warnings.

2. 2

   Locate LDPlayer

   Select or confirm the supported LDPlayer installation and allow the profile list to load.

3. 3

   Review detected profiles

   Match profile names to the farms you recognise. Detection is not permission to automate all of them.

4. 4

   Choose initial capacity

   Use one concurrent farm for the first controlled run.

5. 5

   Enter the Command Centre

   Confirm Environment Health is ready before creating a routine.

Permissions and security#

Use the least Windows privilege that the released installer and runtime documentation require. Do not disable antivirus, firewall or account controls merely to force an installation through.

A security product warning should be checked against the official download, signature and current release notes. Send the exact warning to support if it cannot be reconciled.

A successful first run means#

• The intended LDPlayer profile opened—not merely any available emulator.
• Viking Rise reached a recognisable foreground screen.
• A small, low-risk routine completed or produced a clear no-action-needed outcome.
• The Command Centre recorded the farm and step results.
• No other emulator profile or Windows application received unintended input.

Choose one workflow and define what passing means#

1. 1

   Verify the character first

   Open the exact mapped profile and confirm the intended account. A matching window title alone is not enough.

2. 2

   Choose available work

   Pick a documented workflow your account exposes. Review its resource permissions and expected result before starting.

3. 3

   Remove competing input

   Do not run another bot or control the same emulator manually during the observation.

4. 4

   Inspect the immediate result

   For timed training, the expected result can be an active queue, not instant troop completion. An already-running queue can be a legitimate no-action state.

5. 5

   Expand only after review

   Record the farm, settings, starting state and observed result. Resolve an uncertain spend or dispatch before replaying or adding more farms.

• Train Troops prerequisites and expected outcome
• Collect All City Rewards workflow
• Make your setup checklist
• Check public download status