Escort a hauler or industrial crew

Agree protection and disengagement rules

Before departing, confirm the protected ship, route, group leader and response to contact. Agree whether the escort observes, deters or fights, and what makes the convoy leave.

Expected result: The hauler and escort know the same plan and can distinguish their own group.

If it did not work: Do not assume every unknown contact authorizes an attack. Read the local law and the contract scope.

Read back roster and retreat call

mobiGlas > Commlink > party contacts

Invite the intended contacts and have each person acknowledge their handle, ship and job. Test the agreed channel with the break-off and rally words.

Expected result: The client and escort can identify their own people and the person making the escape call.

If it did not work: If voice fails, establish an acknowledged text fallback before departure. A party list alone is not a working communication check.

Rehearse one meeting and departure

mobiGlas > Maps > agreed rendezvous

Each pilot selects the same accessible point, reports arrival and visually confirms the other ship before moving together.

Expected result: The group can find the client and rally point without relying on a guessed marker.

If it did not work: If one player cannot reach the point or is in another session, solve that first. Do not load the valuable cargo while the escort is still trying to join.

Verify any shared mission separately

mobiGlas > Contracts > Accepted > Share

The holder selects an actually shareable mission. Each invitee reads and accepts their prompt, then checks their own accepted entry.

Expected result: Only people who accepted the offered mission count on its stated shared conditions.

If it did not work: If Share is absent or the invite was not accepted, do not claim party membership shared the contract or its reward.

Rehearse the regroup with an empty ship

Share the planned destination and a fallback marker. Make a short practice movement and confirm every pilot can find the regroup before carrying the valuable load.

Expected result: A separated pilot has a named place to go without waiting for a crisis.

If it did not work: A fast escort can leave a slow hauler behind. Match the route and calls to the protected ship.

Read each route rather than assuming a group jump

mobiGlas > Maps > destination > route details

Compare destination, next leg and required fuel with the client. Set the fallback and have the client call ready before departure.

Expected result: Every pilot has a usable route and can state the next stop.

If it did not work: If the escort cannot match the route, change the leg or service first. Party membership does not guarantee synchronized quantum departure or identical arrival.

Request the correct port assignment

Request Landing; Commlink alternative

Request your own clearance with Left Alt + N and follow the marker assigned to your ship. Keep the client exit and approach clear.

Expected result: Both ships can leave or arrive without blocking each other.

If it did not work: Do not borrow the client clearance or park in their approach. Ask for a separate usable assignment when the hull or port requires one.

Depart in the correct travel operator

Cycle Master Mode (Long Press) > Next Operator Mode > Engage Quantum Drive (Hold)

When the client is ready, hold B if needed for NAV, cycle middle mouse to QT, align and wait for readiness, then hold left mouse to start your own leg.

Expected result: Your HUD reads NAV/QT and your ship begins the agreed leg.

If it did not work: A route or readiness warning needs diagnosis. Do not assume the escort can automatically pull the client through a jump or clear an obstruction for them.

Hold the watch through the service result

mobiGlas > Landing Services, landed in the pilot seat

The client requests the needed service and checks the resulting readouts. The lookout reports contacts and tells the group before leaving position.

Expected result: The client confirms readiness and the group knows when observation was interrupted.

If it did not work: For the published service delay, allow several minutes, close and reopen the app. If still unavailable, agree a reachable alternative before launching with an inadequate reserve.

Report a contact before chasing it

Call the contact, its direction and the protected ship's condition. Let the agreed leader choose whether to continue, escape or engage, then keep reporting the hauler's status.

Expected result: The protected ship remains the focus of the operation.

If it did not work: If an attacker pulls the escort away, return to the protection plan instead of turning the job into an unrelated pursuit.

Select, read back, then choose a response

Vehicles - Target Cycling > Cycle Lock - In View - Under Reticle

Aim at the intended contact and tap T. Read the selected identity, distance and target indication on the HUD, then call the identity before an engagement decision.

Expected result: The group can distinguish a known friendly, an uncertain contact and the identified threat.

If it did not work: If the wrong contact was selected, withhold fire, aim again and reselect. Your saved profile overrides the inspected default. Check Cycle Lock - In View - Under Reticle if needed, not the separate Lock Target Under Reticle action with no inspected keyboard default.

Check the local legal context

mobiGlas > Journal > relevant legal code

Confirm the system and applicable legal code. Treat the client order and any accepted contract as context, not an exemption from the law.

Expected result: The response plan has an identified target and a lawful scope.

If it did not work: If a shot crosses the client path or creates friendly damage, stop firing, report it and reassess instead of adding more fire.

Confirm SCM before an authorized defensive pass

Cycle Master Mode (Long Press); active weapon preset

If still in NAV, hold B once and wait for SCM. Read weapon and shield readiness. With the identified threat and clear firing line confirmed, use left mouse briefly for the selected weapon preset, then reassess the client and your ship.

Expected result: The HUD confirms SCM and you can observe the weapon response while keeping track of the client.

If it did not work: If mode, target or friendly position is uncertain, stop firing. Break off toward the agreed rally when the client calls it; do not keep making combat passes after losing the protection task.

Verify the client made the regroup

mobiGlas > Maps > agreed rally point

Route to the rally, confirm your own safe arrival and ask the client for location and condition. Resume only after the client acknowledgement.

Expected result: The group knows who is present and whether another recovery step is needed.

If it did not work: If the client is missing, first establish their location and status. Do not blindly repeat jumps to a stale marker or assume every interdiction device or escape path behaves as planned.

Choose service, evacuation or cancellation

Ship status displays; mobiGlas > Maps / Landing Services

Read condition and reachable services, ask the client what is needed, and communicate whether the job continues, changes to recovery or ends.

Expected result: The client has an explicit next action and the escort still has a return reserve.

If it did not work: Do not label the original delivery complete merely because combat ended. If you cannot recover safely, state the limit and coordinate assistance rather than promising guaranteed protection.

Confirm completion and the next safe state

mobiGlas > Accepted contracts / transfer app / Landing Services, as applicable

Have the client confirm the agreed destination and any unresolved damage or payment. Check your own supplies before accepting another escort.

Expected result: Both sides know what completed, what remains unresolved and whether the ships can return.

If it did not work: An unresolved transfer is not a reason to resend blindly. If services or the route are unavailable, agree a revised finish and reachable stop rather than advertising a guaranteed outcome.