Ship-to-ship refueling after the overhaul

Separate your flight fuel from the fuel you sell

Hydrogen supports normal maneuvering; Quantum Fuel supports quantum travel. Your tanker’s own reserves and its sale pods are separate checks. The current lesson follows the 4.8 refueling overhaul.

Current / total

The first value is fuel present; the second is capacity. Neither is a promise that the current customer needs that much.

Operator mode

A working configuration for the vehicle. Refueling mode presents the equipment and interface needed for the connection.

Write sale stock and flight reserve on separate lines

SC Nomads departure check: read each pod type and its displayed current/total amount. Copy the current amount with its unit, then record the tanker flight-fuel state separately. Check the receiver request against the sale stock; a full flight tank does not fill an empty sale pod.

Have the receiver read its Hydrogen and Quantum Fuel state before the trial. Agree the requested type, amount and affordable total. Choose a small first transfer whose result you can compare, rather than advertising the sum of empty pod capacities.

The 4.10.1 notes record a fix for incorrect contract fuel amounts and introductory contracts requesting both types. Read the actual accepted objective; an older mission description is not a reason to add a second fuel purchase.

• Pod type and current stock recorded
• Flight reserve recorded separately
• Receiver need and units read back
• One agreed initial purchase

Choose a small first customer

SC Nomads practice: complete one friend-to-friend transfer before offering a long paid trip. If flying alone as the tanker operator, start with an eligible single-recipient NPC job.

Field note: Both roles can be performed by different players, while an AI recipient lets one human operate the tanker. A friend aboard is useful for lookout and communication; the pilot still needs to coordinate the connection.

Out of fuel? Request help as the receiving pilot

Receiver route, based on CIG’s 4.8 introduction. Service availability still needs current-build confirmation; this is not a live test.

Deploy the nozzle before the approach

Rehearse this without a nearby customer. Observe the mode change before moving closer.

Assign who requests, who moves and who confirms connection

SC Nomads two-pilot rehearsal: the tanker pilot confirms the refueling HUD and deployed nozzle, then both pilots identify the selected ship. Agree which pilot sends the request and which follows the approach guidance. Call stop before either changes an uncertain approach.

Either player can initiate docking; contract AI does not initiate it. A solo human tanker operator can serve an AI recipient, but cannot also occupy a separate player receiving ship. A lookout helps communication and clearance; that does not add another connection or replace a pilot.

Use the original mode and docking cards below. Read the actual connected state before opening a purchase screen. A request message alone is not a connection. No distance, alignment tolerance or universal ship compatibility is established here.

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.

Identify the recipient before requesting docking

Agree which player moves and which holds position. AI recipients do not initiate the request. Keep a clear approach and read the docking guidance instead of rushing toward the nozzle.

Read the quote aloud before the receiver confirms it

SC Nomads receiver drill: open Vehicle Maintenance, identify the fuel type and amount, and read the displayed total to the supplier. The supplier identifies the matching stocked pod and its open state. Confirm one agreed transaction, then tell the supplier which purchase state appeared.

The 4.8 flow starts fuel delivery after a purchase when the relevant supply pods are open. Compare the receiver fuel display with the starting record while the supplier watches stock and progress. Keep the displayed units; do not turn a percentage into an invented fuel volume.

If the quote does not match the agreed order, stop before confirmation. If the purchase was confirmed but fuel does not change, distinguish missing connection, purchase state and empty or closed supply. Repeating the purchase is not a diagnosis.

• Receiver type and amount match
• Displayed total agreed
• Supplier stock and open state checked
• Purchase and actual fuel change distinguished

Check the quote, then follow the transfer

For a player customer, the receiver purchases fuel through Vehicle Maintenance. The supplier opens the relevant stocked pods. The current flow does not require an old manual-pressure balancing exercise.

• Recipient confirmed
• Amount and total read
• Transfer observed
• Completion verified before departure

Diagnose a stopped transfer by its stage

SC Nomads drill: have the receiver call “connected”, “purchase confirmed” and “fuel arriving”. Those are separate checkpoints.

Nozzle and pod choice

The 4.8 overhaul makes flow rate depend on equipment; old advice about manually raising pressure until a nozzle breaks is obsolete.

Two fuel types

When both are requested, the documented order is Hydrogen followed by Quantum Fuel. Read the current stage before treating a waiting Quantum amount as a fault.

Abort an unsafe transfer and account for what actually arrived

The active 4.8 interface retains payment information, a process timeline and Abort. SC Nomads stopped-transfer drill: call the last state both pilots saw, read the current fuel and stock, and use the visible Abort control if the operation cannot continue safely. Observe the resulting process and connection state before attempting separation.

Compare the receiver starting and ending fuel readings in the same units. Record the displayed payment result and remaining pod stock separately. A quote is not a receipt, and a receipt is not proof the full requested quantity arrived. Do not promise that Abort refunds a particular amount.

If the interface still shows a connection, coordinate with the other pilot and use the original closeout guidance after the operation has stopped. Do not pull away with thrust or restart a purchase to try to force the ships apart. Preserve a matching build and failed-stage record for an Issue Council report.

Close the connection before moving away

Finish the transaction first, then create separation. For a contract, the mission result is the receipt.

Verify release, the customer result and the next trip separately

SC Nomads departure check: read whether the connection is already released before using a docking toggle again. When release is needed, use the original closeout card; then have both pilots confirm they can depart independently. Payment, delivered fuel and released connection are three different checks.

For a contract, reopen its actual completion result. For several recipients, record which target remains unfinished and recalculate stock before moving to it. Check the tanker flight reserve again; the fuel left for sale is not a return-route allowance.

The current known-issues page describes delayed station Landing Services. That station workaround does not establish a ship-to-ship transfer fix. The 4.10.2 notes and issue review are source context, not an SC Nomads live refueling test; use the present interface if it differs from these 4.8-derived steps.

• Release visibly confirmed
• Receiver fuel result recorded
• Payment or contract result checked
• Remaining customers and stock recorded
• Tanker return reserve rechecked

Before you commit

Some distress contracts are ambush variants. A fuel truck still needs an escape plan.

A tanker’s flight fuel and fuel available for sale are separate planning concerns. Reserve your own trip home, and do not advertise capacity you have not checked at the console.

M does not show refueling controls.: Check the occupied seat, refueling capability and Toggle Refuel Operator Mode binding. Mining and salvage also use context-sensitive modes.

I can buy fuel but none arrives.: The receiving and supplying roles have different checks. Verify the purchase state, connection and appropriate pod stock/open state. Use Abort if the operation cannot continue safely.

I cannot refuel two ships simultaneously.: Plan sequential connections. A second player can help with navigation and safety, but does not create another nozzle or guarantee parallel service.

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.