Page History

The !md feature in Mecha allows rats to list a case for deletion, which is done after review by an overseer or above. This means that the case as a whole is completely removed from our rescues database, and neither counts as a success or a failure on the leaderboard. This feature, although handy, needs to be applied in the right way.Closing cases is important so that we have accurate records of our successes, failures and other cases.   

Invalid cases that can be deleted

You can mark these types of cases for deletion:

Cases that should always be filed as Valid Cases

• If Rats are dispatched, Fuel or Non-Fuel Rescues (e.g. Jumponium, Emergency-repairs or Unstuck) should always be filed as valid cases.
  • If a client is fueled or otherwise provided with jumponium, repairs or other help (i.e. Rescued) by Rat(s) file the case as a "Success".
  • When a rescue does not occur because the client was able to rescue themselves (i.e. make it to a station, star, etc.), changed their mind, or became unresponsive, after Rats are dispatched, the case should be filed as "Other".  
  • If the client is destroyed due to a lack of fuel, after Rats are dispatched, the case should be filed as a "Failure".
  • If the client is destroyed due to NPCs or player attacks, after Rats are dispatched and before a limpet or rescue is completed, the case should be filed as "Other".
  • If the client is destroyed due to NPCs or players, after Rats are dispatched but after  a limpet or rescue is completed, the case should be filed as "Success".

Cases that can be marked for deletion

Generally, cases where Rat(s) have not been dispatched can be marked for deletion using the command !md <case# or clientname> <reason> (see below for other related commands).

• PEBKAC - When a rat or other visitor mistakenly raises a ratsignal, or improperly uses the !inject or !grab commands.
• Duplicates - More
• Fake cases,when we know it is fake before sending anyone on a rescue. I.e, someone mistakenly triggering a ratsignal, or using !inject improperly.
• Duplicates - more than one case from the same client, usually caused by reconnecting using the IRC client in rescue mode, after the rescue has been cleared.
• Clients who change their mind - before we dispatch (such as make it to a station or scoopable star, reboot/repair or otherwise save themselves even with help from us) - without dispatching rats to their case. If rats have been dispatched, it is a valid case , and we record it as a success.(see above). 
• Clients who immediately leave chat - Clients that start a rescue, but do not respond to our communications, or immediately leave IRC.
• Clients who have pushed the wrong button - i.e, their intent was just to chat with us, but they did not understand the green button, or want to see how the system works.

Cases that should NOT be deleted

...

Cases where Rat(s) have been dispatched should be filed and assigned a rescue outcome:

• Cases where the client changes their mind after rats have been dispatched on their case. Record the rescue as a success.

  Jira
  showSummary false server JIRA serverId cef5650c-d37f-3920-ad06-513e8ea1558f key OPS-30

  their mind either because they choose to self-destruct, or find a way to carry on their journey (Either through tips from the Rats or on their own). Clear case and file as "Other"

• Fake Calls - Calls which are intentionally created for purposes other than a legitimate need for fuel. ALWAYS clear case and file as "Invalid", and then report the event to a Janitor.  These cases get filed regardless if Rats were dispatched or not.

  • Cat calls - Fake

  Cat calls - fake

  • cases in an attempt to lure us out for target practice

  , or who intentionally signal and fake a rescue 'just to see how we do things'. ALWAYS write paperwork on these, and file as successful.

Info
For any rats that feel that a successful rescue shouldn't be reflected on the leaderboard as a success they can attribute the first limpet to "N/A"

 

• • . 

  • Troll calls - Cases where a user intentionally creates a case for purposes other than requiring fuel. Typically these reasons include: personal amusement, attention, attempting to troll the dispatcher, or to generally disrupt the rescue channel.

When to close inactive cases

Inactive cases should be closed and filed after they have exceeded the times below. In the event that the client returns after their case has been closed, a new case should be created.

• 15 minutes after a client leaves chat immediately.
• 1 hour after the client leaves chat mid-rescue.
• 24 hours after a LRR client fails to make a meeting time, and cannot be contacted.

Associated Commands

...