OGame Bot
TBot is a .NET 5 OGame bot based on ogamed deamon by alaingilbert
TBot supports Ogame v8.7!
Feel free to publish issues or pull requests
Scripting and botting are forbidden by the OGame rules. I adopt a series of measures to prevent detection and thus ban, but I cannot, and never will, guarantee anything. Use this bot at your own risk!!
Testing and PR are very much appreciated!
Do you like the project? Buy me a beer!
TBot has a wide variety of useful features. They all can be configured and customized editing settings.json. Here follows a shot explaination of each of them:
- Defender: TBot checks periodically for incoming attacks
- Autofleet: TBot dispatches your endangered fleet and resources on the safest mission possible
- MessageAttacker: TBot sends a message to the attacker(s). The message is picked randomly from the array given in settings.json
- SpyAttacker: TBot automatically spies attacker with set number of probes
- Alarm: TBot plays a nasty sound if under attack
- TelegramMessenger: TBot sends you a notice if under attack (requires additional configuration, see below)
- Expeditions: TBot will handle them for you
- TBot can automatically optimize expeditions for your account, sending them from one or multiple origins. Military expos are supported too, by adding a ship type to the automatically calculated optimal fleet or by manually setting the desired fleet.
- Brain: TBot has a series of extra functionalities
- AutoCargo: TBot checks wether your celestials have enough capacity to displace the resources. If not, TBot builds ships for you (preferred type taken from settings.json)
- AutoRepatriate: TBot periodically repatriates all your resources to a single drop celestial. You can also specify to leave a set amount of deuterium (only on moons or both moons and planets)
- AutoMine: Tbot will develop your planets and moons up to the levels given in settings.json. A cool ROI based algorithm is present: TBot will develop your planets calculating to the most profitable building for each planet! A maximum amount of days of investment return can be set. An origin can be set in settings.json to send the necessary resources from.
- AutoResearch: Tbot will develop your researches from the planet set in settings.json up to the given levels. An origin can be set in settings.json to send the necessary resources from.
- BuyOfferOfTheDay: TBot can buy the daily item from the Trader (check intervals are implemented so you can configure shorter check times when there is the specific event)
- AutoFarm: TBot will scan one or more ranges of systems spying inactive players and attacking them with the specified type of ship if they are profitable above a given amount.
- AutoHarvest: TBot will harvest expedition debris in your celestials' systems as well as your own DFs
- AutoColonize: TBot will make new colonies. Input the list of coordinates of your desired colonies and TBot will do the rest.
- SleepMode: TBot will not interact with your account between the hours specified in settings.json
- AutoFleetSave: TBot will keep your fleets safe by dispatching them on the safest mission possible until wake up time (deploy with recall is supported!)
- Local Proxy: Tbot allows you to play in your browser
- Insert the hostname of the machine you'll run TBot onto in the settings.json (i.e.: localhost, or the local ip of a computer on your local network such as 192.168.X.X)
- Navigate with your browser to http://hostname:port/game/index.php (remember to change hostname and port with the ones you specified in settings.json)
- Pay attention: TBot is not aware of what you do in the browser, it will do his job regardless of you playing manually, so keep an eye on the console
- Proxy: TBot supports routing your traffic through a HTTP o SOCKS5 proxy
- Fill the settings in settings.json. The settings are quite self-explainatory.
TBot supports the editing of the settings even while it is running. It will take care of turning on and off features as well as the specific feature config settings.
- Download and unzip latest release.
- Insert you credentials in settings.json
- Under "Universe" type your universe name with leading capital letter, i.e.: Andromeda, Bellatrix etc...
- Under "Language" type your universe community code. You can find it by logging to your account and analyzing the url, such as s161-us.ogame.gameforge.com => us
- Configure the bot by editing all settings.json fields
- All config options are sorted by feature, check which features you want and configure them before activating
- Make sure you have installed the .NET 5 runtime for your platform
- Run TBot.exe
- Open a terminal (if you are in a desktop environment)
- Download latest release for your platform.
wget https://github.com/ogame-tbot/TBot/releases/download/VERSION/TBot-VERSION-PLATFORM.zip
(change the filename to your real one!)
- Unzip the downloaded file
unzip TBot-VERSION-PLATFORM.zip -d TBot
(change the filename to your real one!)
- Make ogamed executable (this is only required on first run or update)
chmod +x ogamed
- Make TBot executable (this is only required on first run or update)
chmod +x TBot
- Insert you credentials in settings.json
- Under "Universe" type your universe name with leading capital letter, i.e.: Andromeda, Bellatrix etc...
- Under "Language" type your universe community code. You can find it by logging to your account and analyzing the url, such as s161-us.ogame.gameforge.com => us
- Configure the bot by editing all settings.json fields
- All config options are sorted by feature, check which features you want and configure them before activating
- Make sure you have installed the .NET 5 runtime for your platform
- Run TBot
./TBot
Some successful tests have been done to run TBot on the smallest instance of LightSail (1 vCPU, 20 GB SSD, 500 MB RAM and 1 TB outbound traffic) on Amazon Linux 2, which is free for a three month trial. In order to run it, steps should be as follow:
- Create your account on Amazon Web Services (Credit Card required), and create a LightSail Instance running Amazon Linux 2. The smallest one fits into the "Free Tier" Program, which allows a 3 month free trial.
- Select the ports where you want to connect, and open them in the Networking Settings on the instance's AWS Console (ex. ports 8000 - 8020 open for TCP and from any ip address if you don't know where you will be connecting from). This should make it accessible to the public internet.
- Connecto to AWS instance using SSH and the .pem key you get during the instance setup:
$ ssh -i ~/pem/<my>.pem ec2-user@<instance's public ip-address>
- Update the system with
sudo yum update
- Install the .NET 5 tuntime, which can be done using these instructions for CentOs, and which is something like
$ sudo rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm
$ sudo yum install aspnetcore-runtime-5.0
$ sudo yum install dotnet-sdk-5.0
- Upload your TBot files, which were previously downloaded and setup correctly. You can do this by using something like FileZilla using sftp and the same credentials as the ssh connection and then copy your TBot folder into the user's home directory in the server. Make sure your settings file has the public ip of the aws instance and the port where you want to connect.
- Follow the instructions as written above for Linux by changing permissions.
Very important: if you run TBot by using the command ./TBot
and then disconnect from the ssh connection, it'll kill TBot. In order to prevent this, you have to use a service called screen, and run the TBot instance like this:
$ screen ./TBot
then press <Ctrl + a + d> in order to detach the console.
Once it is detached you may close the ssh instance and TBot will run fine. You can repeat the process in order to run another instance of TBot on the server, as long as you detach it every time after you run the command.
The testing was done on the smallest LightSail instance has been running up to 4 instances of TBot (different accounts each), with no problems so far, however if you run a 5th instance, it can cause the server to run out of RAM and it'll crash.
TBot supports automated Telegram messaging. In order to enable it, you need to follow theese steps:
- Create a new Telegram bot
- Write "/new_bot" to @botfather
- Follow the instructions given by BotFather, assigning a name and an username for the bot (theese are not important, set them to whatever you like)
- BotFather will send you a message containing the API Key you need
- Insert the newly obtained API Key in settings.json under TelegramMessenger.API
- Get your ChatID
- Write "/start" to @getmyid_bot
- It will answer you a message containing your user ID and chat ID (WARNING: you need the USER ID)
- Insert the newly obtained ID in settings.json under TelegramMessenger.ChatId
TBot implements an automatic captcha solving mechanism.
However, being based on ogamed, it supports manual captcha solving as well as Ninja Captcha Autoresolve service.
To manually solve captcha navigate to host:port/bot/captcha
To configure Ninja Capthca Service follow this guide and insert the obtained APIKey in settings.json
A web config interface should be written soon or later, as well as a database persistence.
Also, a proper documentation about how to deal with settings.json would no doubt be helpful, especially for new users.
Feel free to fork and make pull requests or give suggestions posting an Issue or joining the Discord chat.
I write and build TBot with Visual Studio 2021 Community Edition, thus .NET 5 SDK is enough for command line compilation.
Releases are automated by GitHub Actions, take a look at the workflows if you are interested on the build process.
TBot is currently developed and mantained for Windows 64bit, Windows 32bit, Linux x86_64, MacOS 64bit, Linux ARMv7 and Linux ARM64.
MacOS ARM will be natively supported when .NET 6 will be officially released, for the time beeing the MacOS 64bit version works fine in emulation on M1.