|Table of Contents|
It takes a special CMDR to want to be a Fuel Rat. Fuel Rats fight against the galaxy’s greatest foes: Time, instancing, distance, and the countdown as a CMDR’s cabin atmosphere runs out. We need CMDRs who are enthusiastic, disciplined, and willing to go way above and beyond the normal call of duty. If we can possibly save a client, we will.
The Fuel Rats is strictly non-PvP. Our only enemy is instancing. As a fuel rat you will use skill and speed to get to clients, and advanced evasion tactics to manoeuvre around obstacles. Refuel, don’t provoke or get provoked.
If you’re our kind of CMDR, we’ll welcome your assistance.
Before you sign up, think about whether you’re willing to:
Cooperate as part of a team, to do great things
Lead when leadership is needed
Follow when following is the right thing to do
Do whatever it takes to rescue clients
Generally be a cheerful, funny, helpful, Fuel Rat
About the Fuel Rats and Our Ethos
"Give a man a fuel limpet, he jumps for a day, teach a man how to fuel scoop they jump for a lifetime"
- CMDR Datalink
The Fuel Rats are a more or less flatly structured collective of equals. By necessity, there is SOME form of management in the form of the Ops Team and the Overseers, but by and large, the Mischief operates by means of unity towards a common goal. Disagreements are worked out by listening to each other, suggesting solutions, and (hopefully) deciding collectively what to do. The “collective” is a team, sharing a common goal. Military units have to resort to hierarchical command-structures in order to get people to do the right thing in a situation where disagreement is fostered by political pressure. In the Fuel Rats we prefer to expect people to do the right thing. If someone doesn’t fit in, they’ll get polite suggestions to find another hobby than Fuel Ratting.
Even though we are leaderless, we are a collective; the actions of each individual reflect on how others perceive the collective. Every one of us makes all the Fuel Rats collective look good. Which also means that if one of us is misbehaving, they make all of us look bad. If one Fuel Rat feels another is making the collective look bad, your starting move should be: “Hey, please think how your behavior reflects on the collective.”
We are The Good Guys and first and foremost our job – our only job – is to save stranded pilots quickly, courteously, and professionally. Some of us are fairly serious role-players. By all means, role-play if you like. Or not. If one of your fellow Rats is role-playing, it’s probably nice if you play along.
Since the game hasn’t got a very good fee-structure or means of exchanging wealth, we talk a lot about charging a 100t of platinum, an arm, or a liver. If you want to work something out or role-play something with a rescuee, have fun.
Please do not mix other game-play with your Fuel Ratting; while you’re out on a rescue, you represent the lot of us. If you decide to get creative, just be thoughtful.
The Fuel Rats are not a war guild. Yes, we’ll equip good shields, fast ships, even guns to protect ourselves and our clients from NPCs, but you'll never see a Rat-pack go to war against other CMDRs. After all, many of the Rats are on different sides and factions. When we’re being Fuel Rats, we’re all on one side: The Fuel Rats. Otherwise… it gets complicated.
|The Doctrine of Individual Excellence: If we do our best, individually, then collectively we’ll be awesome.|
In truth, any ship can be made to serve as a Ratting ship, although the nature of our service often leads to certain types of ships being preferred. The most frequent ship to be found in the hands of Rats are the Asp Explorer (The RAsp) and the Anaconda (Rataconda), due to their superior jump range and flexible modules.
There are a few things that come as a bare minimum to enable your ship to refuel another though:
- Jump Range: Because Rats are assigned based on how quickly they can reach a client, maximizing jump range is a good idea. We highly recommend a minimum 20Ly jump range before going on rescues or requesting a drill.
- Cargo Hold: Limpets need space to be stored in, so you need a cargo hold with enough storage space (1t per limpet). It's recommended that a minimum of 8 limpets are carried. Most Rats carry 12-16 limpets. Remember that too many limpets will lower your jump range.
- Fuel Scoop: Our clients often end up in inhabited space, and every limpet you give to the client takes 1T of fuel out of your tank. Without a fuel scoop … you will soon find yourself in serious trouble.
- Limpets: All nice and well, yet without limpets, all your shiny ship would be very, very useless. Don’t forget to resupply your stock through [ADVANCED MAINTENANCE → RESTOCK] at a station’s menu. You should carry at least 8 limpets, better are even more, but not too many. T9 vessels, for example, can be very fuel hungry – ten limpets might just be enough to get such a client to the next station.
- Fuel Transfer Limpet Controller: This is what programs, launches and guides the limpets on their way to the client.
- Extra fuel tanks are optional and depend mainly on the class of your Ratship. Note that increased fuel capacity reduces plottable jump range.
- Weapons are not required. You are free to take them with you, of course, yet they reduce your jump range, and Rats usually like to run rather than stand and fight, and thus invest in stronger defensive mechanisms or speed anyway. We usually do not run into trouble from other CMDRs through rescues, yet it happens (very, very seldom). It's more likely that you'll run into an NPC attempting to take cargo or claim a bounty.
Note that you do not need a dedicated Rat ship to do your ratting in. Many rats prefer to customize their ship for ratting by using light, class D modules and foregoing weaponry for added jump range and speed, but as long as your ship has a fuel transfer limpet controller and a few limpets, any ship in your shipyard can be used for ratting. People often rat 'on the side' while out doing other things, like mining, exploring or combat. Especially on long range exploration trips, many a client has been saved by a rat that just happened to be in the neighborhood, rather than thousands of light years away.
IRC and Communications
IRC is our communications backbone, and where all our rescue activity takes place. Although we have a presence on both Reddit, the Elite: Dangerous forums, Discord and various other media, 99.9% of our rescues happen on IRC, with the other media mostly serving to help get our clients to IRC.
Our IRC network is irc.fuelrats.com, which is served by two servers; one in the EU and one in the US (irc.eu.fuelrats.com and irc.us.fuelrats.com). Clients are primarily connected to the US server, falling back to the EU server if the US server should, for some reason, be down. Clients connect using a customized KiwiIRC web client, which presents them with a form requesting important information, such as their commander name, their platform (PC, Xbox or PS4), their location, and their O2 status. Once they fill out the form, they are connected to our IRC server, and sent to the rescue channel, #fuelrats.
|The #fuelrats channel is meant for rescue traffic only, and chatting should only happen in #RatChat.|
Once the client is connected, our trusty IRC Bot, MechaSqueak, is notified of the new case and triggers a Ratsignal, a word that most Rats have set up as a highlight to warn them of new cases. From there, a rat currently holding the role of Dispatcher handles the case workflow.
Primarily, the client communicates with the Dispatcher, and the rats communicate with Dispatch in the IRC channel. Once assigned on a case and winged up with the client, the rats can freely communicate directly with the client through in-game text or voice chat.
Although we keep the #FuelRats chat channel very brief and almost mechanical-sounding, the in-game voice and text chat is an opportunity to give the client a good experience. Some CMDRs like to roleplay; feel free to play along with them. Others appreciate a more informal, out of character tone. Adaptability is your greatest resource here. Our first priority is of course to give them fuel, but our second priority is turning a crisis situation into an enjoyable game experience.
While on a case, your primary task is getting to the client as quickly as possible, which usually means you will spend most of your time enroute on the "jump-honk-scoop-jump" cycle. During this time, you will also receive friend and wing invites from the client, which you need to report receipt of back to Dispatch. Most rats do this while in witchspace between systems.
|Been spending most of your time in Solo until now? Check out the Wing Mechanics Tutorial|
Identifying the client
It’s a good idea to include the client name or case number (NOT system name) in all of your messages, particularly when multiple cases are ongoing. Some dispatchers have preferences on whether they want report by client name or case number; they will most likely inform you about which.
Once you know a client’s (hopefully correct) system, if you are available to perform the rescue report the number of jumps to dispatch, along with any pertinent info. “5j”, “9j + scooping”, “ship change + 4j” are all concise ways of doing this.
While many of us choose to use multipurpose ships for Ratting in, it's important to notify Dispatch if you have any cargo (other than limpets) or active missions as these greatly increase the chance that NPC pirates will attempt to interdict you and possibly attack the client. If you are interdicted by an NPC it's imperative that the interdiction end (in game terms). This can be accomplished by successfully winning the interdiction mini-game, destroying the NPC, or creating a new instance by logging out of the game by using the menu only (killing the process, i.e. combat logging is against the ToS and is prohibited) or jumping out/back into the system (i.e. the Dystopia Protocol).
If you report jumps, it is implied that you are willing to perform the rescue and it’s good to assume you will be assigned (e.g. start jumping immediately) until you hear otherwise. Don’t call jumps if you don’t want the rescue.
It’s important to wait until someone has communicated with the client to !prep them before calling jumps. This way the IRC channel doesn’t get clogged with communication that can potentially confuse the client who is unfamiliar with IRC or our procedures. It’s critical to quickly get information on Code Red clients so that they can log out and rats can be organized for the rescue.
If no dispatch is present, any Rat can (and should) !prep the client in order to conserve their fuel. As stated above, this should be done before calling jumps. If you don't want to dispatch, !prep the client and call "Hatsignal" in #ratchat, which will notify other Rats that a dispatch is needed (also see Who you gonna call? for additional signals).
To !prep a client, the Mecha command fact is simply:
It’s also a good idea to add the client’s IRC nickname or case humber after your call, such as “5j clientname” or "5j case #2" so that dispatch knows which client you’re calling jumps for. This is important when multiple cases are being run in the channel at the same time and multiple people are talking at the same time.
CMDRs currently in a Multi-crew session can NOT wing with other CMDRs. If a CMDR tries to wing a CMDR that is in multi-crew there is no warning message. Make sure that you're not in a Multi-crew session when ratting.
Your status updates
- If you’re interdicted or other mishaps happen, let dispatch know.
- Also update dispatch periodically on your remaining jumps, usually this can be bundled into another update to keep traffic down (“3j, FR+”)
Client status updates
- Let dispatch know when you’ve accepted a wing request (WR) or friend request (FR) from the client. “WR+” or “FR+ client” are examples of this.
- If you haven’t received a request and a reasonable amount of time has passed, notify dispatch of that as well (e.g. “FR- client”). This can also serve as a subtle way to remind dispatch to instruct the client to send friend/wing requests if they forgot to do so.
Anchor RevFR RevFR Warning title Do not reverse-FR or message clients who immediately leave IRC
We do not send reverse FRs or send XBL/PSN messages to clients who send a ratsignal and then immediately disconnect and do not return. The client may have changed their mind, or in extremis, it may even be someone using someone else's CMDR name. If they require help, they will reconnect.
Beyond that, if the client has communicated previously and hasn't clearly indicated they no longer need assistance, Dispatch may instruct rats to attempt reverse FRs if it's probable the client still wants help.
- Since Code Red clients are logged out, you won’t receive a Wing Request until after they log in. This is normal and there’s no need to report WR- while you’re still en route.
- If the client says they have friended/winged you but you haven’t received the request, notify right away in case they friended or invited the wrong person.
|Xbox friends are a 2-way process of "following" the other person. To have an fr+ status, both the rat and client need to friend each other. Yes, that's technically a reverse friend request, but it's required on Xbox. The rat should only report fr+ after both the rat and client have friended each other. The rat can confirm this by seeing the client's name on the comms panel or by checking the clients profile (you'll see "#+you" under Friends and/or your name under the Friends & Followers tab)|
- Once a client has friended you, it’s possible to check galmap to confirm they’re in the system they reported. Alert dispatch with the correct location as soon as possible.
- Since Code Red clients are logged out, this can’t be done until you’re already in (hopefully the correct) system
- Let dispatch know if you can/cannot see the client’s Wing Beacon (BC) once in their target system and wing
- Always drop to clients with nav-lock engaged on first try.
|Confused by the above terms? Consult The Fuel Rats Lexicon|
When you drop out of Supercruise at the client’s location, there’s two options to take based on whether you see the client or not. (Sometimes you won’t, because instancing issues):
If you see the client:
- Target the client and begin your fuel transfer FIRST (especially on a Code Red). Targeting the client from the Navigation panel can save precious seconds while turning your ship around. If you’re running a high rated limpet controller you may not even have to turn around before launching your limpet as you can target the client through the navigation panel’s contact list.
- Update dispatch on your status. Only report successful fueling after you hear “Fuel Transfer Complete”
Fueling, refueling, fuel+ or any other similar word that means the limpet was successful are acceptable terms.
It’s important to do these steps in this order, because a client may have only seconds of Emergency Oxygen left. Dispatch can wait.
If you don’t:
- Tell dispatch ASAP. “Inst-” or “Instance-” is fine.
- Have a look at the distance to the signal. Lightseconds (ls) point towards client in exclusion zone (EZ), kilometers (km) towards regular instancing-issues. Let dispatch know, too.
Bearing and Distance
On a CR-rescue or when client is very far away from star, it can be necessary that the rats get a bearing and distance to the wing-signal before client logs out to main-menu.
- Bring wing-signal of client to the center of your HUD. You can check if it's dead-center by rotating your ship along it's stern-bow-axis. Don't move the controls until you are in position of client.
- Check the distance to client and to the star so you can get into position of client by calculating the correct distance from star after the wing-signal has gone.
Code Red Rescues
Code Red (CR) rescues are those when a client is on emergency oxygen, or a few other special cases at the discretion of the dispatcher.
In the case of a CR, we have the client logout to the main menu after telling us their location. This prevents the client from running down their oxygen timer. On CR cases multiple rats are always assigned if available. The client then stays in the main menu until all rats assigned to his case have arrived in the system he was reported to be in. Once the rats are in the system the client will login, and invite the rats to a wing. If the client is far away, notify dispatch immediately and they will have the client logout again if enough time is available. If instancing issues arise during a CR then Dispatch will advise the rats and client which maneuver to try next.
It’s important to keep in mind that on CR cases every login/logout by the client reduces the remaining O2 timer. Each time a client logs out while on life support, they have a 15 second timer (similar to trying to log out while your ship is in danger/combat), and it takes time to send wing invites and turn the wing beacon on. Managing the remaining O2 timer versus the time needed to travel to the client and initiate the rescue is key to a successful CR case.
To see both an annotated example of a rescue and some real rescue chatter from #FuelRats, click here.
Top Speed: 250 (340)
Top Speed:180 (240)
Speed: 200 (300)
Top Speed: 290 (415)Fuel Capacity: 16t
Cargo Capacity: 20t
Maximum range: 27.20LY
Unladen range: 25.63LY
Fully laden range: 23.55LY
Top Speed: 230 (366)
Top Speed: 258 (338)
When you actually reach a client, you begin a fuel transfer by making sure you’re in the correct firing group, targeting the client, and firing your fuel transfer limpet controller. Each limpet will consume 1t of your fuel and, after a short delay, will transfer it to the client. Note that the client does not actually have fuel until you receive the “Fuel Transfer Complete” message, which occurs after the “Transferring Fuel” message. It’s good practice to have the Fuel Transfer Limpets assigned to a fire group without weapons and to lower your landing gear so that you don’t accidentally boost and hit the client.
Xbox and PS4 Note: Lowering landing gear is a careful undertaking on the Xbox where the default boost button (B) is also used to lower the landing gear (B+down on the D-pad). Make sure that buttons are set to contextual mapping in the options menu. It’s a good idea to hold the B button down until after the D-pad is pressed to prevent unwanted boosting. It’s also a good idea to make sure that you’re not pointed directly at the client.
Do not report Fuel+ to Dispatch before you have a "Fuel Transfer Complete" message from the ship's computer. Until the fuel has reached the player's tank, they may still blow up if they are on Emergency O2. If you wish to report a successful instance with client, use Inst+. (But if it is a code red, your focus should be on getting limpets on target rather than reporting)
No two rescues are the same. Even though many of our rescues run through our standard operating procedures like Snickers hot off the factory line, we are quite frequently faced with situations that fall outside of what our SOP covers. Long Range Rescues, escort missions due to broken fuel scoops, nudging SRVs that have gone orbital back to the surface - The Fuel Rats are sometimes called upon to do some very weird rescues. And for the most part, we try to help those too, even if it falls outside our standard job description. Some of them are covered in our Special Rescue Scenarios page.
Non-CR Tactical Face Plants
Tactical Face Plants (The act of intentionally slamming into an Exclusion Zone to reach a client) are required for Code Red rescues where the client has lost the ability to power their ship while too close to a star or planet. We provide the optional TFP training specifically for these incidents. TFP training is not standard drill material because in 98% of cases, people who drop out inside Exclusion Zones still have fuel enough to perform a Supercruise Hop and get themselves out of the situation. Thus, TFPs are not SOP for non-CR rescues.
The reasons for this can be summarized simply; it's less risky. For both the client, the rat, and for the outcome of the case. Faceplanting, be it tactical or not, is a risk to the player's ship, both client and rats. It is also a gamble, since you might very well end up well out of reach of the client, even with a carefully planned TFP. When the client can get out of the Exclusion Zone, we get them out of the Exclusion Zone first. Then we fuel them.
The bottom line: Tactical Face Plants are for Code Red rescues. It should not be attempted simply as an 'expedient' way of getting to the client. Non-CR TFPs are at the discretion of the dispatcher, when the actual situation requires it. (Client unable to understand instructions to SCHop, or otherwise unable to do so, for instance.)
Common Client Mistakes
Elite: Dangerous has a steep learning curve, and many newbie players find themselves in need of calling upon our services. Some make common mistakes that we have included procedures to help avoid. Find out more about them on our Common Client Mistakes page.
Issues and How to Solve Them
No matter how good our SOP has become over time, we are still at the mercy of Murphy's Law, and sometimes things do not go quite according to plan. Some of these things, we have learned to work around - in most cases. Take a look at Issues and How to Solve Them. For the Xbox platform, we have some additional information in Xbox Troubleshooting. For PS4 we have additional information in PS4 Troubleshooting.
Once the client has received fuel, we share some information with them to help prevent them ever needing our services again - although some people apparently love us a lot, as they keep coming back. This Debriefing Guide serves as a good reference for the knowledge we want to impart to our clients.
Although we do not charge for our services, if the player asks whether we take payment, you can inform them that the service is free, but if they wish to donate, they can do so from our webpage. The direct link is http://t.fuelr.at/donate
With the client debriefed and safely on their way home, Dispatch should have cleared the case, and if you had the honor of getting the first limpet of fuel to the client, you will have a private message from MechaSqueak, containing a link to our paperwork form. This is where you file any notes about the rescue, and whether it was a success or a failure. There isn't a need to notify dispatch that paperwork is completed any more, just call jumps for the next case!