LDPlayer setup for Viking Rise
LDPlayer is the Android emulator BotDaddy drives. Get this part right and most automation problems never happen; get it wrong and you'll spend your time chasing symptoms.
Install LDPlayer 9
Download LDPlayer 9 from ldplayer.net and install it. Before anything else, make sure hardware virtualization is enabled in your BIOS/UEFI — without it LDPlayer either refuses to start or runs unusably slowly. If Windows is holding the virtualization layer through Hyper-V, see Hyper-V and virtualization errors.
Install and log into Viking Rise once
Install Viking Rise on your first instance and log in manually at least once, all the way to the city view. Get through any first-time tutorial the game insists on.
Doing this by hand once is worth it. It's the cheapest way to be certain the account is in a normal, playable state before automation ever touches it — and a half-finished tutorial is a common cause of an account that mysteriously does nothing.
Set the game to English if it isn't already. The bot reads the screen, and it reads English.
Create your instances
Instances are created in LDMultiPlayer, not in BotDaddy. Open it from the Windows Start menu, its desktop shortcut, or the Multi-player button on a running LDPlayer window.
- New player makes a blank instance — you install the game yourself.
- Clone player copies an existing instance including installed apps.
Set one instance up completely, then clone it for every other account. Cloning is the difference between installing the game once and installing it forty times.
Instance management — Settings, Remove, Backup/Restore — is unavailable while an instance is running. Close it first.
Keep instance settings consistent
The bot recognises the game by what's on screen, so instances that differ from one another in resolution or DPI are instances that behave differently for no good reason. Clone from one known-good instance rather than creating each by hand and configuring it separately.
Cloning gets you this for free, which is the other reason to prefer it.
Performance
Every running instance is a full Android VM competing for the same CPU, RAM and disk. The single biggest performance lever is how many you run at once, not per-instance tuning — see Running multiple accounts.
An SSD matters more than you'd guess. Instances boot, load and screenshot constantly, and on a mechanical drive that's where the time goes.
Rebuilding an instance
LDPlayer instances degrade. They accumulate cruft, and occasionally a virtual disk corrupts outright and the instance stops booting or starts failing in ways that make no sense.
BotDaddy's Rebuild Instances tool wipes and recreates instances with the recommended profile and reinstalls the game. It's the right answer when an instance has gone bad, and the wrong one when you haven't established that it has.
Two things to know: it is destructive — anything on that instance is gone — and it only runs while the bot is stopped. Your account bindings survive a rebuild; BotDaddy repoints them at the recreated instance.
Reach for it when one instance fails repeatedly while its neighbours are fine. That asymmetry is the signal: a problem affecting every account is almost never an instance problem.