OGame Bot: What It Does and How to Choose One

Kepler is an OGame bot that plays your account for you: mines, research, expeditions, raiding, overnight Fleet Save. It runs on your computer or on our servers, and its built-in browser lets you play while it works. This page covers what a bot automates, where it runs and how to choose one. 7-day free trial, no card needed.

Updated 13 October 2026 · OGame V13

Your expeditions come back in the middle of the night, and a miner two systems over has just gone inactive. Sooner or later every OGame player wonders whether a program could deal with that for them. This page starts with the question most players ask first, then explains what a bot automates and how to pick one. It uses Kepler, the bot we build, as the example, limits included.

In short

No, OGame bots are not allowed, and an account that uses one risks a permanent ban. How big that risk is depends mostly on how the bot plays, starting with whether it takes breaks and how many tools run on the account at once.

What is an OGame bot?

A program that plays your account for you. Once logged in, it reads the game pages and gives the orders you would give yourself, like starting a building or getting the fleet out before an attack lands. It does not cheat on resources or flight times: you could do everything it does by hand. It simply does it at 4 a.m. without leaving a slot empty.

The word covers tools that people often mix up:

Interface extensions

AntiGame, OGLight or OGame Infinity change how the game looks, but they do not play for you.

Browser bots

They run inside a tab that has to stay open.

Standalone bots

They are separate programs, on your computer or on a server. Kepler is one of these.

Discord bots

They are bots in name only: they post game information in a channel.

Are OGame bots allowed? The rules and the ban risk

No. Section 5.2 (Scripting) of the international game rules, in force since 24 August 2026, prohibits bots, macros and automated scripts unless Gameforge has expressly allowed them, and only scripts on the official list are permitted. Gameforge's General Terms of Use also forbid, in section 6.4, bots and any program that automates actions meant to be done by hand. An interface extension being allowed does not make a bot acceptable.

Gameforge's General Terms of Use (PDF)

Penalties range from a warning to the permanent loss of the account, and Gameforge can suspend an account as soon as a breach seems established at first sight. Kepler is independent, not affiliated with or endorsed by Gameforge, and a penalty gives no right to a refund or compensation. No tool can promise immunity, so be wary of anyone who does.

How bots get caught and banned

Most of the time it is not a technical detail that gives a bot away, it is the way it plays. What stands out is an account that is active around the clock and sends its fleets at the same rhythm every time. Actions chained faster than anyone can click get noticed too, and so does a flood of requests: the same terms forbid putting excessive load on the game's servers. Other players see it and report it, and the GOs, the game operators, read the logs.

What Kepler does to play like a human

None of this makes an account untouchable. These are ways to reduce the visible signs, and most of them depend on your settings.

Every request from an account goes through a single scheduler. When several modules have work at the same moment they do not interleave: expeditions go first, and a module finishes its pass before handing over. Two to three random seconds separate two modules. Delays avoid round numbers too, so an hour becomes anything between 52 and 67 minutes.

Sleep mode puts the account to rest for a time window, then resumes whatever was running. Started by hand or scheduled day by day with a random shift, it leaves the account alone during the window, apart from what you asked of it, such as bringing the fleet home from its overnight Fleet Save. It is off when you install the bot. Turn it on: it is probably the setting that matters most.

Planning, a calendar that switches each module on and off at set dates, also adds a random offset. And the bot warns you when an account has been active for 24 hours without a break of at least 4 hours.

Each robot has its own browser fingerprint, consistent with the country its connection comes from, and the bot never opens two sessions on the same account.

How Kepler protects your account, in detail

There are limits. Under attack, Defence does not wait its turn, although the exact moment the fleet leaves is still randomised. There is one exception: Phalanx and the Debris field check keep the account to themselves, Defence included, and while they run, no attack is being watched. The tools in the Tools menu make a lot of requests, and a script's rhythm depends on whoever wrote it.

What Kepler can automate

The names below are the site's, close to those in the bot's menu.

Building

Mines, research and lifeforms, towards a goal you set (AI mode) or through your own queue.

Supply

Sends a planet what its queue is missing, from the nearest bank that has enough.

Discovery

Sends the lifeform discovery missions for you.

Expeditions

A fixed composition, an automatic fleet sized from the server's progress, or the ticked ships shared equally across free slots.

Raiding and Espionage

Inactive farming campaigns relaunched in one click, and an area you spy on again with one click a day.

Defence

Gets the fleet out before an attack lands. From a moon it can even send it to a debris field it never harvests.

Overnight Fleet Save

What a lot of players call their fleetsave (FS): when the account goes to sleep, the fleet leaves, then comes back inside the return window you choose.

Repatriation

Brings production home. In moon mode the transports leave from the moons, invisible to the phalanx.

Flight planning

Lands a fleet at the time you choose.

Colonisation

Keeps the planets that match your position, size and temperature criteria, and abandons the others.

Galaxy scanner and Player watch

The first records every player's positions, the second brings out their regular gaps in activity.

Phalanx

The exact second a fleet got home after a moonbreak.

Rewards and boosters

Does the missions of the Universe Rewards event and keeps your boosters running. It only spends Dark Matter if you have ticked the box.

The full list of bot features

The Tools menu adds four watchers. Debris field detection reports every battle in the universe, and the Debris field check follows a field until the second it disappears, so you can catch the enemy recyclers on their way back. New colony detection spots a player moving into your system, Timer watch a target going inactive. These tools make a lot of requests: the bot's own advice is one robot per tool, with no other module switched on, preferably on a secondary account. Alerts go to Telegram, Discord or both.

Scripts cover the rest, with over 300 functions in anko. One robot plays one OGame account, and your licence sets how many run at once.

The scripting documentation

Where an OGame bot runs: browser tab, your PC or a server

A browser bot needs its tab open. Kepler is a standalone program, and you choose where it runs.

At your place.

Windows 10 and 11 (64-bit), 64-bit Linux, Raspberry Pi 4 or 5 on a 64-bit system, and macOS 12 or later. The macOS build is the newest and has seen less use than the others. You launch one file: a console stays open while the interface opens in your browser. The bot runs as long as the computer is on, and your credentials stay on your machine, encrypted. The licence is checked locally and keeps working for up to three days without our server. Kepler is not signed with a certificate, so Windows warns you on first launch; a SHA-256 checksum lets you check the archive.

Download Kepler for Windows, Linux and macOS

At ours.

Nothing to install or leave running. Each robot gets a dedicated IP address in the country you pick. The interface has its own web address that also works on a phone, and we install the updates for you.

Built-in browser and manual mode

The built-in browser lets you play while the bot runs: it opens the game through the robot's own session, with no second login. Switch on manual mode and every automation waits, Defence included, and the bot never changes planet under your mouse. Only the recall of a Fleet Save already under way still leaves on time. Manual mode ends after ten minutes without input (you can change that) and lasts two hours at most. During that time nothing watches for attacks.

Four extensions are adapted to the built-in browser: AntiGame updated for V13, OGame Infinity, OGame Tracker, which keeps count of your expeditions, and OGLight, which you just tick.

Extensions adapted to the built-in browser

How to choose an OGame bot

Most pages that come up for "best OGame bot" are vendor pages, this one included. So here are the questions we would ask of any bot, starting with ours.

Is it up to date?

The game is on V13, with lifeforms. Look for a dated changelog, like our version history.

Free or paid?

Free, open-source OGame bots let you read their code, but check that they still keep up with V13. A paid bot should earn its price through updates, support and documentation.

Where does it run?

A tab you must keep open, a program on your PC or a server that runs with your PC off: each makes for a very different routine.

Where does your password go?

The answer should be there in black and white, encryption included.

Is it honest about the rules?

A bot sold as impossible to detect should ring alarm bells.

Can it take breaks?

Without sleep and varied delays, the account plays like a metronome.

Can you play at the same time?

With no second login, and without the bot switching planets on you mid-action.

Does it do what you need?

Well-sized expeditions beat a long list of checkboxes.

Can you try it before paying?

Ideally without a card, and with documentation you can actually read in your own language.

Kepler's version history

Try Kepler free for 7 days

The trial lasts seven days for one robot, with no card, on your machine or in the Cloud. Confirm your email address, then start the trial from your customer area. On your machine, when the trial ends, the robot stops and tells you why; your settings stay. A Cloud instance is suspended instead, then deleted after the delay announced by email if you do not carry on.

The installation video goes from creating your Kepler account to adding your OGame account. The bot also accepts an OGame account protected by two-factor authentication. The interface comes in 25 languages, and each new version installs in one click.

Install Kepler and start your first bot in 2 minutes

After that, the price depends on the number of robots. You can pay monthly by card and stop whenever you like, or pay once by card or crypto.

Frequently asked questions

Are OGame bots allowed?

No. The game rules (section 5.2) and Gameforge's terms forbid them, and an account that uses one risks a warning, a suspension or a permanent ban. The risk exists with any bot, Kepler included. Turn on Sleep mode, and give each tool a robot of its own.

Do I need to leave my PC on?

On your own machine, yes. In the Cloud, no: the bot runs on our side.

Is there a free OGame bot?

Yes, a few open-source projects, notably on GitHub. Check above all that they still support V13. Kepler is paid, with a seven-day trial and no card.

What is the difference between a bot and AntiGame or OGLight?

These extensions change how the game looks without playing for you. A bot sends orders to the game by itself, and that is what the rules forbid. Kepler's built-in browser runs adapted versions of both.

Does an OGame bot work with V13?

Kepler does, lifeforms included, and every version is dated in the version history. For any other bot, check the date of its last update.

Download

See pricing