...
- Confirm client is not on emergency oxygen (CR). Else see CR-SOPs.
- Prepare the client.
- Assign rats to the client.
- Give the necessary instructions to client about friend/wing/beacon.
- If the rat(s) don't get instance, perform a SC-hop.
- If still no instance, let all restart the game (no need to close the launcher), test comms from main menu and try again with rats in SC ready for beacon and wing.
- When clearing a case, assign a rat to the paperwork
- Every rescue where a rat moved and client disappeared from comms is to be marked as a successful rescue so we have the information on it.
- If no rat was assigned or it was a repeat signal, please add it to the deletion-list with giving a reason.
...
- Let client get his current system and log them out into main menu.
- Make sure they don't log in until told otherwise.
- CRs are usually performed by 3 rats to rise the possibility of instancing with the client.
- Get a location in system and place rats accordingly.
- Give the instructions on beacon and wing to client and log them into open play.
- If client is far out, let rats get a bearing and distance and log them out into main menu again until rats are in position.
- If the rats can't get instance, distance to beacon can be helpful to see if client is in exclusion-zone. In any case, log client out again.
- If client is in exclusion zone (EZ), rats need to perform a TFP (tactical faceplant).
- If client is not in EZ, let all restart the game (no need to close the launcher), test comms from main menu and try again with rats in SC ready for beacon and wing.
- If client is in open space (not close to any structures), rats may wait at the drop in normal space for next login of client and do a short SC-hop followed by a nav-lock-drop if the client doesn't respawn right in front of them.
...