OGame Helper Bot

Guide

OGame Defender Setup
Last updated: 2026-09-253 min read

OGame Defender Setup

The Defender tab configures incoming-attack checks, fleet evacuation timing, optional recall, and rules for each planet or moon. This guide describes the extension's 1.2.4 settings as reviewed on 25 September 2026. A configured panel does not prove an evacuation can be sent; the current game state determines which actions are available.

Overview

Use this guide as the map for the Defender tab. The tab is split into Settings, Celestial Configs, and Plans. Before enabling it, confirm the extension license is active, the game tab is signed in, and the bot can see your planets or moons. Keep the main bot stopped while reviewing destinations and timing.

Subtabs

Settings

The Settings subtab controls global defender behavior.

Important options include:

  • Check interval and randomized interval.
  • Evacuation seconds before impact.
  • Ignoring attacks far in the future.
  • Recall behavior after evacuation.
  • Origin check mode.
  • Optional probing or messaging attackers.

The Dump Remaining Resources Into Defenses control is not available in this reviewed build, so do not plan around it. Telegram alert controls are documented in the separate Telegram guide.

Celestial Configs

The Celestial Configs subtab defines evacuation behavior per planet or moon. Each celestial can have its own mode, preferred destination, and expedition spy behavior. Configure one important celestial first and verify that its destination is still valid in OGame.

Plans

The Plans subtab lists detected defender plans and lets you remove plans that are no longer needed. Review a plan's target, impact time, status, and any error before relying on it.

  • Start with a conservative check interval.
  • Configure one or two important celestials first.
  • Enable Telegram alerts only after connecting Telegram.
  • Review plans regularly so old targets do not stay active.

First-Run Check and Troubleshooting

After setting one celestial and its destination, enable Defender and the main bot only when you intend to run it. Watch the Plans subtab during an ordinary supervised session. Compare any detected event and plan with the game's movement view; do not create an attack or move a fleet solely for a screenshot.

If a plan is absent, check whether the bot and Defender are on, whether the target celestial is configured, and whether the attack lies inside any enabled impact window. If a plan exists but evacuation fails, inspect its error and the current fleet slots, ships, fuel, destination, and pause state before adjusting timing. A browser or connection interruption can prevent a scheduled action even when the configuration is valid.

Defender does not guarantee that every attack is detected or that an evacuation succeeds. Pauses and random intervals change when checks run; they do not make prohibited automation permissible under the OGame rules.

FAQ

Does a Defender plan mean the fleet has been evacuated?

No. A plan records what Defender intends or attempted to do. Confirm the status in Plans and the actual fleet movement in OGame.

Why might Defender wait despite an incoming attack?

The bot or Defender may be stopped, the target may be unconfigured, or an impact-window rule may exclude the event. Check those settings and the current game movement before changing evacuation timing.