Common Client Mistakes

Client in unsuitable gamemode/version

Clients can only send a wing/team invite if they are in the same gamemode/version.  Clients may be in solo, private group, the main menu, or one of the various current PC game versions(Horizons or Odyssey).  Rats can spot the game mode after fr+ and should notify dispatch with their fr+ call if the client is not in open. It is also possible the client may be in PC Legacy, which would potentially be indicated by fr-, though this is best determined by the dispatch/a rat in Legacy who can check on their account.  

If the client is currently in a different version, it is good practice to inform dispatch as you or the clients change gamemodes/versions.

Example: #3 FR+ solo / #3 FR+ client in hor, I am relogging / #3 I am back in open ready / #3 client in mm / #3 client in Open

For more information, please see: Elite Live and Legacy Modes

Client in Wrong System

Clients are sometimes unfamiliar with the navigation system and panel readout.  This often 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.

• 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.

The earliest time you can spot a wrong system is on the comms panel immediately following FR+ or on the galaxy map after WR+.  Sometimes system names can be truncated on the HUD icon or in the comms panel, so be careful!  Wrong system calls are commonly bundled with FR+ or a client gamemode update.  

Example:  #3 FR+ sys is Maia

Incorrect commander name

It is important for us to know the client’s correct commander name for record-keeping purposes. Make sure to check the comms panel during the rescue and report any errors!

Example: #3 cmdr is BigJester

Client fails to complete !prep instructions

In some cases, clients may receive the !prep instructions, but not complete them.  This is typically due to not understanding how to execute them and may be indicated by blue shield rings around their icon on the top of your screen when in wing/team (this only applies if the client actually has shields). Dispatch should be alerted if this is the case by using the prep- call. If rats are moments away from refueling the client, they may choose to omit the call, or the dispatch may choose not to act on your prep- report.

Example: #3 WR+ Prep-

If at any point the client’s shields go off without dispatch prompting, it is very likely the client has just turned Code Red. Make sure to report prep+ immediately!

Example: #3 Unexpected prep+!

Client is very, very far away

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 when players go AFK while in supercruise.  Either way, this results in players that are 100kLS+ from the main star and drastically increases the potential search area.  Worse, clients who attempt this usually find themselves completely out 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, rats can wing/team up and report the distance of the beacon. 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 fuel. If the client is extremely far out (e.g. 1ly - 4.5 hours of supercruise time), rats may do a navcheck (see Standard Operating Procedures).

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 / planet

Some clients, particularly those attempting to fuel scoop without an understanding of the mechanics behind it, may approach a star or non-landable planet and impact the exclusion zone. At this point, they are too close to the body to allow a normal navlock drop. Rats should attempt a navlock drop first. If the wing/team signal is still “Mm” or ”Ls” away after drop, the client is in the EZ. Rats should inform dispatch that the client is in EZ.

If the client is not CR, dispatch will instruct them to make a brief hop to put some distance between them and the star.  Rats should go back to supercruise and prepare for a normal navlock drop. It is good practice to update dispatch on the client’s movements.

Examples: #3 in SC / #3 no movement / #3  needs to go farther / #3 good to drop

In CR cases clients cannot enter supercruise, so a tactical faceplant (TFP) may be necessary. Note that only trained rats should perform TFPs. If you are not confident in your abilities, tell dispatch!

Client logs in early during CR rescue

It is possible that a client does not heed the dispatch’s warnings on a CR case, and logs in before the dispatch’s GO GO GO instructions.  This may be because they thought the instructions provided by dispatch were an invitation to log in, they wanted to check their timer to be helpful, or they misunderstood an instruction sent to someone else being rescued.  Every assigned rat is responsible for monitoring the game’s comm panel for any gamemode changes (in this case, logging into open from mm).  Even seconds can make the difference in a CR case, and a login takes at least 15 seconds.  This should be reported immediately to dispatch by indicating that the client is in OPEN.  Please also be aware that if they do this once, they may well do it again.

Client showing as solo bug when GO GO GO

It is common for clients to show as in Solo Play on the comms panel when logging into Open, especially if the countries of the rat and client are far apart or the client has connection issues. This bug usually resolves itself within 10-15 seconds of the client logging in. It is good practice to wait for 5-10 seconds in CR cases to see if it changes to Open Play at login. If the bug is resolved, the rat can report #3 Open as usual. If the client still shows as Solo Play after 10 seconds, they likely logged in to the wrong gamemode which should be reported immediately. 

Example: #3 still showing solo