Phiên bản 2.1.0.5 (TƯƠNG THÍCH BLUESTACKS VÀ CERBERUS)
Evony Smart Bot Version 2.0.9.5 less-intensive CPU version of the bot
I am excited to announce a much ligher, quicker, and less-intensive CPU version of the bot! It will require a new resolution change, so please follow instructions accordingly! There is a 400% performance improvement
I very much appreciate the people who helped me test the past couple of days! This will work much better on slower pcs, and even better on faster ones! There may or may not be issues, but if you run into them, let me know and ill get it fixed.NOX Guide
English versionStep 1: Setting up NOX Emulator
NOX is a brand of emulator that some people prefer, please follow the guide.
- Download and install NOX here: https://www.bignox.com/
- When creating a new instance, make sure it is on Android Version 7 Recommended Version!
- Install Evony. Link either your main or alt account and make sure you can load in!
- Your game MUST be in English. You can change this in the Evony Game Settings.
Step 2: Deleting ADB from NOX Folder
To prevent conflicts with our own version of ADB, let's delete the one from NOX. Sometimes Windows will get confused on which to use due to path variables (mine or NOX).
- Locate where you downloaded NOX. You can do this by searching “NOX” on your pc right click “Open file location”
- You will most likely see a shortcut. Right click on that and select “Open File Location”
- Look for adb. Delete it.
Step 3: Set Display Resolution of NOX
You must set this resolution. Please do as follows.
- Open up NOX settings and go to Performance Settings.
- Under resolution setting, set mobile.
- Set the resolution to 1080 * 1920
- Click Ok. Restart if asked.
Step 4: 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.
- Under NOX Settings, go to the Performance Tab.
- Select Low (1 Core CPU, 2048MB Memory
- Click Save changes. Restart if asked.
Step 5: Android Debug Bridge (ADB) - Finding Port Numbers
NOX is different from Bluestacks in that it has ADB enabled automatically for you. However, it doesn’t tell you the port numbers. 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. NOX Port Pattern Explanation:
NOX follows a pattern when setting up port numbers. You must understand this SIMPLE pattern.
The first NOX emulator you open will have its own port and it won’t change, just like in bluestacks.
The first port starts at: 62001
After, the port moves to 62024, and increments by one after.
So for four instances, the port values would be:
62001
62024
62025
62026
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 NOX Multi-Drive
- 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.
- 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 "*NOX*" -and $_.LocalPort -gt 62000 -and $_.RemoteAddress -like "*0.0.0.0*")}
- You will see a result like below. Keep in mind, it MUST follow the pattern! The first port starts at 62001. Notice how you see 63001, 64001, that doesn’t follow the pattern, that isn’t correct. You can see the correct port below at 62001. So that port is open and ready to connect with ESB!
Step 6: Opening and Logging into the Bot (ESB-TKR)
The moment you’ve been waiting for.
- Continue the guide: Part 1: How to Prepare to Install ESB-TKR
LD Player 4 Guide
English versionStep 1: Setting up LD Player 4Emulator
LD Player is a brand of emulator that some people prefer, please follow the guide.
- Download and install LD Player here: https://www.ldplayer.net/
- Install Evony. Link either your main or alt account and make sure you can load in!
- Your game MUST be in English. You can change this in the Evony Game Settings.
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).
- Locate where you downloaded LD Player. You can do this by searching “LD Player” on your pc right click “Open file location”
- You will most likely see a shortcut. Right click on that and select “Open File Location”
- Look for adb. Delete it.
Step 3: Set Display Resolution of LD Player
You must set this resolution. Please do as follows.
- Open up LD Player settings and go to Advanced Settings.
- Under resolution setting, set mobile.
- Set the resolution to 1080 * 1920
- Click Save, restart if asked.
Step 4: Enable Android Debug Bridge (ADB)
- Under LD Player settings, go to the Other Settings tab.
- Look for ADB Debugging, you want to enable this.
- Select: Open Local Connection
- 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.
- Under LD Player Settings, go to the Advanced Tab.
- Under CPU, set it to 1 core.
- Evony doesn’t need more than 1 to run.
- Under RAM, set it to 2048M
- You don’t need more than 2048M, believe me.
- 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 NOX 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
- 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.
- 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*")}
- 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.
- Continue the guide: Part 1: How to Prepare to Install ESB-TKR
Collective Guide for Farming
English versionIntroduction
The Collective is an amazing way to share information between other bot users and multiple computers. For example, if you have run the bot on two computers, you can share information between the two, such as tiles. Only level 15 tiles will currently be shared to the collective.
This means you can have other people help you in the search for tiles, so that you can use farming mode much more efficiently! Always stay loaded up on level 15 tiles by having everyone contribute to the collective.
Make sure to enable “send to collective” in farming mode!
Remember, the collective is a team effort! The point is to have other people helping contribute - or if you use the bot on multiple machines, so that they can communicate with eachother!
How to Use
Follow the steps below to understand and take advantage of the collective
- Go to the collective tab.
- Enter in a key that someone gave to you OR generate your own.
- To use the same pool of tiles shared from another user, enter in their collective key.
- Any user who enters the same key as you will have their tiles shared to your collective. You both can then pull those tiles using farming mode. This helps increase efficiency as other people you know can help you spot level 15 tiles!
Collective Guide for Bossing
English versionIntroduction
The Collective is an amazing way to share information between other bot users and multiple computers. For example, if you have run the bot on two computers, you can share information between the two, such as bosses.
This means you can have other people help you in the search for bosses, so that you can use Auto-Setter much more efficiently! Always stay loaded up on bosses by having everyone contribute to the collective.
Make sure to enable “send to collective” in auto-setter and boss-finder!
Remember, the collective is a team effort! The point is to have other people helping contribute - or if you use the bot on multiple machines, so that they can communicate with eachother!
How to Use
Follow the steps below to understand and take advantage of the collective
- Go to the collective tab.
- Enter in a key that someone gave to you OR generate your own.
- To use the same pool of bosses shared from another user, enter in their collective key.
- Any user who enters the same key as you will have their bosses shared to your collective. You both can then pull those bosses using auto setter. This helps increase efficiency as other people you know can help you spot bosses!