BotDaddyBotDaddy
All guides

Viking Rise bot setup

This guide takes you from a fresh install to a Viking Rise bot running its first automated cycle. It should take about fifteen minutes, most of which is LDPlayer downloading things.

If you already run LDPlayer with the game installed, skip to Connecting LDPlayer.

What you need first

  • Windows. BotDaddy is Windows-only, because LDPlayer is.
  • LDPlayer 9 with Viking Rise installed and logged in at least once.
  • Hardware virtualization enabled in your BIOS/UEFI. Without it LDPlayer runs at a crawl or refuses to start.
  • A BotDaddy licence key, which arrives by email after checkout.

One LDPlayer instance per account is the model. How many instances you can keep is a question of disk space; how many can run at once is a separate question, covered below.

Installing BotDaddy

Run the installer and launch the app. It opens on the Overview dashboard; before anything else, go to License in the sidebar.

Paste your licence key and activate. The key binds to this machine, which the License page shows alongside your renewal date — so activating on a second computer needs the key freeing from the first. If you've lost the key, it's on your account page, masked, with a regeneration option.

Regenerating replaces the old key. The app on any machine still holding it will stop validating, so only regenerate if you actually can't recover the original.

Connecting LDPlayer

Open Settings and set the LDPlayer path. This is the folder containing ldconsole.exe — typically C:\LDPlayer\LDPlayer9. In the desktop app you can browse for it directly.

BotDaddy talks to LDPlayer through ldconsole and ADB rather than clicking on your desktop, so the emulator windows don't need to be visible or focused. You can keep working while it runs.

While you're in Settings, the Runtime control sets how many accounts run at the same time. This is concurrency, not how many accounts you can have — you can add as many accounts and instances as your disk holds, and this decides how many of them are awake at once.

It's the setting that matters most for stability, and there is no correct number we can give you: it depends on your CPU, RAM, disk speed and what else the machine is doing. Find it by testing. Start low, watch a full cycle complete, raise it a step, watch again. When boots start timing out or cycles get noticeably slower, you've gone one step past your limit — come back down.

Every concurrent account is a full Android VM, so the usual failure mode for a new setup is running more at once than the machine can actually boot. Fewer accounts that finish reliably beats more that thrash.

The timeouts on that page (instance start, game process, game ready) exist for slow machines. Leave them alone until something times out repeatedly.

Creating LDPlayer instances

Each account needs its own LDPlayer instance, and instances are created in LDMultiPlayer, LDPlayer's own multi-instance manager — not in BotDaddy.

You can open it any of three ways:

  • Search for LDMultiPlayer in the Windows Start menu.
  • Use the LDMultiPlayer desktop shortcut, created when you installed LDPlayer.
  • Click Multi-player on the right-hand toolbar of a running LDPlayer window.

The first two don't need LDPlayer open, which makes them the easier route when you're setting up a batch of instances.

Two ways to add one:

  • New player creates a blank instance with no apps installed. You then install Viking Rise on it and log in once.
  • Clone player copies an existing instance, including everything installed on it.

Clone is almost always the one you want. Clone from an instance that already has Viking Rise installed and you skip the download and install on every subsequent account — you only need to log into the right account on the copy. Set one instance up properly first, then clone it as many times as you need.

LDMultiPlayer also has batch controls for adding, cloning and starting several instances at once, which is worth knowing about if you're building a farm rather than adding one account.

Two things to expect:

  • Instance management is unavailable while an instance is running. Settings, Remove and Backup/Restore are all greyed out until you close it. Close instances before reorganising them.
  • How many instances you can keep is a disk-space question. Each one is a full Android VM with its own copy of the game. Whether they can all run at once is the Runtime concurrency question from earlier, and the two limits are unrelated.

Give each instance a name you'll recognise in BotDaddy's account list. Renaming later is safe — accounts bind to the instance itself, not its name — but it saves you matching numbers.

Adding your first account

On the Accounts page, add an account and bind it to an LDPlayer instance. The binding is by instance, not by name, so renaming an instance in LDPlayer later won't break it.

Then pick the actions that account should run. Each action has its own config, and most have sensible defaults — gathering, dailies and training are the usual starting three. Actions run in the order you arrange them, so put the time-sensitive ones first.

Each action can also carry a schedule, if you want it gated to certain days or a time window. Leave scheduling off for your first run; it's one more thing to be wrong while you're still confirming the basics work.

Your first run

Hit start. The bot boots the instance, launches the game, waits for the city view, and begins working through the actions you enabled.

Watch the first cycle rather than walking away. The activity feed narrates what's happening in plain language, and the per-account logs in Documents\BotDaddy carry the detail if something needs chasing down.

A healthy first run looks like: instance starts, game launches, the account reaches its city, and actions begin completing one after another. A restart or two along the way isn't a problem — the bot restarts an instance rather than pushing through a state it doesn't recognise, and picks up where it left off.

When something doesn't work

LDPlayer won't start at all. Almost always Hyper-V or another hypervisor holding the virtualization layer. The in-app virtualization assistant detects and walks you through this.

The bot can't find your instance. LDPlayer reassigns indices after some rebuilds. Restarting the bot re-reads the current list and fixes it.

Everything is slow, or instances time out. Too many accounts running at once for this machine. Lower the Runtime concurrency in Settings by a step and see whether cycles complete cleanly again.

Actions fail on one account but not others. Usually that account's game state rather than the bot: an unfinished tutorial step, a modal the game won't dismiss, or a building the action needs that isn't built yet.

Next steps

  • Tune gathering so every march slot stays busy — see Automating gathering.
  • Scale past one account — see Running multiple accounts.
  • Anything unexplained: the support page usually gets a reply within a few hours.