Safety & support
Glossary and frequently asked questions
Plain-language definitions and quick answers covering farms, routines, queues, concurrency, trials and support.
Glossary#
Action
One supported automation workflow inside a routine.
Concurrency
Maximum farms allowed to execute at the same time.
Evidence
A customer-visible capture or record used to explain a result.
Farm
A VRA identity mapped to an intended LDPlayer profile.
Game availability
Whether the account currently exposes the feature, event, resource, queue or control required by an action.
LDPlayer profile
One local Android emulator environment containing Viking Rise.
No action needed
The farm is already in an acceptable state, such as an active queue or nothing to claim.
Routine
An ordered group of actions and supported preferences assigned to farms.
Run
One execution of an assigned routine for a farm.
Schedule
A rule deciding when a farm routine becomes eligible to run.
Verified outcome
The expected customer-visible change was observed after an action.
Common questions#
Can I use VRA today?
Not publicly. It remains in development; join and confirm the interest list for access news.
What platforms are planned?
Windows with existing LDPlayer profiles. Mac, mobile-only and cloud-hosted game running are not in the current plan.
Is the trial free?
The seven-day trial period will be completely free when trial access launches.
Does joining start the trial?
No. Joining records interest and email consent only.
Can every farm use the same routine?
It can where settings and unlocks fit, but per-farm purpose and game availability often justify different routines.
Can VRA guarantee I will not be banned?
No. No third-party automation can honestly make that guarantee.
Does migration copy GnBots?
No. It previews and translates allowlisted supported configuration, not proprietary software, licences or credentials.
Why was an action skipped?
Settings, limits, active queues, locked features, unavailable events or missing owned resources can all produce a legitimate skip.
Why is a run slower than expected?
Game startup, emulator capacity, unavailable-task checks, pop-up recovery and evidence deadlines can dominate runtime.
What should I send support?
Version, environment, one farm/routine/action, exact outcome, time, relevant redacted evidence and safe reproduction steps.
Still need help?#
Use the evidence checklist before contacting support. A concise report with one reproducible problem is more useful than unrestricted remote access or a large unreviewed data bundle.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.