Skip to main content

Walrus SOP

This Standard Operating Procedure (SOP) is for a Hull Seals Specialized Role. In order to become a Walrus, one must first become a standard Hull Seal and pass all Hull Seal trainings. This document is a supporting addition to the Hull Seal SOP, and is not superior to that document.

This Page is a Draft! - SOP not complete. Info may change, and more will be added.

Hull Seals Walrus SOP Hull_Seals_Patch_V2.png

Revision 01

Walrus SOP:The Basics.

What is a Walrus?

Simply put, it's an ARMED seal, ready to put themselves between a needing commander and an attacking NPC pirate.

A potential Walrus has by this point in their career:
-Logged hundreds or even thousands of hours in the game
-Has extensive knowledge and experience in PvE combat
-Has the same knowledge and experience in combat ship builds
-Has completed all other Seal training, in addition to having a solid number of regular seal rescues to their name (TBD)

If this sounds like something you would like, and you meet the requirements listed above, read on..

Walrus SOP

Hull Seal Walrus SOP, Guidance and Procedures

Revision 3.01

 

What is this Document?

The Walrus SOP is designed for specialized sealing missions, where the normal repair is complicated by imminent or potential NPC combat.

 

Guidance for Seals

Walruses are a specialized group within the Seals. Their methods rely on quick reactions, detailed knowledge of NPC combat, and enough situational awareness to ensure the NPCs are not on the client.

 

When Should Walruses be Used?

Any time a NPC will spawn or otherwise be close enough to spot the client when they log in or when the Seal enters the client's instance.

----Some missions can spawn NPCs upon log ins, and logging out within certain rings can also do so.

 

 When Should Walruses not be Used?

If the client is damaged from combat, but still logged in, and the NPCs have not followed them,

Walruses will not respond to cases involving PVP combat under any circumstance

----If PVP occurs mid-case, the Seals are to disengage, and cease all operations

Walruses are to be deployed to defend the client, not other seals

 

Walrus Equipment and Builds

There are no set Equipment or Builds for being a Walrus, aside from the following additional requirements:

Have a Repair Controller (5D is the standard)

Limpets and a Cargo Rack

Have sufficient jump range to get to client in a timely manner

A fuel Scoop (Sufficient to refill the ship in a timely manner)

Be in a ship that is capable of excelling at a combat role

At least one weapon

Shields and Armor sufficient to weather incoming fire

 

Walrus Processes

The Walrus carries the standard Hull Repair Limpets to conduct repairs, along with a ship equipped with sufficient weapons to ensure the attention of the NPCs is on the Walrus, and defenses to endure weapons fire from that attention. The destruction of the NPCs is not the goal.

 

It is preferred that a Dispatcher utilize a Walrus and a normal Seal together (Two Walruses is acceptable as well). The Walrus is to focus on getting the danger away from the client first and foremost. The seal is to focus on getting the client repaired first and Foremost. If two Walruses are deployed, the first instances walrus takes on the Walrus role, the other takes on the Seal role.

 

In addition to normal sealing duties, the Seal is to also keep an eye out for straying NPCs. It is highly recommended that the two responders be in voice chat with each other.

 

The Seal should be the one informing Dispatch of what is occurring (Inst+, RL+, etc.), leaving the Walrus to focus on their duties. In the case of Confirming instance, and deploying the first repair limpet, these actions have priority over informing dispatch that they are occurring.

 

The Walrus is to, upon instancing with the client, immediately drop wing to reduce wing threat, then find, and tag all NPCs in combat until they have acquired their attention. Then pull the NPCs away from the client. Once all NPCs are away from the client, and the situation is otherwise secure, the Walrus may destroy, or run, from the NPCs as they wish.

 

  • The case is otherwise to be treated as a normal seal case.

 

Whoever fills out the paperwork should inquire for notes from the responder that is not filling out the paperwork, as well as adding any notes requested by Dispatch.

 

Dispatcher Decision tree, or "Should I send a Walrus?":

If the client is logged in:

If they are logged in, and they can still see the NPCs on the contacts list while running away and they are not losing them, the Dispatch is to get as detailed an idea of the clients locations as possible in the time they have before having the client log out to safety to then direct a Walrus to the clients location as the logged out section details. If they are logged in, and there are no longer any NPCs around to engage in combat, or they are successfully losing the NPCs by running away, the case is to proceed as a normal seal case, and the client is not to log out. This is a case where combat has ceased, an After Combat case.

 

If the client is logged out:

If the client is logged out, but it is expected that, due to a mission the client had, cargo they were carrying, or location they logged out at (Haz Res, etc.), a NPC will be waiting or expected to spawn in not long after they Log in, then this is a case where combat is about to ensure. These are Impending Combat cases, and a Walrus and Seal should be dispatched.

 

 

Note: Detailed case notes, quirks in NPC mentality and other useful but difficult to condense information will be assembled into a separate document when it has been condensed down enough for perusal.

 

Back to top