Wrong System

Clients are sometimes unfamiliar with the navigation system and panel readout.  This leads to them making one or more of the following mistakes when reporting their system:

  • Clients often look at their targeting display rather than their navigation panel, leading them to report their destination system (since it’s targeted) rather than their actual system.  This may also cause them to report “Unexplored” or “Deep Space” as their location.
    You can avoid this by checking the client’s location on the Galaxy Map once they are friended: A green icon will appear on the Galaxy Map representing the in-game location of each person on your friends list, and the first tab of the Galaxy Map will also identify each friend located in the currently highlighted system.
    Xbox Note: The Xbox profile will show the current system of each player that is in game unless that player is accessing Xbox Live through multiple devices at the same time (such as the Xbox and  Smartglass App).  This allows for a quick way to confirm the client’s location without having to navigate the Galaxy Map.
  • The game’s font makes certain letters and numbers look very similar to the untrained eye.  Common mistakes involve the numbers 0,1,2,5,8 and the corresponding letters O,I,Z,S,B.  
    All procedurally-named systems follow a fixed format of ending with “LL-L LN-N” or “LL-L LN”, where “L” represents a single letter and “N” is one or more digits.  Not all clients realize this, so they may think the second portion is a number (e.g. “84” when it’s really “B4”)
  • Clients occasionally report the name of the currently targeted body or their “neighborhood” rather than their system name.  This is usually the case if the last part of the system name is something like “B” or “AB 2”.  In most cases, the system name is the same as the planet/star name minus the suffix, so it’s easy to determine the correct name.

In all cases, notify dispatch if the client’s actual system is different from their reported system so that the case can be updated with the correct information and other rats assigned to the case can reroute if necessary.

Attempted Supercruise to Next System

Some clients — especially newer players — may attempt to supercruise to the next system over when they find themselves without enough fuel to jump.  This situation can also occur from players going AFK while in supercruise.  Either way, this results in players that are may be 100kLS+ from the main star and drastically increases the potential search area.  Worse, clients who attempt this usually find themselves completely empty of fuel — which means they become Code Red rescues on emergency oxygen and are logged out to the main menu.

If a client still has fuel and is in game, a player’s wing beacon makes it easy to locate them.  If a client is unsure of their distance (which they can check by looking at their navigation panel and reporting the distance to the main star), the rat(s) can drop to normal space and obtain the distance to the wing signal.  This is useful when the client is close to running out of fuel and an estimated time for the rat(s) to arrive is needed to determine if the client should log out to the menu to save that remaining time or not.

If a client in this situation is Code Red (likely), the common practice is to have a rat determine the client’s direction and approximate distance and have multiple rats fly out so that one is at about that distance, one some distance before it and one some distance after it.  This can be done without a client login if the client remembers what star they were attempting to reach and their rough distance.  Dispatch will coordinate these cases as needed.

It is not possible to properly supercruise to another system — even if you reach it, it will not load in.  After a rescue attempt on a client in this situation (whether or not it is successful) be sure to inform the client of this fact.

Client too close to star

Some clients — particularly those that are attempting to fuel scoop but may not understand all of the mechanics behind it — may approach a star too closely to allow normal supercruise travel to that client.

In most cases, this is resolved by informing dispatch who will then instruct the client to make a brief hop to put some distance between them and the star.  In CR cases though, clients cannot supercruise and thus it may be necessary to perform a tactical faceplant.

Client in unsuitable game mode

Clients may be in solo or private group mode. Rats can spot the game mode after fr+ and should notify dispatch if client is not in open.


3 Comments

  1. Maybe include that clients are often in the wrong game mode?

  2. oh, also maybe add something on prep-/checking for shields

  3. > "You can avoid this by checking the client’s location on the Galaxy Map[...]"

    Information about checking for system/game mode via comms panel should be added.

    > "[...]the rat(s) can drop to normal space[...]"

    No longer required; rats can gather distance to BC in supercruise.