Strategy guide

OGame fleetsave guide: what the phalanx sees and how to save your fleet without mistakes

Everyone knows the fleet should be flying while you are offline. What sets apart players who never lose their fleet is knowing which missions an enemy phalanx can see, how to time the return and how to avoid being predictable.

Updated

The idea in one sentence

A fleet in flight cannot be attacked. Fleetsaving means keeping your fleet, and your resources, in flight whenever you are offline, in a way that nobody can tell when they land.

The second half of that sentence is what matters. Almost every fleet that gets crashed was "saved": the attacker knew when it would land because they saw it with a phalanx, or because the player always used the same schedule.

How the attacker sees you: the phalanx

The sensor phalanx is a moon building. From it you scan a planet and see the fleets heading to it or leaving it, with their arrival times.

  • Range: level² − 1 systems on each side, in the same galaxy. Level 2 = 3 systems, level 4 = 15, level 5 = 24, level 6 = 35, level 7 = 48. The Discoverer class gets 20% more range.
  • Cost: deuterium for every scan (5,000 according to the community wiki). The scanned player gets no warning.
  • It scans planets only, never moons. Anything that leaves a moon and returns to a moon is invisible to the phalanx.
  • Since lifeforms it also shows the speed of the slowest ship in each fleet, which helps to work out the speed you sent it at.

To know who can scan you, look for moons in your galaxy close to you (a level 7 phalanx reaches 48 systems, level 8 reaches 63) and spy them: a moon espionage report shows the sensor phalanx level if you send enough probes. A moon without a phalanx today may have one tomorrow, so check again now and then.

What the phalanx sees and what you can recall

MissionDoes the phalanx see the outbound flight?Does it see the return?Can you recall it?
Deployment moon to moonNoNoYes, until it arrives
Harvesting debris from the moonNoNoOnly before it reaches the field
Expedition from the moonNoNoOnly before it reaches position 16
Deployment planet to planet, recalledYes, until recalledNoYes, until it arrives
Deployment planet to planet, not recalledYesNo return: it stays at the targetYes, until it arrives
Harvesting debris from the planetYesYesOnly before it reaches the field
Expedition from the planetYesYesOnly before it reaches position 16
Transport or attack from the planetYesYesYes, until it arrives

The rule behind it: the phalanx sees whatever leaves a planet or arrives at a planet. A mission that only touches moons, debris fields or position 16 leaves no trace. The one useful exception without a moon is a recalled deployment: its return does not show.

The recall rule

When you recall a mission, the fleet takes as long to come back as it had already flown. Recall after 4:05:23 of flight and it lands 4:05:23 after the recall: 8:10:46 in total since it left.

Two consequences follow:

  • Late recalls are expensive. Send an 8 hour flight, recall it after 7 and it comes back after 14. Recalling is for fixing a mistake in the first minutes, or a deliberate tool to set the return time, as you will see below.
  • Recalling hides the return, not the fact that you recalled. If a rival had your deployment on their phalanx and it disappears, they know you recalled it. They do not know exactly when, unless they scan often (and every scan costs deuterium).

The methods, from most to least reliable

1. Deployment moon to moon

The reference method. Neither the outbound flight nor the return can be seen, and you can recall it if you log in early.

Its only weak point is moon destruction. If the target moon or the origin moon falls, the fleet heads for the planet instead, and from that moment the phalanx does see it. The chance to destroy a moon is (100 − √diameter) × √deathstars, in %. An 8,000 km moon against 9 deathstars: (100 − 89.4) × 3 ≈ 32%. Big moons hold up better.

2. Harvesting a debris field from the moon

The phalanx cannot see this one either. It has two drawbacks:

  • Once the fleet has harvested, you can no longer recall it: it comes back at the planned time no matter what.
  • A rival can watch the debris field. When it vanishes, they know when you arrived and can work out the return.

That is why experienced players send a decoy recycler first to clear the field, or use an invisible field (one so small it does not show in the galaxy view). According to the community, invisible fields are wiped every week, on Sunday night.

3. Deployment planet to planet, recalled (no moon)

If you do not have a moon yet, this is the method the phalanx cannot time. The outbound flight is visible while it lasts; the return after the recall is not.

The trick is to send it hours before you leave and recall it right before you log off. Since the return takes as long as the fleet had flown, the time between sending and recalling is exactly how long it will stay away afterwards. The example below works it out.

Vary the speed and the target: if it always leaves at the same time, at the same speed and to the same planet, a patient rival ends up working out when you recall.

4. Expedition

It works and keeps the fleet out of everyone's reach, but it is not free:

  • Risk of losing it: with version 7 numbers, 0.33% black hole per expedition, plus 5.8% pirates and 2.6% aliens fighting your fleet. Lifeforms and the Discoverer class lower some of those risks.
  • Less predictable duration: 7% of the time it comes back late and 2% of the time it comes back early. Early is the dangerous one: the fleet lands while you sleep.
  • If it leaves from a planet, the phalanx sees the return.

An expedition with the whole fleet is an acceptable fleetsave now and then, not a daily routine.

5. What is not a fleetsave

  • Transport or attack from the planet: the phalanx sees both legs. Whoever watches you knows to the second when it lands.
  • Leaving the fleet on the moon "because the phalanx cannot see moons": the phalanx cannot, but an espionage probe can, and a moon can be attacked like any planet.
  • Harvesting from the planet a field everyone can see: the easiest fleetsave in the game to catch.

Worked example: the night save

You go to bed at 23:40 and your alarm goes off at 7:15. You want the fleet to land once you are awake, with a few minutes to spare: around 7:45. You need roughly 8 hours 5 minutes of flight.

With two moons. Flight time is almost inversely proportional to speed. If the flight between your two moons takes 2:30:00 at 100%, at 30% it takes about 8:20:00 (2.5 h ÷ 0.3) and lands around 8:00. At 40% it would be about 6:15, landing at 5:55, which is too early. You pick 30% and burn far less deuterium too. If you wake up earlier you recall it and it returns to the origin moon; wake at 6:00, for example, and it comes back around 12:20, so recalling only makes sense in the first hours.

With 10% steps the time does not always fit. Play with the target (a closer or farther moon) or, as a General, with the 5% steps.

Without a moon. At 15:30 you send a deployment to another of your planets with a flight longer than 8 hours, say 10 hours. At 23:40, right before bed, you recall it: it had flown 8:10, so it comes back at 7:50. The phalanx stopped seeing it at 23:40 and cannot know when it returns. Meanwhile, from 15:30 to 23:40, the fleet was not on the planet: if you want to use it that afternoon, pick another method.

Always check the arrival time on the in-game fleet screen before confirming: that is the number that counts.

Mistakes that get your fleet crashed

  1. Leaving resources on the planet. The fleet is safe and 3 million metal waits for whoever comes by. Load what fits before leaving; that is what cargo ships are for too.
  2. Same time, same moon, same speed. A rival who watches you for a few days finds the pattern even without seeing your fleet. Change the target, speed and method.
  3. Landing before you log in. If the fleet lands at 6:30 and you log in at 8:00, it has sat for an hour and a half on a moon that can be spied and attacked. Landing a little late beats landing a little early.
  4. Leaving from the planet. Even if the target is a moon, the phalanx sees the departure and, if it returns to the planet, the return.
  5. Recalling late. A recall in the middle of the night stretches the flight up to twice what it had flown.
  6. Not knowing who has a phalanx nearby. A new moon 20 systems away changes which methods work for you. Check the moons around you now and then.
  7. Trusting a time worked out by hand. The universe may have different fleet speeds for peaceful, war and holding missions, and lifeforms change ship speeds. The game's time is the right one.

It depends on your universe

  • Fleet speed: every universe has its own, sometimes different for peaceful, war and holding missions. It changes every flight time.
  • Class: the General adjusts speed in 5% steps and the Discoverer gets 20% more phalanx range and fewer pirates and aliens on expeditions.
  • Lifeforms: some technologies speed ships up or reduce expedition risks. The expedition numbers in this guide are version 7 values, before those bonuses.
  • Debris and moons: your universe's debris percentage decides how easily someone gets a moon near you, and how often there are debris fields to harvest.

How Orbit helps

  • The flight simulator works out outbound and return times with your drives, your class and your universe speeds, and backwards from the time you want to land. See the calculators manual.
  • In the chat, Catch on return does the maths your attacker would do: when an observed fleet returns at every possible speed. Run it against yourself to see what your routine gives away.
  • The player scanner shows observed activity by time slot for the players around you. It does not say when they are online, but it does show which patterns can be seen from outside; yours can be seen the same way. See the intelligence manual.

Sources

  • Sensor Phalanx and Fleetsaving, community wiki (Fandom): range, cost and what the phalanx sees.
  • Moon, community wiki: moon destruction formula.
  • Player classes FAQ, official English board (16/09/2021): General and Discoverer bonuses.
  • Expeditions 7.1, community compilation (January 2020): odds of each expedition outcome.