This document is not intended to take the place of reading and understanding Dispatch SOP.  This is a guide intended to summarize key points, and then provide further details and options in the finer details.  For information on all Mecha’s capabilities, visit mecha.fuelrats.com.  For a guide on how to file cases, see this page here: How to File Cases / When to !md, !invalid and !delete cases.

Quick Reference Guides

Standard Rescue (Client not on Emergency O2)

  1. !Prep the client
  2. Assign rats to the client
  3. Have the client add rats to a wing/team
  4. If necessary, have the client light their beacon
  5. If the client is far away- check their fuel status, log them out to conserve fuel, if needed
  6. If the rat(s) are inst- or in EZ, investigate these steps, in order:
    • Have client perform SC Hop (remedies EZ, and most inst. problems)
    • Rats and client restart their game/console
    • Test comms (have client send rats a message from comms panel)
  7. When clearing a case, assign the rat that got first limpet to do the paperwork. (Use !close <case> <rat>)

For extenuating circumstances on filing see How to File Cases.

Code Red Procedures (Client on Emergency O2)

Ensure that you have the client's system, and that the client has logged out to main menu.

  1. Ensure client stays at Main Menu until GOGOGO
  2. Assign rat/s to the client
  3. Get the client's oxygen timer and location in system, if possible.
  4. Verify client’s system name (from main menu).
  5. Place rats according to the information you have.
  6. Give the client instructions on how to log into open play, send wing/team invites and check that their beacon is lit.
  7. Confirm rats are in position and that everyone is ready.  Then give GO GO GO signal.
    • No response after ~1 min: resend wing/team instructions to client
    • Inst-: Log out and troubleshoot (relogs, etc.) See Instancing for more information (or console troubleshooting guides)
    • EZ: Instruct rats to TFP
    • BC+ [distance]:  Decide whether to leave client logged in or log them out.  See Supercruise Travel Times for more info.

 Extended Guide (with extra information!)

Normal Cases

Prepping and Greeting the Client

When clients enter #fuelrats you will see the following messages which will give you vital information on the case:

<&RatMama[BOT]> Incoming Client: Grünregen - System: HIP 104045 - Platform: PC Odyssey - O2: OK - Language: German (de) - IRC Nickname: Gruenregen
<%MechaSqueak[BOT]> RATSIGNAL Case #3 PC ODY – CMDR Grünregen – System: "HIP 104045" (G Yellow dwarf 167.5 LY from Fuelum) – Language: German (de) - Nick: Gruenregen (ODY_SIGNAL)

The client must first be prepped, by using any number of prep commands.  An example of this is:

!prep-auto 3
Bitte falle vom Supercruise in den Normalraum und komme zum Stehen. Deaktiviere alle Module AUSSER der LEBENSERHALTUNG (Instruktionen sind bereit, falls nötig). Falls irgendwann der Sauerstoff-Countdown beginnt, lasse es uns sofort wissen.

For more methods of prepping, please see Common Prepping Practices

If the client is using a language other than English in their browser (mecha will indicate this in the ratsignal), you should ask them if English is okay in their browser language.  For example:

Hallo Gruenregen, kannst du Englisch sprechen?

If the client agrees, the rescue can proceed in English (you may choose to use the translated facts, though).  Please note, even if you are a native speaker, the rats on the case may not be.  If the client is capable of reading and responding in English it is to everyone’s benefit that the rescue proceeds in English.

Many dispatchers will take an opportunity shortly after prep to greet the client and ask them to report back once their modules have been turned off.  It is best if this welcome is kept as short and simple as possible so as to avoid confusion. An example is:

Welcome to the Fuel Rats Gruenregen.  Please let me know once you have those modules taken care of.

It is a good idea as well, while you are waiting for your client to prep and while your rats are calling jumps, to examine the rat signal for potential errors or issues.  You might be looking for a system that is likely wrong(ie: Sol), a system that is incomplete (ie: Col 285 Sector), an unusual platform (PC-Legacy), or a client’s commander name being different from their IRC nick.  Mecha will also attempt to provide mostly accurate information about the client’s system and online status, but it is not infallible.

Once the client has responded to your prep-query, you can proceed with assigning rats!