SC NOMADS
Checking your account…
Back to the field guide
GATHERING / VISUAL FIELD GUIDE

Hunt, gather and fulfill collector requests

Bring the exact requested item back without losing track of its purpose.

Getting startedSolo carefully; partner recommended in dangerous terrain17 min read
Transport with storage for the requested items
01
STEP 1 OF 13

Read the requested item before going out

Collector contracts ask for specific resources or objects. The 4.1 release introduced Wikelo and Rayari requests; later patches expanded the surrounding activities.

Record the exact item name and quantity. Our suggestion: finish one small request before building a large collection with no confirmed use.

  1. 1

    Identify the requested species or resource

    Separate controls: F1

    Read the collection or hunting objective and note its exact target, quantity and submission destination. Decide whether you need a kill, a carried item or a handoff.

    What you should see

    You can distinguish the requested evidence from unrelated loot.

    That did not happen

    A visually similar plant, animal or item is not necessarily accepted by the mission.

    RSI Missions and Contracts, updated 22 Jun 2025
Read the complete guide as text

The same published instructions in one readable view. Use the steps above for controls and practice panels.

Read the requested item before going out

Collector contracts ask for specific resources or objects. The 4.1 release introduced Wikelo and Rayari requests; later patches expanded the surrounding activities.

Record the exact item name and quantity. Our suggestion: finish one small request before building a large collection with no confirmed use.

Identify the requested species or resource

Separate controls: F1

Read the collection or hunting objective and note its exact target, quantity and submission destination. Decide whether you need a kill, a carried item or a handoff.

Expected result: You can distinguish the requested evidence from unrelated loot.

If it did not work: A visually similar plant, animal or item is not necessarily accepted by the mission.

Read back the exact order before collecting

SC Nomads practice: make a small order record from the accepted objective: issuer, contract, exact item name and variant, required quantity, destination, and any displayed time limit. Write numbers with their units. A kill counter, a carried specimen and an item delivery are different objectives.

Read the current reward before committing. The Alpha 4.10.2 notes add Wikelo recipes; an older recipe list is not a promise that your offer has the same ingredients or reward. This general lesson does not replace the separate Wikelo introduction walkthrough.

Identify the requested species or resource

Separate controls: F1

Read the collection or hunting objective and note its exact target, quantity and submission destination. Decide whether you need a kill, a carried item or a handoff.

Expected result: You can distinguish the requested evidence from unrelated loot.

If it did not work: A visually similar plant, animal or item is not necessarily accepted by the mission.

  • Exact variant recorded
  • Quantity and unit recorded
  • Accepted destination recorded
  • Kill count or physical handoff distinguished

Equip for the environment and the creature

Kopion behavior includes greater danger in a pack. The source release describes several surface and cave biomes; it does not guarantee a particular spawn for your current session.

Bring compatible ammunition, treatment, light and free storage. In irradiated areas, account for environmental protection as well as combat.

Carry room for the result as well as supplies

Separate controls: I

Check environment protection, suitable tools or weapons, medical supplies and empty carried storage. Record the transport location before leaving it.

Expected result: The trip has enough capacity to bring the requested result home.

If it did not work: Do not consume every storage slot with spare equipment if the objective requires collectable items.

Count only items in storage that will leave with you

SC Nomads storage drill: start with usable carried space after supplies, then collect one item and check its actual destination. Compare required quantity, carried quantity, quantity stored elsewhere and the remainder still needed. Keep similarly named variants on separate lines.

Before moving specimens to a ship container, verify the destination can accept that actual item and inspect it again after transfer. Nominal ship SCU is not proof that a particular backpack, armor pocket or container accepts the object. An item visible only in a station warehouse has not travelled with you.

Solo: stop and secure transport before inventory work. With crew: assign one carrier and one objective reader, and call out each transfer. Do not assume a partner carrying the item completes your contract or grants identical rewards.

Carry room for the result as well as supplies

Separate controls: I

Check environment protection, suitable tools or weapons, medical supplies and empty carried storage. Record the transport location before leaving it.

Expected result: The trip has enough capacity to bring the requested result home.

If it did not work: Do not consume every storage slot with spare equipment if the objective requires collectable items.

  • Supplies still accessible
  • First item located after transfer
  • Carried and stored totals separate
  • Return capacity checked

Turn back while you can still bring the load home

SC Nomads return rule: record the parked transport and a reachable safe destination before leaving it. Choose a stop condition based on the required quantity, storage, fuel, time and remaining survival supplies. Leave when that limit is reached rather than filling every slot because more specimens are nearby.

If a radiation or environmental warning appears, stop extending the collection run and use the prepared exit. This lesson does not establish a safe exposure time or protective equipment threshold. A partner can help with carrying and observation, but does not make a hazardous area safe.

Use the central landing cards when the return destination requires clearance. These retain the original annotated controls; they do not prove a particular outpost has a landing service, buyer or collection terminal.

Contact the port within service range

Choose the applicable control: Left Alt + N or F11

Approach the spaceport at a controlled speed and request landing. If the shortcut does not connect, use F11, find the local Landing Services entry and call it.

Expected result: ATC acknowledges you and assigns a marked hangar, pad or docking port.

If it did not work: If no service appears, check that you are near the actual spaceport. Continue a careful approach without entering restricted space.

Identify the assigned entrance before descending

Follow the assignment marker, stop outside it and identify the opening and floor orientation. Read any docking instruction if the port assigned a dock rather than a hangar.

Expected result: You can point to the assigned entrance and a clear approach path.

If it did not work: If the marker points elsewhere, do not use the nearest open door. Back out of traffic and recheck the assignment.

Field note: Different input? Open Options > Keybindings, choose your device, then Advanced Controls Customization. Read the named action before changing it. Submit corrections through this guide’s normal edit proposal.

Inspect the harvested item and keep it identifiable

Use the available interaction on the resource or defeated creature and verify the resulting item in inventory. Keep requested variants separate when names are similar.

Before returning, check quantity against the live contract. At handoff, confirm the recipient accepted the material and the objective progressed.

Verify the objective after the first specimen

Separate controls: F

Use the actual collection interaction on a suitable item, or complete the contract's hunting action. Then check inventory and objective progress before repeating.

Expected result: The carried item or mission counter confirms this is the right target.

If it did not work: If progress remains unchanged, inspect the objective rather than repeating the same action across a whole region.

Submit the collection at the specified destination

Return with the requested quantity and follow the named recipient or terminal handoff. Check the completion state before selling or using leftover materials.

Expected result: The contract recognizes the submitted result.

If it did not work: Having items in a backpack is not always the final delivery step. Read the remaining accepted objective.

  • Exact request recorded
  • Hazards planned
  • Items inspected
  • Handoff recognized

Prove one specimen matches before repeating

SC Nomads first-specimen check: compare the full name in the inventory or objective with the order record. Check prefixes, environmental variants and item condition requirements when the contract states them. A similar icon, a defeated animal or a promising location is not the requested result.

Use the original collection card, then inspect what actually changed. For a hunting counter, check the objective count. For a physical collection, find the resulting item and count it in the container you are carrying. A delivery counter may remain unchanged until handoff; inspect the remaining objective before calling collection a failure.

The historical Kopion introduction describes broad biomes and pack aggression, not a guaranteed present-day spawn. The Quasi Grazer egg Atlas entry does not establish a current harvesting control, exact spawn or container requirement. Do not invent a route or harm an animal merely because an old guide says eggs exist.

Verify the objective after the first specimen

Separate controls: F

Use the actual collection interaction on a suitable item, or complete the contract's hunting action. Then check inventory and objective progress before repeating.

Expected result: The carried item or mission counter confirms this is the right target.

If it did not work: If progress remains unchanged, inspect the objective rather than repeating the same action across a whole region.

Field note: Different input? Open Options > Keybindings, choose your device, then Advanced Controls Customization. Read the named action before changing it. Submit corrections through this guide’s normal edit proposal.

Separate transfer, submission and reward collection

SC Nomads handoff check: reopen the accepted objective and compare its destination with your current location. Follow its recipient or terminal instructions with the requested items. Check the displayed quantity before confirming, then inspect the remaining objective and completion result.

Moving items into local storage, lowering a freight elevator and submitting a contract are separate observations. None alone proves the others occurred. If a quantity remains outstanding, compare the exact variant, selected inventory source and accepted destination before offering another set.

After completion, inspect where the stated reward arrived and move physical items into storage that will leave with you. Keep unused ingredients separate. Do not sell, consume or discard a remaining specimen until you understand whether the accepted objective still needs it.

Submit the collection at the specified destination

Return with the requested quantity and follow the named recipient or terminal handoff. Check the completion state before selling or using leftover materials.

Expected result: The contract recognizes the submitted result.

If it did not work: Having items in a backpack is not always the final delivery step. Read the remaining accepted objective.

Rayari recovery: try Place instead of Drop

Displayed inventory and item Place action

If loose Rayari delivery items disappear when dropped at the designated freight elevator, a player report from 18 January 2026 suggests one bounded alternative, confirmed by another player on 11 March. Their builds were not stated. Take one matching item into your hand from inventory, close inventory, choose the offered Place interaction and confirm its placement preview on the delivery platform. Use the current displayed controls; this note does not establish a current key chord.

Expected result: Check whether that one item remains visibly placed. Follow the accepted contract’s actual submission step, then reopen the objective and read its remaining item counter. Placement alone is not completion.

If it did not work: This is a dated reported workaround, not a guaranteed fix. If Place is absent, the item still disappears or the counter does not advance after the required submission, stop with the remaining stock secured and record the exact stage. Do not repeat with the whole load or assume this applies to every collection mission.

The items moved but the contract did not complete.: Check the remaining accepted objective, exact item variant, quantity and destination. Preserve the terminal result. Do not submit another valuable batch merely to test whether the first one disappeared.

Record the failed stage and recover the rest of the load

SC Nomads recovery record: note the build, accepted objective, exact item, quantity, original container, destination container and what changed. This distinguishes a missing specimen, a rejected transfer, an unrecognized handoff and a missing reward.

The current known-issues page describes held-item problems after some logouts and mission-history clearing on client exit. Do not treat a vanished history row alone as proof that a completed result was erased, or promise that logging out will recover carried loot. Secure items in appropriate storage and inspect the result before ending the session.

If the stage remains blocked, stop risking additional ingredients. Check a matching Issue Council report and preserve useful evidence without exposing other players. Choose a safe return with the remaining load. No universal refund, item recovery or spawn guarantee is established here.

Write a useful failed-stage record

SC Nomads collection record

Record the exact stage and item movement once, then compare a matching report with your installed build. Submit a guide correction when the instructions disagree with the current interface.

Expected result: The next attempt has a specific question and the surviving load is accounted for.

If it did not work: Do not repeatedly abandon or repeat a costly contract as a diagnostic experiment. A historical workaround for a different item is not evidence that it applies to this one.

Pitambu field trip: choose the fruit, not a recipe substitute

Use this optional exercise to bring one identified plant item home before accepting a valuable collection order. The existing Atlas Pitambu entry lists Hurston and microTech as dated regional leads. Choose a world you can safely return from; those leads do not promise a plant beside your landing spot. Set a short search limit and keep the parked transport in sight or otherwise reliably located.

Look for the offered item name Pitambu. Its extracted description identifies waxy skin with green leaf-like growths and red flesh containing small white seeds. Appearance is a clue, not sufficient proof: inspect the actual loose item. The source is an extracted 4.10.2 record, not a present-server observation.

Do not replace a requested horn or egg with this fruit. The separate Wikelo introduction specifies Tundra Kopion Horn; its walkthrough already covers that hunt. A request for another animal variant, an egg or a quality bracket must be matched on its own terms. This trip has no promised reward, buyer or Wikelo unlock.

Identify a collectible before taking it

Displayed loose-item interaction

Move close enough to read the offered item interaction. Choose Inspect when available and read the full name. Confirm Pitambu before using Carry or Store. Do not fire at plants or animals to test this fruit route.

Expected result: The interaction identifies Pitambu, rather than only a decorative plant or a similar food icon.

If it did not work: If there is no offered collectible or the name differs, leave it uncounted. Search only within the planned return limit; do not turn an empty area into a guaranteed spawn claim.

Field note: Different input? Open Options > Keybindings, choose your device, then Advanced Controls Customization. Read the named action before changing it. Submit corrections through this guide’s normal edit proposal.

Store one Pitambu and prove where it went

The dated item record exposes Carry, Inspect, Store and Consume. For a collection trip, use Store when offered, or Carry followed by the available storage interaction. Consume uses the food; it is not a storage shortcut. A held fruit is not yet proof that it is inside the container you will take home.

Keep ordinary food supplies separate from collection stock. In particular, do not taste a nearby item to identify it: the separate Sunset Berries description warns that they are toxic, despite having a Consume interaction. This is a source warning, not a measured safe dose or a tested treatment.

Keep the first fruit instead of eating it

Displayed loose-item interaction

Select the offered Store action. If you are holding the item, use the displayed storage option and then inspect your carried container. Locate the named fruit before repeating the collection.

Expected result: One matching item is visible in the container that is travelling with you.

If it did not work: If Store is unavailable, check actual carried space and the offered interaction. Do not substitute Consume. If it was eaten or dropped, record zero secured fruit until another item is visibly stored.

Check the carried kit before leaving the area

Personal Inventory / displayed inventory prompt

Open the available inventory view and identify the container holding your collection. Keep a note of the item name and visible quantity, separate from anything in a station warehouse.

Expected result: You know which carried container must reach the return stop.

If it did not work: If the item is only in a different location inventory or still lying outside, it is not ready for transport. Secure the actual item before extending the trip.

Return with the same named item, then decide its destination

Return using the existing route and landing cards. At a safe Storage Access kiosk, press F and use the inventory interface to move the fruit into the intended local container if it accepts the item. Inspect the destination after transfer. Local Inventory remains at that location; it is not remote access to the collection from your next planet.

For this practice, success is the named fruit accounted for after the return, not a payout. If you accepted a real collection objective, reopen it before transferring anything to a recipient: compare the named ingredient, any stated quality, amount and delivery location. The contract determines the submission method. A generic commodity terminal, a freight movement or possession alone is not a proven Wikelo hand-in.

Reconcile the returned fruit at the kiosk

Separate controls: F

Interact with Storage Access

At the safe return stop, access the kiosk and select the inventory holding your carried item. Transfer only if the destination accepts it, then inspect that destination for the same name and quantity.

Expected result: The fruit is either still in its known carried container or confirmed in this location storage.

If it did not work: If it seems missing, check source and destination once, including a held or dropped item. Stop moving more stock while the discrepancy is unresolved. Logging out is not an established recovery method.

Choose practice storage or the actual accepted recipient

Accepted collection objective

Keep the practice fruit unless an accepted objective explicitly requests it. For a real order, read its recipient and submission instructions, select only the matching stock and inspect the resulting remaining objective.

Expected result: The practice has a recorded storage location, or the real order shows the actual accepted delivery result.

If it did not work: A rejected transfer is not a reason to consume, sell or replace a named ingredient blindly. Preserve the remaining load and compare the exact objective before another attempt.

  • Pitambu identified by offered name
  • Collection stock not consumed
  • Carried container identified
  • Returned quantity reconciled
  • No invented recipe or buyer

Before you commit

A creature’s presence does not guarantee the desired drop. Do not rely on an old loot table or assume an irradiated variant can substitute for another item.

Some carried resources can be hazardous. If the item or location presents a radiation warning, manage exposure and transport rather than ignoring it for the reward.

Version history

Sources & guide information

Sources checked 13 October 2026. Not gameplay verified on Alpha 4.10.2.. Reference information, not a claim of current-patch playtesting.

CIG Alpha 3.23: Kopion and Marok behavior introductionCIG Alpha 4.1: Hathor, mining and collector missionsCIG Alpha 4.2: ASD, radiation and refinery changesRSI Missions and Contracts, updated 22 Jun 2025RSI Equipping Your CharacterCIG Alpha 4.10.2 release notes; Wikelo recipe changes, checked 19 October 2026CIG Alpha 4.10.2 Known Issues, updated 9 October 2026; checked 19 October 2026Rayari player handoff report, 18 January 2026; confirmed 11 March 2026; build unspecified; checked 21 October 2026Pitambu item identity and interactions: extracted 4.10.2-LIVE.12881860; checked 21 October 2026; not a gameplay testSunset Berries item warning: extracted 4.10.2-LIVE.12881860; checked 21 October 2026; not a gameplay testCIG Commodities, updated 24 July 2026; checked 21 October 2026