Every hour you spend offline in OGame is an hour your resources sit exposed on a planet that any active scanner can probe and attack. The difference between players who compound their progress and players who log in to smoldering wreckage is almost always a handful of deliberate habits executed in the ten minutes before they close the browser. Overnight resource management is not complicated — but it demands consistency, because the one night you skip the routine is the night someone is watching.
The Overnight Problem: Why Sleep Is the Riskiest Part of Your Day
OGame's time-zone asymmetry is brutal. While you sleep, players in different regions are fully active — scanning galaxies, sending probes at 03:00 server time, and dispatching battleships the moment they detect a profitable ratio. On a standard server this matters. On a speed universe running at 50x or 99x economy it matters enormously, because resources accumulate fast. A planet sitting at three or four times storage capacity is a beacon.
The overnight window is typically six to nine hours. On a 99x economy universe like Nebula, that is the equivalent of roughly a week of production on a 1x server compressed into one night. Leaving that production unguarded is the same as handing a key to anyone with a decent probe count. Understanding the scale of the problem is the first step; every tactic that follows exists to close that window of exposure.
There are four levers you can pull: spend resources before they accumulate to dangerous levels, fleet-save your ships and resources simultaneously, use storage limits and planet layout to make your planets unattractive targets, and build enough passive defense to push the attacker's profit margin below zero. Most experienced players combine all four. Relying on only one is the amateur move.
Spend-Down Before Sleep: Turn Resources Into Assets
The single most reliable overnight protection that requires zero active management during the night is spending your resources before you go offline. Every unit of metal, crystal, and deuterium you convert into a building level, a research step, or a ship that joins your fleet is a unit that cannot be stolen. This sounds obvious and yet an enormous number of players leave hundreds of millions sitting idle simply because they did not queue anything before logging off.
The priority order for spend-down looks like this:
- Queue active research. Research locks resources into the lab for the duration. On speed servers with 100x or 200x research multipliers, even late-game techs finish in hours, so queue the most expensive research you can afford and let it run overnight.
- Queue building upgrades on every planet. Each planet has its own construction queue. A mine upgrade on five planets simultaneously can absorb an enormous resource surplus. Prioritize mines that give the best long-term production return, but in a pinch any upgrade is better than leaving resources liquid.
- Build ships. If research and buildings are already queued, dump remaining resources into ships. Recyclers, large cargo ships, and combat ships all work. Avoid letting the shipyard sit idle overnight when you have surplus resources. Ships join your fleet and can be fleet-saved; idle resources cannot save themselves.
- Build defenses last. Defense is slower to build per resource unit on most server configurations and cannot be fleet-saved, but it raises your defense value, which deters marginal attackers. If you have leftover crystal after queuing everything else, Plasma Turrets and Gauss Cannons are the most resource-efficient defensive investments.
On a server like Proxima (200x economy, 80% ship debris rate), aggressive spend-down is even more critical. At 200x, a single planet can accumulate resources fast enough that leaving even 30 minutes of unchecked production exposed before a long offline session adds up to a meaningful raid target. The habit of spending down should become reflexive — every time you are about to go offline for more than two hours, open every planet's queue and fill it.
Overnight Fleet Saves: The Fleeter's Non-Negotiable
If you fly ships in OGame, fleet saving overnight is not optional — it is the game. Losing your fleet while you sleep is effectively losing months of production in a single event. The fleet save is how you make your ships and the resources loaded onto them unreachable for the duration of your offline window.
The mechanics are straightforward: send your fleet on a mission (deploy, harvest, expedition, or attack on a distant target) with a return time that lands after you expect to be back online. The art is in the calibration. Too short and you return while you are still asleep, landing in your own hangar as a sitting target. Too long and you tie up your ships for unnecessary hours, missing attack windows and expedition slots.
How to calculate your return time: Take your expected time back online, add one to two hours of buffer, and set your fleet arrival + return time to match that total. If you go offline at 23:00 and expect to be back at 07:00, aim for a round-trip that returns around 08:00–09:00. Use the slowest ship in your fleet (usually large cargos) to your advantage — they naturally extend trip duration. Alternatively, target a system that is far enough to stretch the journey.
Load your fleet with resources. A fleet save that leaves resources on the planet is only half a fleet save. Load your large cargo ships and any free cargo space on combat ships with every resource that exceeds your storage-cap comfort zone. Resources in transit cannot be raided.
Moon-to-moon saves. If you have moons, the standard overnight save is a deploy mission from one moon to another. Moons hide your fleet from basic sensor probes and from phalanx unless the attacker has specifically targeted your moon's coordinates. A deploy to your own moon in another system with a return time past your morning login gives you strong overnight protection. On OGames, the moon formation chance caps at 20% on Andromeda, 30% on Nebula, and 40% on Proxima — universes with higher moon chance reward investment in moon infrastructure. Once you have moons established, moon-to-moon fleet saving becomes a routine you can execute in under two minutes.
Expedition saves. Expeditions are an underrated fleet-save vehicle. Sending your main fleet on an expedition with a long travel distance ties up the fleet for a defined period and adds the chance of positive resource returns. The risk is that expeditions can return losses (fleet damage, pirate encounters), so this approach is better suited to older fleets with high combat power relative to the expedition-level enemies they face. See the expedition fleet optimization guide for how to structure expedition missions for maximum overnight safety.
Storage and Bait Management: Make Your Planets Unappetizing
An attacker decides whether to hit you by running a simple profit calculation: expected loot minus deuterium cost of the mission minus expected losses. Your goal is to make that number negative. You do this through a combination of storage management, light bait defenses, and a clean resource profile that signals "not worth it" to casual scanners.
The 10% rule. Storage mechanics in OGame limit the amount a raider can steal in a single attack. Ships can only carry so much, and the attacker must account for the cargo capacity of their fleet. If your planet shows only a thin layer of resources above your storage capacity, experienced players will move on. Conversely, a planet sitting at 300% of storage capacity looks like a jackpot. Upgrade your storage buildings on every colony — metal, crystal, and deuterium storage should always be ahead of your mine production level so that even a full night's accumulation does not push you into obvious overflow.
Bait resources. Some veterans deliberately leave a small amount of resources on defended planets — enough to make probing "find something" but not enough to justify an attack after factoring in deuterium costs and defense losses. This works best with a dense rocket launcher + light fighter screen that makes any attack on the planet unprofitable unless the attacker brings overwhelming force that costs more than they would gain.
Spread across colonies. Concentrating all your resources on one planet is a single point of failure. Distribute production and storage across all your colonies so that no single planet presents an irresistible raid target. A raider scanning your empire and seeing six planets all at moderate, defended levels is far less motivated than one who finds a single planet drowning in resources with minimal defense. The multi-planet logistics guide covers efficient colony coordination in depth.
Defense thresholds. You do not need a full turtle setup to deter overnight attacks. The target is making your defense expensive to crack relative to the reward. On most speed servers, a mixed defense including Rocket Launchers, Light Lasers, Gauss Cannons, and Plasma Turrets — scaled to your production level — is sufficient to dissuade the casual farmer. If you are farming actively, you know your own attack capacity; mirror approximately that level of defense across your most resource-exposed planets.
Morning Routines: The First Ten Minutes After Login
Overnight resource management does not end when you wake up. The morning login is its own critical phase. You have a brief window where your returning fleet is visible but not yet landed, where other players who watched your fleet save know the approximate return time, and where your overnight production has been sitting since your last login. Moving fast matters.
Execute this sequence every morning:
- Check for incoming attacks immediately. Before anything else, look at your overview for red combat icons. If there is an incoming attack, assess the arrival time and your options. Recall your returning fleet if you cannot counter or escape.
- Re-queue buildings and research. Anything that finished overnight should be re-queued to the next level. Do not let queues sit empty even for an hour during active hours.
- Spend down overnight production. Any resources that accumulated overnight and exceeded your safe storage threshold should be queued into ships, buildings, or research before you go about your day.
- Check expedition results. If you fleet-saved via expedition, review the return for resources gained. Factor those into your morning spend-down.
- Probe competitors. Morning is an optimal time to probe competing players who used aggressive fleet saves or long attacks overnight. Their timing may leave them vulnerable in the early hours. The counter-espionage guide covers how to read probe results and identify raid opportunities.
The morning routine compounds over time. Players who execute it consistently pull ahead of equally-skilled players who log in, collect resources manually, and scroll the feed. Every queued building level, every spent resource, every fleet safely returned is a small edge. Over weeks on a speed server, small edges become ranking gaps.
Overnight on 200x Economies: Proxima-Level Intensity
Everything above applies to all servers, but on OGames' highest-speed universe — Proxima at 200x economy — the overnight stakes are fundamentally different in scale. In eight hours of sleep, a well-developed Proxima colony cluster can produce resources equivalent to days of output on a standard server. The math on raid profitability is extreme, and so is the competitiveness of active players at peak hours.
On Proxima specifically, several adjustments become mandatory rather than optional:
- Multiple fleet saves running simultaneously. One fleet save is not enough if you have significant fleet power. Layer your fleet saves across different missions so that even if one return is sniped (attacked while your fleet is landing), you do not lose everything. Use different moons, stagger return times by 30-60 minutes, and vary your save targets.
- Deuterium management is tighter. At 200x fleet speed, missions that cover meaningful distance are short in absolute terms but expensive in deuterium relative to economy speed. Ensure your deuterium reserves are sufficient for emergency fleet recalls and do not drain your deuterium stockpile into the save mission itself. The advanced deuterium economy guide covers production balancing in detail.
- Debris field exposure. Proxima has an 80% ship debris rate and 32% defense debris rate. This means any fight on your planets creates a massive debris field that incentivizes follow-up attacks from recyclers. After any overnight battle, even a defensive win, expect aggressive recycler activity in your system within minutes of the result posting. Your morning routine should include immediate recycling or a defender recycle to deny the attacker the field.
- 20,000 DM + 50,000 weekly DM on Proxima. The generous Dark Matter allocation on Proxima enables more Commander slots and longer commander durations. Use the Geologist commander overnight — the 10% production bonus compounds directly into your overnight resource yield. On a 200x server, that is meaningful additional production protected (or spent down) before sleep.
Players who build solid overnight habits on Proxima accelerate past competitors at a rate that feels unfair. The ones who skip fleet saves, leave planets exposed, or forget to queue buildings before sleeping are essentially donating their production to whoever scans them first. Speed universes reward discipline disproportionately precisely because the feedback loop — gain or loss — arrives so fast.
Choosing the Right Universe for Your Play Schedule
Your overnight risk tolerance should influence which OGames universe you call home. If you have irregular sleep schedules or cannot commit to a consistent offline window, Andromeda's 50x speed and lower debris rates (43% ship, 17% defense) offer a more forgiving environment. A bad overnight on Andromeda stings; a bad overnight on Proxima can set you back dramatically.
Nebula at 99x sits in the middle — fast enough that overnight habits matter significantly, but with a more active mid-game community that creates interesting alliance dynamics. ACS fleet saves (coordinating saves with alliance members who are active when you sleep) are particularly powerful on Nebula. The alliance warfare and politics involved in building those overnight ACS agreements is its own deep meta-game. For a full breakdown of universe differences, the universe selection guide lays out every stat comparison in detail.
Regardless of which universe you pick, the overnight habits described in this guide apply universally. The specific numbers change; the principles do not.
FAQ
What is the safest fleet save mission type for overnight?
Moon-to-moon deploy missions are the safest for most players. Your fleet is hidden from sensor probes, and the phalanx threat exists only if an attacker specifically targets your moon — which requires intelligence about your moon's location. Expedition saves add resource upside but carry small combat risk. For players without moons yet, a long-range harvest or attack on an empty coordinate in a distant galaxy works as an emergency overnight save.
How much defense do I actually need to deter overnight raids?
There is no universal number because profitability depends on the attacker's fleet power, deuterium costs, and the resources on your planet. The practical guideline: your defense should cost more to destroy than the resources the attacker would gain from the raid. Calculate your own ship attack capacity against your defense total and build upward from there. A mix of Rocket Launchers for mass, Gauss Cannons for heavy damage, and Plasma Turrets for high-value targets is the cost-efficient standard.
Should I always load maximum resources onto my fleet save?
Yes, unless you are saving to a destination where cargo loss is a real risk (such as an active war zone or a hostile system). Load everything above your safe storage threshold onto large cargo ships and include them in the fleet save. Resources in transit are untouchable. The only exception is deuterium needed for the save mission itself — do not load all your deuterium if you need a reserve for emergency recalls.
What if my fleet save return time lands while I'm still asleep?
This is the most dangerous overnight scenario. If you miscalculate and your fleet returns in the middle of your sleep window, it lands in your hangar and sits exposed until you log in. Prevent this by always adding 60-90 minutes of buffer beyond your estimated wake time. If you realize mid-session that your save will return too early, recall it and resend to a farther target. On speed servers, always double-check the return timestamp shown in the fleet screen before confirming the mission.
Can alliance members help cover my overnight window?
Absolutely, and this is one of the most underrated benefits of an active alliance. Players in different time zones can watch your system, send you in-game messages if something suspicious appears, and coordinate ACS attacks on anyone who moves against you. Building those relationships — offering the same coverage to allies when you are active — is a multiplier on your overnight security that no amount of solo turtling can replicate. The buddy system on OGames supports exactly this kind of cooperative play.
The overnight window is where OGame empires are made and broken. Ten disciplined minutes before you close the browser — spending down queues, launching the fleet save, checking storage ratios — protect everything you built during the day. Register on OGames and put these habits to work from your very first session; the players who internalize this routine early are the ones who are still flying fleets months later while others log in to empty planets and wonder what went wrong.