Start here
Start here: what VRA is and how to use this wiki
The quickest route from a new VRA installation to a controlled first farm run—and where to look when something goes wrong.
What VRA is#
Viking Rise Automation (VRA) is a Windows desktop command centre for running supported, repetitive Viking Rise farm tasks through existing LDPlayer profiles. You choose the farms, task order, preferences, limits, schedules and practical concurrency.
VRA is not a cloud game service and it does not choose your account strategy. It operates the farm routine you configure, checks the visible game state, records task outcomes and stops or asks for attention when a result cannot be established safely.
The product is still in development. Screens, labels, supported workflows and final requirements can change before public access. This wiki documents the intended customer experience without exposing implementation details.
Recommended learning path#
- 1
Check your PC and LDPlayer
Read System requirements, then make sure each intended farm has a stable, playable LDPlayer profile.
- 2
Complete the environment checks
Use the guided setup and environment-health view before adding automation complexity.
- 3
Add one non-critical farm
Map one known emulator profile, assign a small routine and confirm you can identify its results.
- 4
Expand gradually
Add tasks and farms in small groups. Set concurrency around measured PC capacity, not the number of farms you own.
- 5
Use the evidence
If a task fails, read its result and capture before retrying. Search this wiki by the visible symptom.
The support ladder#
- Search the exact visible status or symptom in the wiki.
- Check Environment Health and confirm the farm is mapped to the expected LDPlayer profile.
- Open the latest failed step and review its screenshot or customer-visible evidence.
- Try only the safe recovery described in the relevant article; do not repeatedly replay uncertain spending or dispatch actions.
- Contact support with the evidence checklist only after the above steps.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.