The drill is a replicated rescue designed to teach the rat the skills they need to successfully operate on real rescues. In addition to the prospective rat, the drill requires a “drillspatch” (i.e. dispatcher for the drill), “damsel” (i.e. client) and an overseer to evaluate and provide advice. The drillspatch, damsel and overseer are all experienced rats that will share their knowledge and offer advice to the prospective rat.
Before requesting a drill, the prospective rat should read and understand the information on this page, have spent time in IRC watching real rescues in #fuelrats and asking questions of other rats in #ratchat.
The prospective rat should also have a ship with a minimum jump range of 20Ly equipped with a fuel scoop, fuel limpet transfer controller and at least 8 fuel limpets.
Once a prospective rat is ready to schedule a drill they should change their IRC nick to include [NeedsDrill] or [XBNeedsDrill] and ask in #ratchat for an overseer, drillspatch and a damsel. Only the damsel needs to be on the same platform (PC or Xbox) as the rat. Check http://www.fuelrats.com/roster for a list of overseers.
| Tip | ||
|---|---|---|
| ||
In order to help reduce the Xbox drill time, make sure that your NAT Type is Open (Xbox settings > Network > Network settings). ( on reddit has an excellent guide on achieving an open NAT) Your privacy settings should also be set to Adult Default (Xbox settings > Account > Online Privacy and Safety), and your profile should be set to Online (the top right button on your profile should read “Appear Offline” as the button is backwards). If you need to change these settings, make the changes and then hard reset your Xbox by powering down the machine, and pulling the power cable for 5-10 seconds. |
In order to successfully complete the drill, the rat should understand the following:
- Standard Operatings Procedures (SOP) for rescues, including Case Red rescues
- Communicating using IRC while flying
- Using the Galmap to plot a course to a named system
- Understand the naming conventions for procedurally generated systems
LL-L L#-#orLL-L L#, where L is a single letter and # is a single, double or triple-digit number. For exampleCOL 285 Sector HB-G A40-3is a valid system name, butCOL 285 Sector H8-6 A40-3is not.
- Verifying client’s reported system
- Understand the naming conventions for procedurally generated systems
- Communicating with dispatch
- Calling jumps
- Status and updates on Friend (fr+/-), Wing (wg+/-), System (sys +/-), Beacon (bc +/-), Instance (inst -)
- Refueling status
- Problems and troubleshooting
- Instancing
- Route plotting and travelling
- Filtering the Galmap for scoopable stars
- Fast route plotting
- Fuel scooping
- Receiving friend invites
- Wing operations
- Receiving/Sending Wing invites
- Wing beacons (turning on, targeting)
- Checking distance to wing signals (dropping to normal space)
- Wingman Navlock
- Fire groups and fuel limpet controllers
- Debriefing the client about how not run out of fuel again: Debriefing guide
A successful drill includes:
- Prompt communication and updates to dispatch
- Demonstrated understanding of rescue procedures
| Warning | ||
|---|---|---|
| ||
| Please state the phrase “CLIENT HAS GONE CODE BLUE” to the Overseer after you have read this page. |