Skip to content

Resources & Automation

Grey Expedition Controls: Check the Ore Cost

Evidence checked: November 6 developer answer and resolved player follow-up · reviewed November 7, 2026

The short answer

Check the expedition’s required ore before treating grey assignment controls or Waiting status as an expeditioner-count bug. The developer explains that expeditions consume ore mined from the star chart, and a missing requirement appears light red or pink. The opening player and other participants confirm that overlooking those costs caused their assignment problem.

On this page

Read the displayed ore as a cost to fund

  1. Open the intended destination or its entry in the Expedition Manager.
  2. Inspect the ore required to launch the trip.
  3. Compare those requirements with the stock actually available, paying attention to light-red or pink amounts.
  4. If ore is missing, obtain the relevant mined resource before trying to assign the intended expedition size again.
  5. Recheck the controls and observe whether the funded expedition can proceed.

The thread describes expeditions returning their own special ores, relics and SEALS. That reward does not make the mined ore shown for launching the trip another reward; it is an input the trip needs.

Why a large pool of idle people does not prove a population bug

The opening player has 338 expeditioners and cannot assign them to several destinations. Other participants report the same symptom with much smaller pools. Those numbers describe their saves, not a documented maximum or minimum for assigning a trip.

The developer first asks whether the required ore is available. After that explanation, the opening player says they had stopped gathering it while feeding resources to the Void and confirms the issue is resolved. Another participant also acknowledges missing the ore requirements.

Keep repeat expeditions funded

Review what other systems are consuming the same mined resources before committing them all. An unlocked destination and available expeditioners do not guarantee enough ore for the next departure.

The separate Auto-Dispatch advice makes the same condition explicit: automation continues only while your production can fund the configured expeditions. If the controls remain blocked with the actual requirements met, retain the destination, allocation and save details for a support report; this explanation does not rule out every possible bug.

The resource diagnosis is confirmed when replenishing the missing requirement makes the intended assignment or departure possible. If that does not happen despite sufficient resources, report the actual state rather than forcing the original thread’s answer onto a different failure.

Sources & version

Expeditioner Bug?, November 6, 2026, opening post and all seven replies. joffarex explains the ore cost and light-red/pink warning; SlimThicky, Gene and depg acknowledge the misunderstood requirement. Fun vs. Grind, November 7, provides Valborg’s separate resource-funded Auto-Dispatch example. No complete port-price table or population limit was inferred.