CloudBot is high quality automation software run on the virtual machines. It uses screen recognition, simulate mouse/keyboard inputs, artificial intelligence and machine learning to act like a human.

There is no download link. Nobody has direct access to the software except the creator. Cloudbot is run in virtual private servers which makes all of us safe from BattlEye. Everything is managed on the CloudBot Console and there's no need to have your PC running.

To use the CloudBot, you have to download VNC client eg. TightVNC or VNC Viewer and connect to the machine using IP address and password.

CloudBot is on market since 2019 and so far has been caught by BattlEye only twice - in summer 2020 and spring 2021. After each mass ban, CloudBot has been strongly reworked and it takes really long time for BattlEye to detect it again.

Moreover, CipSoft has also ability to detect any bot based on how your character act in game. To minimalize the risk of banishment you should:

• bot suitable amount of hours everyday (8-10 hours per character is enough)
• 1 character per account
• avoid reports (choose less crowded spawns)
• pick less popular worlds (less players, less reports, more spawns for you)
• be nice to other players (make them think you're real person)

Depending on the amount of hours and payment method, the pricing is:

Available payment methods: Transfer in-game (Tibia Coins), PayPal (USD) and BLIK (PLN).

Purchase link and more information can be found here: https://cloudbot.mv-scripts.com/cloudbot

The way the license time expires has been significantly changed in the last CloudBot update. Additionally, the possibility of pausing the license has been implemented. Removing all machines from your key will prevent losing license time.

From now, you can assign any number of machines to your key. The number of currently assigned machines will have an impact on how the bot hours are billed to us.

For each assigned machine, regardless of whether we are currently botting or not - we lose 1 hour from our license, e.g.

• having 1 virtual machine assigned, we lose 1 hour of the license every hour.
• having assigned 3 virtual machines, we lose 3 hours from the license every hour.
• without having a virtual machine assigned, time is stopped.

Machines can be assigned to or removed from our key at any time, so if we do not have such a need, we can get rid of them. Note that the number of machines is limited, so there will be times when no machine is available.

One machine is guaranteed for each key purchase, so you don't have to worry about it at the start.

CloudBot is not intended to be used as heal bot or other support. It's not even run on your PC and playing on it via VNC client is inconvenient. Thus what CloudBot has to offer?

• Full AFK CaveBot that is capable to walk based on the waypoints, deposit items, withdraw items from depot or stash, refill supplies and ammunition based on setup and so on...
• Targeting (fast targeting on Battle List)
• Quick looting (about 99% picked loot)
• Advanced Healing (support all kind of potions and spells)
• Advanced persistent actions (eat food, equip items, move ammunition to quiver, lure monsters etc.)
• Discord Alerts (player on screen etc.)
• Running in VPS (no need to have your PC online)

Before you actually obtain a CloudBot License, you should prepare your environment first. Start by downloading needed tools, here's the list:

• Text Editor - the standard Windows Notepad is theoretically enough, but you're going to edit setup files a lot. It's recommended to use more advanced code editor with colour syntax. The most popular choice is Notepad++, but there's a lot of alternatives available.
• VNC Client - in order to connect to the CloudBot, we need a VNC Client. It's recommended to use VNC Viewer. Later, when you get familiar with bot, you can connect to CloudBot using VNC Viewer on your mobile phone (Android/IOS) or any other device that has connection to the internet.

Downloaded everything? All right, now another important thing.

The next step is to show file extensions on your PC. Type in google show file extenstions and find tutorial for your system.

Don't forget to prepare your characters earlier. It's highly recommended to bot 3 or 4 characters per license. Buy cheap characters from Tibia Char Bazaar. Don't waste time and money making them from zero.

CloudBot is available only on two regions - North America and Europe. Location of bot should be based where your characters are in game.

• Are you planning to bot on Europe worlds in Tibia? Choose Europe server.
• Are you planning to bot on North America or South America worlds in Tibia? Choose North America server.

It does not really matter where do you live. You can be anywhere in the world, but Tibia and CloudBot are running on VPS thus your internet connection does not have any impact on bot.

CloudBot offers 180, 360 and 720 hours licenses. Choose amount of hours according to your needs, although 720 hours is the most cost-effective. Refill license option is used for adding hours to existing license - for now, ignore it. You need to get your own License Key first.

Ready to buy? Visit https://cloudbot.mv-scripts.com/cloudbot and make an order for new license.

E-mail comes with some details about your order.

• Order ID is our internal id for tracking all orders:
• License hours is the amount of hours of your license.
• Region is the location of your machine.
• User ID is generated user id by CloudBot that is used for refilling license and identifying machines.

Remember to save your license key!

Click on the Generate License Key button or go to the link from e-mail. You will get redirected to the CloudBot website where you have to make captcha to get your key.

Please note that, your license time starts to count from the moment you receive an e-mail with the generated link, thus generate your key and start to use bot as soon as possible.

Remember to save your license key!

From now your license key (the one you generated in step before) is your login to the CloudBot console. Visit https://cloudbot.site/login, type your CloudBot Key and then press enter button to login to the console. It's good to remember it in your browser to have it saved, so there's no need to retype it everytime you wants to login.

The first thing you must do after purchasing a license is to Start your machine. To do that, on the sidebar, go to the Configuration page or visit this URL direcly: https://cloudbot.site/key_configs

Now press the Start button (red circle) like on screenshot below. If you have error Failed to Reboot - please try again untill it works.

Moreover:

• The Add Machine button will redirect us to a page where we can assign new machines to our key.
• In case we want to get rid of the machine, click the Unassign button.
• If you want to use your own proxy, click on the three dots (...) in the last More column.

Great! If everything went OK, you should see the Password to your virtual machine. From now you will see a Reboot button, instead of Start button, to restart the virtual machine (to fix potential problems) or change your password. You will not lose any data or settings by doing that. Ignore the rest options on this page. You will learn about it in further steps.

Use the VNC Client to connect to your virtual machine. Depending on VNC Client you have downloaded, use IP Port (green circle) and Password (blue circle) as credentials like on screeshot below and connect to the server.

Authetication to connect VM using TightVNC Viewer.

After connecting to the virtual machine, you should see blue screen (depending on the picture quality, it might be blue-green egg). That means you have succesfully connected. You can move now towards next step.

Background of working virtual machine.

In previous step, we didn't launch Tibia and CloudBot, but only connected to the virtual machine. In order to do that, we have to first create a configuration on CloudBot website which will contain setup and waypoints of the script you would like to run.

• What is this setup then?

• Where can I find this setup file?

• How can I edit the setup?

• What can be done in setup?

• What about waypoints then?

Going back to the merits, login again to the CloudBot console and go to the Start page on sidebar. Press now New Config button.

Form to add a configuration with the script.

First, we need to name our script. In Config Name type the name of your script. It's up to you how you call it, can be name of spawn, character or both so you can remember later what script you have uploaded.

Second part with Category is divided into three options:

• Official Scripts (free) - choose the script by its name and it will fetch waypoints from github repository. Setup to the script can be found here. They are mostly maintained by creator of the CloudBot.
• User Scripts (free) - choose the script by its name and it will fetch waypoints from github repository. Setup to the script can be found here. They are mostly maintained by the community of the CloudBot.
• Custom Script (free or paid) - upload waypoints file on your own. This is where you have to upload waypoints from paid scripts or made by yourself/someone.

The next and last thing is Setup. As already explained above, get the setup to the script and upload it. Make sure it's in .json extension. Sometimes it might be in .txt extension because you saved it wrong and didn't enable the option to see file extensions on your system.

Few basic things you should know:

• hours_leave in "script_options" section - the hour bot should leave spawn and go trainers based on CET time zone. By default most of the scripts has this value set to [9], which means bot will go trainers at 9:00am CET (1 hour before server save). It accept few values, so if you set [8, 18] that means bot will go trainers at 8:00 am CET or 6:00 pm CET.
• gold_bp / loot_bp in "containers" section - name of your backpacks needed for bot to deposit items properly. If it's PACC script then gold_bp is not required to provider its name in setup.
• in "hunt_config" section we can set up the cap_leave and amount of supplies needed to go to the hunt and leave spawn. If you would like to change the name of potions, you have also change its name and id in "items" section.

Ignore the Auto Start option. We will focus on it later. Now you must get familiar with CloudBot. This is just an addon, not required especially when you haven't configurated Tibia yet.

Press now Save button.

If you get message You setup configuration has errors that means your setup file is invalid. To solve the problem, paste your setup on this website and find the error.

Login again to the CloudBot console and go to the Start page on sidebar. If you have succesfully created configuration in previous step, you should see all of your configurations like on screenshot below.

Configurations for two different scripts.

From now, you can:

• Edit your configuration
• Duplicate your configuration
• Remove your configuration

To run a given script, go to the main console page (by going to Status in the menu). We should see a list of our machines, where they contain information such as: IP and port, password and location.

List of assigned machines

At the end of each machine, there is a Start Bot button, which redirects us to a subpage where we can start the script on a chosen machine.

Starting scripts from the list..

Apart from the possibility to edit, duplicate or delete the script, in this case the most important buttons are:

• Start New button - launch Tibia and CloudBot on chosen virtual machine.
• Reload button - reload only CloudBot on your virtual machine . It doesn't restart Tibia. Hotkeys will not update if you want to use different script on same Tibia.

Press Start New button on the configuration you want to start and connect to your virtual machine using VNC Client. Tibia should start together with the CloudBot. Login now to the game on virtual machine. Do not press Setup yet - you have to setup your client and save changes before you run the script.

First thing you need to do is to open second sidebar like on screenshot below.

Recommended setup of Tibia

Explanation:

• (1) required Open Battle List and move it to the left sidebar. Sort Ascending by Distance and hide everything expect Monsters. Remember to close buttons and expand it to see at least 10 creatures.
• (2) optional Create new Battle List, rename it to Player List and move it to the left sidebar below current Battle List. Hide everything expect creatures you want have alerts on. Remember to close buttons and there is no need to expand it.
• (3,4) required Put backpack for loot (Green Backpack) and gold backpack (Golden Backpack) to your main backpack. Open it like on screenshot and make sure you have same backpacks names as you provided in script setup.
• (5) optional Put additional backpack for extra stuff such as brown mushrooms, rings, amulets, potions etc. to your main backpack and open it like on screenshot.
• (6) optional Open Hunt Analyzer and any other tracking features Tibia offers. This is not required at all, but it's nice to know if everything is going as expected.

If you're botting on FACC account and you use manual looting type, you must provide name of your gold backpack in Setup and open them like on screenshot below. Bot will move gold from corpses to these backpacks.

Golden backpacks for manual gold looting

It is very important to have enough spaces for deposit and trade windows otherwise bot will fail to refill and logout!

We have our windows and sidebars setup in Tibia. Now we have to tell Tibia where should our loot and items/supplies from stash end up. Right click on any backpack in-game and press Manage Loot Containers.

Manage Loot Container in game

• (1) Unassigned Loot container should be pointing to your backpack for loot (loot_bp in setup).
• (2) Gold container should be pointing to your backpack for gold (there's no need to provide it in setup).
• (3) Retrieve container (scroll to the bottom to find it) should be pointing to your main backpack or extra backpack if using. All items that are withdrawn from stash will end up in this container.

We have completed windows and sidebars setup. We have told Tibia to which backpacks it should move items. Now we have to tell Tibia what items we want to loot. This can be done using Quick Loot Filter in game. It is possible to:

• add items to the the Skipped Loot list that we do not want to loot (default in game and recommended approach)
• add items we want to loot in the Accepted Loot list (not recommended, it is usually more items should to be looted, than skipped)

In order to do that, open Cyclopedia in game and search for the item by its name and then in the right-bottom click Skip when Quick Looting.

You have to search for all non-valuable and trash items that monsters drop and skip them that way. If you would like to accept loot instead, you have to switch Loot Filter in Manage Loot Container to Accepted Loot. From now you will be able only to add items that you want to loot.

All paid scripts by MvScripts comes with two files named: skipped_loot.txt and accepted_loot.txt. They are generated by our system and contain selected items to either Skip or Accept. There's no need to waste your time and search for all possible items to either skip or accept.

If you have completed everything wrote above, relog in game to save your changes on your virtual machine. Now you can press Setup and Run to start the bot.

• Press l (small L) to show FPS and ping.
• Lower quality of your VNC Client in favour of performance.
• Watch your bot on view-only mode to don't interupt it by mistake.
• It's possible to connect to the virtual machine on your mobile phone using VNC Viewer application.
• Close all running VNC Client processes in your system to stop the BattlEye kicks.
• VNC viewer can be closed and bot will continue running.

After purchasing the license, we can assign our Discord account to CloudBot. We will gain access to all channels that are available only to current CloudBot users.

The first step is to join on official CloudBot discord server.

Form to gain acccess to customer discord channels.

In the text field, paste your Discord nickname (example nick: kaden#1234), and then press the Add Role button.

From now on, we should have access to all channels on Discord. If we still do not see them, please try again. Sometimes there may be some delays.

This guide will cover two scenarios:

• Alert when Player on Screen everywhere, even in city (requires only modification of your setup)
• Alert when Player on Screen in specified section eg. only on spawn (requires modification of your setup and waypoints - recommended)

1. Get your Discord User ID (follow this tutorial: https://techswift.org/2020/04/22/how-to-find-your-user-id-on-discord/)

Discord User ID is not your nick! It is a sequence of numbers, example: 58923340853761314 (it has about 18 numbers)

2. Open your setup.json file on your computer in any text editor or edit directly in CloudBot Console, copy code below and paste to your general section in setup like in example screenshot.

                "use_player_list": true,
                "discord_user_id": "your_discord_user_id",
                "session_name": "name_of/your_script"
            

Replace your_discord_user_id with your Discord User ID (from step 1) and name name_of/your_script however you want. Pay attention to the commas at the end of each line!

If you want to use Retro Safe Option, replace "use_player_list" with "retro_safe"

Player on screen settings in setup.json

Next, thing: Add this at the beginning of persistent_actions section in setup like in example screenshot.

               {
                  "alias": "alert_player_on_screen_alias",
                  "action": "alert_player_on_screen",
                  "interval": 6
                },
            

Required action for alerts in setup.json

3. Create additional Battle List in Tibia and:

• rename it to Player List
• hide monsters, npcs etc.
• show only creatures you want have alert on (players etc.)

From now you should get messages from CloudBot Bot when you:

• start a script
• see player on screen
• finish script

4. Enable Alert only on spawn.

First thing we need to is to increase interval of the player on screen alert action that we previously added in setup. To do that, set interval value to high number eg. 999999999 and save changes. Check example below:

                {
                  "alias": "alert_player_on_screen_alias",
                  "action": "alert_player_on_screen",
                  "interval": 999999999
                },
        

In order to do that, edit your waypoints file on your computer in any text editor or edit directly in CloudBot Console. If you are using free script or your waypoints are encrypted, you must copy your waypoints from github repository or contact the creator of script to help you out.

Paste line below to your waypoints file from which waypoint you want to receive alert in your script. Check example of screenshot below.

call set_persistent_interval("persistent_alias": "alert_player_on_screen_alias", "interval": 6)

Alert will be enabled only on spawn.

Paste line below to your waypoints file from which waypoint you do not want to alert in your script. Check example of screenshot below.

call set_persistent_interval("persistent_alias": "alert_player_on_screen_alias", "interval": 999999999)

Alert will be disabled when leaving the spawn.

That's all from now you will get messages on your discord only during the hunt. Happy botting!

Alerts messages on discord sent by CloudBot Bot.

This guide will cover feature to leave spawn and go trainers when player comes to your spawn. (requires modification of your setup and waypoints)

It can be used together with Player Alerts.

1. Open your setup.json file on your computer in any text editor or edit directly in CloudBot Console, copy code below and paste to your general section in setup like in example screenshot.

                "use_player_list": true,
            

If you want to use Retro Safe Option, replace "use_player_list" with "retro_safe"

Enable player list in settings in setup.json

Next, thing: Add this at the beginning of persistent_actions section in setup like in example screenshot.

            {
                "alias": "leave_player",
                "action": "conditional_jump_player_on_screen",
                "interval": 999999999,
                "use_in_battle": true,
                "args": {
                    "go_train": true,
                    "threshold": 10
                }
            },
            

Required action for player leave in setup.json

2. Create additional Battle List in Tibia and: (you can skip this if you already have one for Player Alert)

• rename it to Player List
• hide monsters, npcs etc.
• show only players you want to leave (skulled, non-skulled etc. up to you)

For now, player leave action is by default disabled. We will now enable it only on spawn.

3. Enable Player Leave only on spawn.

In order to do that, edit your waypoints file on your computer in any text editor or edit directly in CloudBot Console. If you are using free script or your waypoints are encrypted, you must copy your waypoints from github repository or contact the creator of script to help you out.

Paste line below to your waypoints file from which waypoint you want to leave spawna nd go trainers. Check example of screenshot below. (it's recommended to add it right after label hunt)

call set_persistent_interval("persistent_alias": "leave_player", "interval": 3)

Player Leave will be enabled only on spawn.

Paste line below to your waypoints file from which waypoint you do not want to go trainers. Check example of screenshot below. (it's recommended to add it right after label leave)

call set_persistent_interval("persistent_alias": "leave_player", "interval": 99999999)

Player Leave will be disabled when leaving the spawn.

That's all from now your character will go trainers if anyone comes to your spawn and this action won't be triggered in city. Happy botting!