BotDaddyBotDaddy
All guides

System requirements

Worth two minutes before you buy a licence or rent a machine. Most of this is the same hardware LDPlayer itself needs, but there is one requirement that stops BotDaddy dead with no warning, and it catches people out.

The short version

  • Windows 10 or 11, 64-bit
  • A CPU with AVX2 — Intel from 2013, AMD from 2015. This one is non-negotiable and there is no workaround.
  • Hardware virtualization enabled, and Hyper-V turned off
  • A real graphics card
  • 4 GB of RAM and around 6 GB of disk per emulator instance
  • LDPlayer 9 or LDPlayer 14

If you already know your machine is modern and you game on it, you are almost certainly fine. Read on if you are buying, renting, or reusing an older PC or server.

Processor: AVX2 is required

BotDaddy's engine is compiled to use AVX2, a set of CPU instructions introduced in 2013. Without it the engine cannot start at all — the app window never opens, and restarting or reinstalling changes nothing.

You have AVX2 if your CPU is:

  • Intel Core i3 / i5 / i7 / i9 — 4th generation (Haswell, 2013) or newer. The generation is the first digit or two after the dash: an i7-4770 is 4th gen and fine, an i7-3770 is 3rd gen and is not.
  • Intel Xeon E5 — v3 or v4 only. A Xeon E5 with no version suffix, or a v2, is too old. This trips people renting cheap dedicated servers, which are very often the 2012 generation.
  • AMD Ryzen, Threadripper or EPYC — all of them.

You do not have AVX2 if your CPU is an Intel Pentium or Celeron, whatever year it was made. Intel disables these instructions on those chips even on otherwise-modern designs.

How to check in ten seconds

Press the Windows key, type powershell, open it, then paste this in and press Enter. It only reads information — it changes nothing:

Add-Type -Name F -Namespace Bd -MemberDefinition '[DllImport("kernel32.dll")] public static extern bool IsProcessorFeaturePresent(uint f);'; (Get-CimInstance Win32_Processor).Name; 'avx2=' + [Bd.F]::IsProcessorFeaturePresent(40)

If it prints avx2=True you are good. If it prints avx2=False, that machine cannot run BotDaddy and no setting will change that.

Windows

Windows 10 or Windows 11, 64-bit. BotDaddy runs as administrator — Windows will prompt you on first launch — because the virtualization tools and a few other things need it.

Windows Server works, but see the note on rented servers below.

Virtualization

LDPlayer runs Android in a virtual machine, so your CPU's hardware virtualization must be enabled in BIOS (called Intel VT-x, AMD-V or SVM Mode) and Windows must not be holding it for itself.

That second part is the common one: Hyper-V, Memory Integrity, VBS, WSL2 and Docker Desktop all claim the same layer, and LDPlayer then runs at a crawl or not at all. BotDaddy includes a Disable Virtualization tool that turns these off in one pass and backs up your settings first.

The full walkthrough is in Hyper-V and virtualization errors.

Graphics

You need a real graphics card — anything from the last decade, integrated Intel or AMD graphics included. LDPlayer renders the game, and BotDaddy reads the screen.

What does not work is a machine with only basic server or management graphics, which is what most rack servers have. The emulator will start and then run far too slowly to be useful.

RAM, CPU and disk

BotDaddy configures each emulator instance with 4 GB of RAM and 3 CPU cores, at 640×480. Installed, each instance takes roughly 6 GB of disk on LDPlayer 9 and a little more on LDPlayer 14, plus whatever the game grows to.

An SSD is effectively required. Instances read their disk images in full every time they boot, and on a mechanical drive a fleet spends its day waiting on that.

How many accounts can I run at once?

RAM is usually what stops you first. A rough starting point:

  • 16 GB — 2 to 3 instances
  • 32 GB — 6 to 7 instances
  • 64 GB — 14 to 15 instances

That is instances running simultaneously, not accounts. BotDaddy cycles through as many accounts as you like on far fewer instances, so a 16 GB machine can happily farm dozens of accounts — it just works through them in batches.

Treat the table as a ceiling rather than a target. A weaker CPU or a slower disk will bind before RAM does, so start a few below the number and raise it while watching how the machine copes. You can change it any time in Settings.

Can I run it on a VPS or rented server?

Sometimes, and there are three things to confirm with the provider before you pay — any one of them will stop you:

  1. CPU generation. Ask for the exact model and check it against the list above. Cheap dedicated servers are very often 2012-era Xeon E5s with no AVX2.
  2. Nested virtualization. On a virtual server, the host has to allow the guest to use virtualization. Many providers do not, and LDPlayer then cannot start at all.
  3. A real GPU. See above — most rack hardware does not have one.

Also worth knowing: some virtual servers present an older "compatible" CPU to the guest, which hides AVX2 even though the real hardware has it. If the check above says avx2=False but the CPU name looks modern, ask your provider to set the VM's CPU type to host passthrough, or to turn off CPU compatibility masking.

Antivirus

BotDaddy and LDPlayer both read and write constantly, and real-time scanning sits in front of all of it. BotDaddy can add Windows Defender exclusions for the folders involved — it asks first and never changes your antivirus settings on its own. It makes a real difference to speed on a busy fleet.

Still not sure?

Get in touch with your CPU model and how many accounts you want to run, and we will tell you straight whether the machine will cope.