Start Orion with a plan for your whole account.
Skie Field Manual · Orion preparation reviewed 9 November 2026. Reward examples are selected PTS beta18 mission cards from 28 October 2026, not current live quotes or collected income. Confirm activation and prices in your destination.

This guide covers:
- Follow a practical first-build sequence once Orion is active in your destination.
- Separate total IAS progression, Lithium throughput, mission completion and reward claims.
- Judge possible per-mission reward scale from observed cards while keeping total IAS, scan settings and actual mission levels separate.

At the merge, confirm the feature before spending

Plan for Orion as part of the move, then check the destination itself. The US merge announcement lists Mars and Nembus as target universes and gives a 9–12 November 2026 merge window. It does not explicitly confirm their Orion activation flag. Both are newly created merge targets; that alone does not prove that the feature is on or off.

The official version 13.1.0 notice limits its 6 November Orion activation to universes launching that day. Gameforge’s launch release says a global rollout is planned for 30 November. Neither statement settles the merge targets individually. Open the destination’s technology tree and check that the IAS, Lithium conversion and anomaly interface are available before committing a build budget.

Use this guide when Orion is enabled
The sequence below is a conditional merge-day plan, not a claim that a named target is already active. The live technology tree supplies the exact prerequisites, fields, construction prices and restrictions. A missing feature is a reason to wait, not to rebuild around an assumed release date.

What to build first, and why

Keep your mines, energy and fleet-safety routine working. Orion adds another use for resources and attention; it does not replace the economy that pays for it. This is a spending order, not a fixed timetable or a requirement to use Dark Matter.

1. Check the live prerequisites and spare fields on each planet you can practically supply. Build the minimum prerequisite facilities needed to place an IAS there. Do not add expensive facilities solely because an old PTS screenshot had them.

2. Place IAS level 1 buildings across those usable planets. For a target total, buy the cheapest next scanner level available, rather than pushing one planet far ahead. Equal per-planet exponential prices make a balanced network the least-resource route to that total.

3. Aim first for a modest total such as IAS 50, then stop to run the loop. Enable a small, affordable Lithium conversion workload and read both the hourly input and output. Check the current storage limit; leave a reserve for claiming the reward as well as finding the mission.

4. Scan for a manageable mission, inspect its actual level, type, stars, waves, participation rules, duration, requirements and reward claim cost. Use ships or delivery cargo you can afford to commit, and cover the return. A large possible reward is not a completed or claimed reward. Check the claim deadline and actual reward-delivery destination; do not assume the reward can wait until your next login.

5. Complete the qualifying mission and confirm the Control Center unlock. Buy a low level of a relevant bonus building only after its effect and price make sense for the missions you actually run. A ship-focused building has little immediate value if you keep choosing resource rewards.

6. Advance through the next useful checkpoints: 100, 150, 200, 250, 300 and 350 total IAS. Recheck affordable missions, Lithium supply and claim costs at each step. Continue beyond a checkpoint only when it supports a mission or bonus you can use.

7. Buy extra discovery capacity, scan results or deeper bonus-building levels only when the existing limit is regularly stopping profitable play. More slots are not more income if you cannot fund claims or finish missions.

Balanced levels optimize access, not everything
The cheapest network for a given total IAS is not automatically the best Lithium-throughput layout. Local scanner levels, conversion workload, input availability and current bonuses also matter. First solve the access target; then measure the bottleneck before specializing a planet.

Total IAS is the sum across your planets

Use T = L1 + L2 + … + Ln, where each L is one eligible planet’s IAS level. Total IAS supports the selectable anomaly level. It is not the exact level of every result, a reward multiplier by itself, or a building level on one planet. Read the mission card and the live unlock requirement.

For a balanced plan from level zero across n planets, set q = floor(T / n) and r = T − n × q. Build r planets to q + 1 and the other n − r to q. Existing uneven accounts should compare the next available upgrade prices instead of demolishing anything to match an illustration.

The table uses 15 hypothetical, equally priced and usable planets. It is not an account requirement. Amounts are cumulative construction costs from IAS 0, in units of each named resource, calculated with the preserved beta13 cost model. They are not current live quotes and do not include prerequisites.

Why distribute the levels?
In the same historical model, total IAS 350 across 15 planets costs 32,992,180 Metal. Across 10 planets at level 35 each, it costs 2,446,262,300 Metal. The total access level is the same; the second plan buys much deeper, more expensive local levels. This comparison isolates construction cost. It does not say the two layouts have equal Lithium output or equal real-world setup costs.

Total IAS | Illustrative 15-planet layout | Metal, cumulative | Crystal, cumulative | Deuterium, cumulative
50 | 10 × level 3 + 5 × level 4 | 7,400 | 3,690 | 1,225
100 | 5 × level 6 + 10 × level 7 | 35,720 | 17,830 | 5,925
150 | 15 × level 10 | 142,740 | 71,325 | 23,745
200 | 10 × level 13 + 5 × level 14 | 569,570 | 284,725 | 94,860
250 | 5 × level 16 + 10 × level 17 | 2,204,365 | 1,102,115 | 367,305
300 | 15 × level 20 | 8,376,990 | 4,188,420 | 1,396,050
350 | 10 × level 23 + 5 × level 24 | 32,992,180 | 16,496,000 | 5,498,560

Build toward a useful unlock, then complete the mission

The public beta13 field research recorded the progression below. Use these as planning checkpoints to confirm in the current Control Center, not guaranteed present-day bonus coefficients. Reaching the total IAS alone did not unlock the building: completing the qualifying mission was the trigger. The actual discovered mission level can differ from the level selected for a scan.

350 is a progression milestone, not a universal first purchase
The historical guide used 350 to reach the final recorded building unlock. That does not prove rushing there has the best payback. A smaller account can stop earlier while it learns mission costs; an established account can advance faster if it can fund and complete the missions. In particular, recheck the Lithium Electrolysis Lab and Anomaly Analysis Center effects in current Techinfo rather than treating this old table as a current bonus specification.

Qualifying mission checkpoint | Recorded Control Center building | Historical effect to recheck
50 | Intergalactic Recovery Center | Ship rewards, if those are part of your routine.
100 | Lithium Electrolysis Lab | Lithium-related rewards; verify its current effect after beta16.
150 | Metal Recycling Unit | Metal rewards.
200 | Crystal Finishing Station | Crystal rewards.
250 | Anomaly Analysis Center | Dark Matter rewards.
300 | High-Pressure Deuterium Tanks | Deuterium rewards.
350 | Catalytic Converter | Lower resource input for Lithium conversion in the historical tests.

Map total IAS to a scan setting and a mission range

Keep three numbers separate: T is total IAS across your planets; S is the anomaly level selected for a scan; M is the level of the discovered mission. Total IAS sets the maximum selectable level, but you can choose a lower scan level. The documented variation of about ±20% is around the selected level S. It maps mission access, not the size of the reward.

Before any undocumented integer rounding, the working range is approximately 0.8 × S ≤ M ≤ 1.2 × S. At the maximum setting, S = T, so this becomes approximately 0.8 × T to 1.2 × T. If you select a lower level, use that selected value instead of your total IAS. The examples below explicitly assume a maximum-level scan; decimal endpoints are arithmetic, not a claim about the game’s rounding rules.

The reported IAS-693 example fits the level range
At a maximum-level scan with total IAS 693, the arithmetic range is about 554.4–831.6. The observed mission level 658 lies inside it and is about 5.05% below 693. The mission’s selected scan setting was not visible, so maximum-level scanning is an explicit assumption here, not an observed fact.

Do not reverse the percentage the wrong way
From a mission level M alone, divide: S is approximately between M / 1.2 and M / 0.8, before unknown game rounding. For M = 658, that is about 548.33–822.5. Applying ±20% directly to 658 gives the wrong inverse. This only brackets total IAS if the scan used the maximum setting S = T; otherwise the total IAS can be higher. Do not infer an exact account total from a mission card. For the separately reported total IAS 693, also require S ≤ 693, narrowing the compatible selected-level interval to about 548.33–693. That still does not identify which setting was used.

Total IAS T | Selected level S, maximum assumed | Approximate mission-level range
500 | 500 | 400–600
600 | 600 | 480–720
693 | 693 | 554.4–831.6
800 | 800 | 640–960

Observed possible rewards can exceed one billion per mission

The evidence pairs a reported total IAS of 693 with a card-visible level-658 Alien Encounter in PTS beta18. That card displayed approximately 1.415 billion Metal + Crystal + Deuterium in possible rewards for one mission. This supports billion-scale possible rewards at that reported IAS; it does not establish a typical payout or a reward formula.

The five examples below were visually read from mission-summary cards dated 28 October 2026, all on version 13.1.0-beta18 and all PvP combat. Possible Rewards appeared in the mission summary, above separate wave information. The separate Mission Rewards area showed No rewards. These are displayed possible resources per mission, not one wave, an actual claim, net profit or daily income.

The screenshots establish actual mission levels, templates, stars, waves and displayed reward costs. Total IAS 693 is separately reported for the level-658 example only, not visible on its mission card. The other four IAS totals and every selected scan level remain unknown. Every resource amount was marked approximate in the interface, so the sums below are approximate too.

Raw resource units means the arithmetic sum of Metal + Crystal + Deuterium. It is not Metal-equivalent value: one unit of each is simply counted as one. Ships and other non-resource rewards are excluded from this sum. The displayed Reward Costs are shown separately in Lithium units. These rounded interface amounts were not paid or independently verified as the full liability; scan costs, conversion inputs, fuel, delivery costs and losses are not deducted.

For planning at a different IAS total, first map the mission-level range from the scan setting, then compare current cards of the same template, stars, waves and mode. These five unlike cards support a scale comparison, not a line to extrapolate to IAS 500 or 1,000. More IAS opens higher mission levels; it does not assign one payout to every mission in that range.

The billion-resource example, with units intact
At actual mission level 658: ≈841,230,171 Metal + ≈372,945,376 Crystal + ≈201,254,900 Deuterium = ≈1,415,430,447 raw resource units possible for the mission. The displayed reward cost was 55.418 million Lithium. The reward had not been collected. This rounded Lithium display is a separate cost indication, not a subtraction in the same units and not the full cost of running the mission.

Observed scale, not an expected return or reward ceiling
These five selected cards at actual mission levels 617–772 span roughly 605 million to 1.415 billion possible raw resource units per mission. They differ in template, stars and wave count; class, bonuses and other settings are not fully recorded. This is not a random sample, a confidence interval, an average return, a guaranteed minimum or a maximum obtainable reward. A higher-level card in this set can show less than a lower-level card. Do not fit one global reward curve through them.

Actual mission level | Mission template, PvP | Stars / waves | Possible M + C + D, raw units / mission | Displayed reward cost, Lithium
617 | Alien Encounter | 3 stars / 7 waves | ≈670,450,730 | 24.25M
658 | Alien Encounter | 5 stars / 9 waves | ≈1,415,430,447 | 55.418M
748 | Alien Encounter | 5 stars / 4 waves | ≈607,756,824 | 27.999M
766 | Medium Alien Encounter | 5 stars / 5 waves | ≈637,096,077 | 35.841M
772 | Chaos Mission | 4 stars / 5 waves | ≈605,341,038 | 28.897M

Turn possible rewards into a measured return

1. Record the game version, total IAS, selected scan level and actual mission level separately. Keep the mission type, stars, mode, waves, class, bonuses, participation and claim fraction alongside each result. Compare like with like.

2. Record the total actually claimed across the mission, not one wave copied as a whole-mission total or the possible reward shown before completion. Treat an unknown value as unknown.

3. For a given IAS band, divide the total actual reward by all attempted comparable missions if you want a return that includes failed attempts. Keep reward per successful full claim as a separate measure. Several observations are more informative than one lucky card.

4. Observe a full real day or week, including waiting for Lithium, travel and attention. The simplest gross daily return is total actually claimed over that period divided by elapsed days. Keep denominators matched: average per attempt × attempts per day, or average per successful full claim × successful full claims per day. Never multiply an average that already includes failures by successful completions only.

5. Subtract the resources spent producing the Lithium for scans and claims, plus delivery costs, fuel and unrecovered fleet losses. Use a stated exchange rate if combining Metal, Crystal and Deuterium into one value. Do not treat Lithium as free because it is produced in a building.

6. Compare the measured extra daily net return with the price of the next IAS upgrades. A rough payback is upgrade cost divided by extra daily net return, in the same value units. If the extra return is zero or negative, that calculation gives no positive payback.

A large card is an opportunity, not income already earned
The observed level-658 card offered ≈1.415 billion raw resource units, but its collected-reward area was still empty. Keep that possible amount separate from the amount actually claimed and from the resources needed for its displayed 55.418 million Lithium reward cost, subject to confirmation when claiming. Value Metal, Crystal and Deuterium with an explicit exchange rate before comparing net returns. No daily-income figure can be inferred from this card alone.

Patch changes that an old Orion guide can miss

The preserved source is guide 0.19.6, dated 11 October 2026, commit 56a951b, describing PTS v13.1.0 beta13. Later official changes take precedence. This list explains specific limits; it is not a complete changelog or a claim that beta17 is the newest release.

No universal Lithium-income calculator
The old production example used an inferred ×10 economy factor and lacked fresh post-rebalance validation. It is not used here as a current income prediction. Read live hourly input/output and storage figures instead.

Date / patch | Verified change | Planning consequence
8 Oct 2026 / beta13 | IAS construction scaling changed from 1.4 to 1.5; Lithium base production changed to 15.36. | Old cost and production estimates must be version-labelled.
13 Oct 2026 / beta15 | Lithium storage limit added. | Discard the old unlimited-storage claim; check the current cap.
16 Oct 2026 / beta16 | Explicit Lithium rewards removed; any reward claim can give additional Lithium by chance. | Do not budget guaranteed Lithium from a mission reward.
21 Oct 2026 / beta17 | Anomaly ship rewards rebalanced. | Earlier ship-yield samples cannot quote present-day returns.

What the preserved cost model calculates

For the historical IAS model, the base resource costs are 84 Metal, 42 Crystal and 14 Deuterium. At target level L, the formula is floor(Base × 1.5^(L − 1)) separately for each resource. A current-to-target result sums each next level through the target. The implementation uses exact integer arithmetic with 3/2, not floating-point estimates.

The beta13 official notes increased the scaling factor from 1.4 to 1.5. The preserved calculator follows 1.5, represented exactly as 3/2. Its outputs remain historical projections and require a live-price check before use.

This calculator prices one planet only. A combined account target of 350 means adding the scanner levels on all eligible planets; do not type 350 into a single-planet target field. For a network, calculate each planet separately and add the same resource columns. Prices exclude prerequisites, facilities, transport and opportunity cost.

Worked historical example: IAS 0 → 2
Level 1: 84 Metal + 42 Crystal + 14 Deuterium.
Level 2: 126 Metal + 63 Crystal + 21 Deuterium.
Combined projection: 210 Metal + 105 Crystal + 35 Deuterium.
This verifies the calculation method, not today’s in-game pricing.

A final check before the next build

1. Confirm Orion activation, current prerequisites, construction prices and your usable planets in the destination universe.

2. Keep total IAS, each local IAS level, actual mission level and completed-mission unlocks separate.

3. Compare one live construction price against the historical model before using its network table or calculator. A mismatch means stop relying on that projection.

4. Reserve enough Lithium for the scan and the reward claim, and price the ordinary resources used to make it.

5. Use actual claimed rewards and sustainable completion rates to decide on the next checkpoint. Keep private coordinates, planet names, balances, fleet details and screenshots out of public research.

Quick checks:
- Orion is enabled in my destination, and I have checked its current prices and prerequisites.
- I have a balanced access target, a Lithium budget and a manageable first mission.
- I know that a qualifying completed mission, not total IAS alone, triggers a recorded building unlock.
- I keep total IAS, the selected scan level and the actual mission level separate when comparing reward cards.
- I distinguish possible mission rewards from actual claims, net return and daily income, and I am not treating selected examples as an average or a guaranteed payout.
- My next upgrade is justified by current costs and actual returns, not only a possible reward card.

Sources:
Official US merge announcement: targets and November 2026 window; no Orion activation flag stated
https://board.us.ogame.gameforge.com/index.php?thread/108152-ogame-server-merges-and-hardware-upgrade/

Official US version 13.1.0 launch announcement: activation scope on 6 November 2026
https://board.us.ogame.gameforge.com/index.php?thread/108158-version-13-1-0/

Official Project Orion introduction, 30 September 2026: account-wide IAS and reward/difficulty direction, not an exact reward formula
https://forum.origin.ogame.gameforge.com/forum/thread/571-pts-project-orion/

Official-forum Orion FAQ, 30 September 2026; later patch notes supersede changed details
https://forum.origin.ogame.gameforge.com/forum/thread/572-orion-faq/

Official US Orion FAQ: lowering the selected anomaly level is allowed; later patches take precedence
https://board.us.ogame.gameforge.com/index.php?thread/108128-orion-faq/

Administrator-maintained Italian official-forum guide, Orion section 22: selectable level and about 20% variation; checked 9 November 2026
https://board.it.ogame.gameforge.com/index.php?postID=6155595&thread/494520-macro-guida-di-ogame-2-0/

Gameforge launch release: global rollout planned for 30 November 2026
https://www.uberstrategist.com/press-releases/ogame-celebrates-24-years-with-the-launch-of-project-orion-its-biggest-update-in-years

Official Orion 13.1 PTS changelog, including beta13 and later changes
https://forum.origin.ogame.gameforge.com/forum/thread/568-orion-version-13-1/

Public historical field guide 0.19.6: IAS network model, mission progression and observations, 11 October 2026
https://github.com/TheIlluminate92/ogame-project-orion/tree/56a951bbeca850d00ff1ccca106b05475daa7fb3

Skie v1.6.1 · reviewed 2026-11-09