Start here
Add and verify your first farms
Map LDPlayer profiles to recognisable farms, prevent duplicate mappings and validate a safe first routine.
Identity before automation#
A farm entry is a customer-facing identity mapped to a particular LDPlayer profile. Give it a name you can recognise without opening the game. If two entries point at the same profile, or one profile is rebuilt and receives a new identity, stop and correct the mapping before running.
VRA should never infer that similarly named profiles are interchangeable. Review the proposed mapping and confirm it deliberately.
Add a farm#
- 1
Open Farms
Choose the add or import action in the customer interface.
- 2
Select an LDPlayer profile
Use the detected profile identity, not a remembered numerical index alone.
- 3
Name the farm
Use a stable label such as kingdom, purpose or character—not a password or private recovery detail.
- 4
Assign a small routine
Start with one or two non-premium, easy-to-observe tasks.
- 5
Run and confirm
Watch the first opening and verify the result belongs to the intended farm.
After cloning, renaming or rebuilding LDPlayer#
Treat emulator changes as a mapping change. Re-run environment discovery, confirm which profile is which and review every affected farm before the next schedule.
Do not assume a displayed slot number remains stable after profiles are added, removed, cloned or rebuilt.
Keep farm purpose and LDPlayer profile name consistent. A clear naming convention prevents more support incidents than an elaborate routine can recover from.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.