Core concepts
Farms, profiles and emulator mapping
How VRA separates a player-facing farm identity from its underlying LDPlayer profile and why mappings must stay explicit.
Three identities to keep separate#
One farm normally maps to one intended LDPlayer profile. Account switching inside the game is a separate capability and must never be assumed solely from a farm name.
Swipe sideways to read all columns, or focus the table and use the arrow keys.
| Identity | Meaning |
|---|---|
| Farm | The name and purpose you use in VRA. |
| LDPlayer profile | The emulator environment containing a Viking Rise installation and its local game state. |
| Viking Rise character/account | The in-game identity visible after the game loads. |
Safe mapping rules#
- Never map two active farm entries to one profile unless the released product explicitly supports that scenario.
- Do not store game passwords, recovery codes or licence secrets in farm names or notes.
- Revalidate mappings after an emulator clone, restore, rename, deletion or major LDPlayer update.
- Keep a farm disabled while its identity is uncertain.
If a mapped profile disappears#
- 1
Do not remap blindly
A newly detected profile with a similar name may not contain the same farm.
- 2
Open LDPlayer manually
Identify which existing profile holds the intended character.
- 3
Refresh Environment Health
Let VRA enumerate the current profile set.
- 4
Update the farm mapping
Confirm the exact target, then run a small validation routine.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.