The ninja is the highest form of revenge in OGame: you let an enemy scan your planet, spot your resources, and launch their fleet in confidence — then you drop a hammer on them the moment they land. Done correctly, a ninja doesn't just save your resources; it erases the attacker's fleet entirely and seeds a debris field that often dwarfs what they were coming to steal. This guide covers every technical layer — bait construction, arrival timing, ACS defend coordination, and reading your attacker's psychology — so you can execute a clean ninja on any server speed.
The Sweetest Revenge in OGame
Most OGame defense philosophy focuses on one of two extremes: turtle up behind enough defensive structures that attacking is unprofitable, or fleet-save so aggressively that the attacker finds nothing. The ninja is the third path, and it is categorically more rewarding than either. A successful ninja doesn't merely defend — it punishes the attacker for choosing you as a target.
The core mechanic is simple. Combat in OGame resolves the instant an attacking fleet lands. If a defending fleet also arrives at that exact second — or is already sitting in orbit — it fights alongside your stationary defenses. The attacker committed their fleet and fuel when they launched. You have until their arrival to position a superior force. Time it right and the attacker loses ships, loses fuel, loses the mission entirely, and hands you a debris field to recycle.
On fast servers the stakes scale dramatically. In OGames' Proxima universe running at 200x economy speed, fleets and resource stockpiles that would take weeks to build on a 1x server appear within days. A single successful ninja on Proxima can yield a debris field worth hundreds of millions of resources — the kind of score that reshapes the server rankings. Even in Andromeda at 50x, a well-sprung trap can delete a raider's primary attack fleet and set them back significantly.
Psychologically the ninja also sends a message that echoes through an entire server. Attackers share intel. A player known to spring traps attracts far less casual aggression than one who just loses resources quietly. One successful ninja often buys weeks of relative peace.
Setting the Bait
A ninja only works if the attacker actually launches. That means the bait has to be convincing. Too little and they skip you. Too obvious and a careful attacker detects the trap before committing.
Resource levels that trigger launches
Most raiders run profitability calculations based on spy reports. They're looking for a positive return after accounting for deuterium consumption and potential losses against your defenses. Keep your stationary defenses light enough that the math looks profitable — a handful of rocket launchers and light lasers is standard bait setup. You want the attacker to see a soft target, not a fortress.
Leave a meaningful resource pile visible. On a 50x server like Andromeda, leaving 500,000 to 2,000,000 metal on a planet is plausible and tempting. On Proxima at 200x you can leave considerably more and it still looks like normal accumulation rather than a trap. Never leave so much that it strains credibility — an implausibly large pile on a low-points account reads as suspicious.
Fleet position before the bait
Your trap fleet cannot be visible on the planet or moon. If the attacker's spy probe reports your Battlecruisers sitting in orbit, they won't launch. The standard approach is to have your combat fleet away on a recycling, harvesting, or espionage mission timed to return just before the attacker lands — or to stage it on a nearby moon and use a rapid-deploy recall. The fleet should genuinely be absent from the spy report.
Acting normal
If the attacker is watching your activity indicator — and careful players do — you should behave like a player who has no idea they're being watched. Log in at your usual times. Don't suddenly go inactive for six hours right after a spy probe lands on you; that reads as "I fleet-saved." Equally, don't start furiously messaging alliance members the moment you see a probe — keep your chat relaxed.
Timing the Trap
Timing is where ninjas succeed or fail. The defender fleet must arrive at the planet on the same combat second as the attacker, or be present in orbit already. Arriving one second early means the attacker's fleet sees your ships and may recall. Arriving one second late means you miss the combat entirely.
Calculating arrival windows
Once you know the attacker's arrival time — visible in your fleet movement or espionage alert — you work backward. Your trap fleet needs to launch from a position where travel time lands it exactly on that second. Speed servers compress real-world travel minutes dramatically, but the math is the same: distance × fleet speed factor, adjusted by any speed bonuses from your character class or lifeform techs.
The safest approach is to launch from a nearby moon one system away. On fast servers with high fleet speed multipliers (OGames universes run fleet at 50x, 99x, or 200x), even cross-galaxy transit becomes viable within a short window. Use the in-game simulator or an external fleet calculator to nail the exact departure second. Set a timer and hit send with discipline — hesitating by even two seconds can throw off the arrival.
The one-second rule and server lag
On any private server there is minor tick processing delay. Experienced players add one second of buffer — arriving one second before the calculated combat second rather than exactly on it. This ensures the fleet registers as present when combat resolves. Test your server's behavior on a low-stakes mission first to calibrate.
Speed-class considerations
If you play Discoverer or Collector class, your fleet speed bonuses change travel time calculations. A General-class player on your server gets a combat bonus instead of speed, which doesn't affect timing but does affect the fight itself. Know your class multipliers and recalculate accordingly. Understanding how combat mechanics resolve lets you predict whether your trap fleet alone is sufficient or whether you need ACS backup.
ACS Defend Ninjas
A solo ninja relies on one player executing perfectly. An ACS defend ninja involves two or more players coordinating their fleets to arrive at the same combat second, vastly increasing the defensive firepower available — and the margin for error if one fleet arrives slightly off-time.
How ACS defend works
Alliance Combat System defend allows allied players to send their fleets to a target planet or moon as support. Those fleets fight alongside the planet's own defenses and any defending fleet launched by the planet's owner. The combined firepower resolves in a single round sequence. For a ninja, the owner sends the ACS defend invite and allies time their arrivals to match the attacker's landing second.
Coordination protocol
The planet owner shares three pieces of information with ACS allies immediately: the attacker's exact arrival time, the attacker's fleet composition from spy reports, and the coordinates. Each ally then independently calculates their departure time from wherever their fleet is staged. Good alliances on OGames maintain a dedicated coordination channel where this data gets posted in a standardized format — arrival timestamp, coordinates, attacker ship count by class.
Assign a "primary" fleet that carries the bulk of firepower and a "secondary" fleet as redundancy. If the primary misses by a second, the secondary is already there. Stagger staging moons: two moons in adjacent systems give you two separate distance-based windows to work with.
Ship composition for ACS ninjas
Against a typical raiding fleet heavy in Battleships, Battlecruisers, and Destroyers, an ACS ninja wants rapid-fire advantage. Battlecruisers are the gold standard — high rapid-fire against Battleships, enormous shields, solid structure. Supplement with Destroyers if the attacker is bringing Deathstars. Light fighters pad the rapid-fire fodder count and absorb early rounds. Death Stars in an ACS defend are devastating if the attacker brings anything with hull points under 400,000, but coordinate their positioning carefully — a Deathstar arriving early tips the trap.
The OGames fleet-save and positioning guide covers staging strategies that make ACS timing coordination significantly easier — highly recommended reading before your first coordinated ninja.
Reading Your Attacker
A ninja is only viable against an attacker you can read. Understanding their fleet composition, their play habits, and their reaction speed is what separates a successful trap from a wasted effort.
What spy reports tell you
Beyond ship counts, spy reports reveal technology levels, especially combustion drive, impulse drive, and hyperspace drive. These determine how fast their ships actually travel. If the attacker has maxed hyperspace drive and plays General class, their Battlecruisers move fast and your timing window shrinks. Calculate at their speed, not the default.
Multiple spy probes arriving in quick succession mean the attacker is watching you closely and is serious about launching. A single probe followed by silence might mean they're still deciding. Learn to read probe patterns — aggressive players send three or four probes before committing; cautious ones send one and wait for your activity indicator to go dark.
Recall behavior
Some attackers recall the moment they detect any defensive fleet movement. If your moon is visible and they've probed it, they may be watching for sudden fleet departures via phalanx. Stage your trap fleet on a moon that isn't easily phalanx-scanned — ideally one where the attacker would need to waste significant deuterium on a long-range phalanx. Reading how phalanx works and its limitations helps you identify which staging positions are blind to your attacker.
Identifying the target profile
Not every attacker is worth trapping. Newbies and casual farmers send small fleets that aren't worth the deuterium cost of mounting a trap. The ideal ninja target is a mid-to-high points player sending a substantial fleet — someone whose ships, if destroyed, produce a debris field worth recycling and send a message to the broader server community. Check the server rankings before committing resources to a trap setup.
Famous Ninja Patterns
Experienced OGame players have refined several repeatable ninja patterns over the game's two decades of history. Each has specific setups and counters.
The Moon Ninja
The defender's trap fleet is hidden on a moon. The planet shows zero fleet. The attacker sees an undefended planet and launches. The defender deploys from the moon timed to the attacker's landing. This is the most common ninja pattern and the reason moon destruction missions exist — attackers destroy moons specifically to eliminate nearby staging grounds before attacking. Keeping multiple moons across several systems defeats this counter.
The Fake Fleet-Save
The defender intentionally appears to fleet-save — sending a highly visible small fleet on a long harvest mission. The attacker assumes the real fleet is away and launches at the "empty" planet. Meanwhile the defender has a second, hidden fleet in a much closer staging position timed to arrive on the attacker's second. The visible fleet-save is misdirection; the real trap fleet was never in the attacker's sight line.
The Passive Ninja
The defender actually does fleet-save most ships but leaves a sacrificial fleet of rapid-fire bait ships — typically a mix of Cruisers and Destroyers — sitting in orbit alongside heavy defenses. The attacker's simulation shows a winning fight, they launch a moderate fleet, and the combination of defenses plus the "small" orbiting fleet is actually enough to inflict catastrophic losses. This works especially well against attackers who slightly undercount defensive stats.
The Recall Bait
The defender launches their trap fleet openly — visible to phalanx — then recalls it partway through the flight. The attacker believes the threat is gone and continues their launch. The defender immediately re-launches on arrival timing. The attacker, having already committed and seeing the recall, doesn't bother to watch for a re-launch. This is a high-execution pattern that requires precise re-launch timing but is psychologically devastating when it works.
All of these patterns benefit enormously from alliance intelligence. Active alliances on OGames share attacker movement data across the whole galaxy range, giving defenders far more warning time. The raider's perspective guide is useful reading here — understanding exactly what a raider looks for helps you construct bait that appears irresistible while hiding your trap.
After the Ninja: Cleanup and Follow-Through
A successful ninja creates a debris field. That debris is profit — don't leave it for the attacker's allies to scoop. Launch your recyclers immediately after combat resolves. On OGames servers the debris ratios are generous: Andromeda returns 43% of destroyed ships and 17% of destroyed defenses to the debris field; Nebula returns 55%/22%; Proxima returns 80%/32%. A large attacker fleet turned into debris on Proxima can yield an extraordinary haul at 80% ship debris return.
Send your recyclers timed to arrive the second after combat. Use debris field management tactics to maximize recovery speed — deploy multiple recycler waves if the field is large, and consider scrambling allied recyclers for the overflow.
After the cleanup, document the result. Screenshot the combat report. Post it in your alliance chat. The secondary value of a successful ninja is its deterrent effect on the entire server. Other potential attackers see the report, recalibrate their risk assessment, and move on to softer targets. You've just invested a few hours of coordination for weeks of reduced aggression.
Finally, consider the counter-counter. After a ninja, the attacker may be angry and irrational. Watch your activity in the hours after — a furious player may attempt a revenge moon destruction or a hasty follow-up attack. Fleet-save everything valuable for 24 hours post-ninja. Let them cool down before resuming normal operations.
FAQ
What happens if my trap fleet arrives one second too late?
If your fleet arrives after the combat second resolves, it does not participate in the fight at all. The attacker's fleet completes its mission — looting resources — and your late fleet appears over an already-looted planet. You've exposed your fleet position for nothing and burned deuterium. This is why precision timing is non-negotiable. Always calculate arrival to land on or one second before the attacker's combat second, accounting for server tick delay.
Can the attacker see my trap fleet if I launch from a moon?
Only if they phalanx-scan your moon. Phalanx reveals all outgoing and incoming fleets for a moon and its planet within range. If the attacker has a moon with sufficient phalanx range covering your staging moon, they can see your deploy launch in real time and recall immediately. Counter this by staging from moons outside their phalanx range, or by using the recall-bait pattern to force them to stop watching.
How many ships do I need to make a ninja worthwhile?
Enough to reliably destroy the attacker's fleet after accounting for your defenses' contribution. Run the battle simulator before committing. On OGames you can access the built-in Battle Simulator to test exact fleet compositions. A good rule of thumb: your combined defensive power (stationary defenses + trap fleet) should produce a simulated attacker loss rate above 70% of their fleet before considering the fight worthwhile. Below that, you risk losing your trap fleet and failing to fully neutralize the attacker.
Is it worth trapping small farmers on speed servers?
Usually not. Small farming fleets — a few hundred Small Cargoes and a handful of Light Fighters — produce minimal debris and the deuterium cost of mounting a precise timed trap often exceeds the debris value. Focus ninja resources on players sending significant combat fleets: Battleships, Battlecruisers, Destroyers, and Deathstars. The debris field from one large raiding fleet covers the coordination costs of twenty small farming runs.
How do I coordinate ACS defend timing with alliance members across different time zones?
Use UTC timestamps exclusively in all coordination messages — never local time. Post the attacker's arrival in UTC, the coordinates, and the attacker's fleet composition. Each ally converts UTC to their own local time and calculates their departure independently. Good alliances maintain a pinned reference document with each member's staging moon positions and typical transit times to common target systems, so timing calculation is fast under pressure. OGames' 8-language community and built-in messaging system make this coordination accessible across the international player base.
Ready to spring your first trap? Register on OGames and choose a universe that fits your playstyle — whether that's Andromeda's balanced 50x environment or Proxima's explosive 200x speed where ninja debris fields are measured in the hundreds of millions. The attacker who hits you first may regret it for the rest of the server cycle.