LD Player Guide

Step 1: Setting up LD Player 4 Emulator

LD Player is a brand of emulator that some people prefer, please follow the guide.

1. Download and install LD Player here: https://www.ldplayer.net/
2. Make sure the emulator you create is in Android 7.1 (recommended but not required) and 64-bit, as Evony is now 64-bit only.
3. Install Evony. Link either your main or alt account and make sure you can load in!
4. Your game MUST be in English. You can change this in the Evony Game Settings.
5. We also recommend disabling game auto-update to prevent any issues with Evony updates.

Step 2: Deleting ADB from LD Player Folder

To prevent conflicts with our own version of ADB, let's delete the one from LD Player. Sometimes Windows will get confused on which to use due to path variables (mine or LD Players).

1. Locate where you downloaded LD Player. You can do this by searching “LD Player” on your pc right click “Open file location”
2. You will most likely see a shortcut. Right click on that and select “Open File Location”
3. Look for adb. Delete it.

Step 3: Set Display Resolution of LD Player

You must set this resolution. Please do as follows.

1. Open up LD Player settings and go to Advanced Settings.
2. Under resolution setting, set mobile.
3. Set the resolution to 540x960, 240 DPI or 396x704, 132 DPI under customize option
4. Click Save, restart if asked.

Step 4: Enable Android Debug Bridge (ADB)

Wow, ADB! This will allow my program to control the LD Player instance.

1. Under LD Player settings, go to the Other Settings tab.
2. Look for ADB Debugging, you want to enable this.
   1. Select: Open Local Connection
   2. Click save, restart if asked.

Step 5: Setting up performance on your Emulator

Emulators take up power on your machine. Imagine if your phone was on your computer. It will require some of your own computer’s resources. This is why you need a computer with modern hardware with decent specifications.

1. Under LD Player Settings, go to the Advanced Tab.
2. Under CPU, set it to 1 core.
   1. Evony doesn’t need more than 1 to run.
3. Under RAM, set it to 2048M
   1. You don’t need more than 2048M, believe me.
4. Click Save changes. Restart if asked.

Step 6: Android Debug Bridge (ADB) - Finding Port Numbers

LD Player doesn’t tell you the ports. You have to sometimes find them yourself. However, it is pretty easy to find the pattern! You need these ports to connect with ESB.

You can use the port scanner on the bot to automatically find the ports for you, however I believe the concept of ports is very important for you to understand, or you won’t know what emulator belongs to what port!

A. LD Player Port Pattern Explanation

LD Player follows a pattern when setting up port numbers. You must understand this SIMPLE pattern.

The first LD Player emulator you open will have its own port and it won’t change, just like in bluestacks.

The first port starts at: 5555

It then increments by two after:

So for four instances, the port values would be:

5555

5557

5559

5561

And so on…

B. Using Port Scanner on ESB

The bot application can help you find open ports, simply open the bot application and review the ports listed. Click on a cell in the table to refresh the list anytime for new ports.

C. Take advantage of naming in LD Multi-Drive

1. Rename each instance to its correct port value so you can remember which instance belongs to which port. Also, please open one at a time, every new NOX instance that hasn’t been opened before will have its own port number. So to ensure order of the pattern explained above, just open each for the first time in order!

D. Verifying those ports exist (Optional, in case you can’t find the specific port number)

We want to check that the ports exist. Open up all your emulator instances first. After that, search for “Powershell” on your Windows PC.

1. In powershell, paste this command:

   get-nettcpconnection | select local*,remote*,state,@{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}} | Sort-Object LocalPort | Where-Object {($_.Process -like "*ld*" -and $_.LocalPort -gt 5554 -and $_.RemoteAddress -like "*0.0.0.0*")}
   

2. You will see a result like below. Keep in mind, it MUST follow the pattern! The first port starts at 5555. Notice how you see 53831, 55387, 53578, that doesn’t follow the pattern, that isn’t correct. You can see the correct port below at 5555. So that port is open and ready to connect with ESB!

Step 7: Opening and Logging into the Bot (ESB-TKR)

The moment you’ve been waiting for.

1. Continue the guide: Part 1: How to Prepare to Install ESB-TKR