Opfor standards

First off: You must be Game Assistant or above to handle OpFors.

• You may handle one if there are no other GA+ staff online, but as you are accepting responsibility for the OPFOR, make sure to read through their OPFOR, while you are not responsible for their conduct, you are responsible for what you approve.
• You are not required to approve any OpFor that you don't wish to for any reason, but please inform the player when you have made a determination.

Second: Any OpFor that requires a special announcement, special permissions, or a lot of dangerous equipment will require heavy oversight and should be approved by Admin+ or Event Manager staff ahead of time, and be properly logged as an event.

Step 1: Read the OpFor - Read the objectives, severity, and reasoning, and determine whether or not it meets the following criteria:

• Objectives are focused and specific, related to very clear areas or individuals or objects.
• Requested Equipment is appropriate for accomplishing the goals in the manner described. No major explosives for a theft mission, for instance.
• Reasoning is given for the 'backstory' part of the OpFor
• It is clear what the condition for stopping will be: If you have to ask "what would make you stop?" then it isn't a well-written OpFor.

Step 2: Open a Dialogue with the player -

• Whether accepting or denying, try to address the posting of the opfor and talk with the player before the 15 minutes grace period has passed.
• If you plan on denying, or just need them to wait, don't just leave the player in the dark, explain why.

Step 3: Consult with other staff and the Traitor Panel, ghost key and critical roles and think, will this unnecessarily divert the round that some people are pushing forward or detract from rp?

• This is going to require some amount of judgment call, but should be based on concrete things.
• If there have been fewer than 3 tickets related to chaos, and fewer than 3 events that have impacted engineering or security in a major way, then most OpFors will be fine.

Step 4: Work with the player to improve the quality of the opfor if necessary.

• If the opfor requires some objectives to be pared back, such as a "murder the captain" objective when the captain has been involved in numerous attacks already, or "Destroy the Armory" when there have been 2 molds, then tell the player that they need to either pick a new objective, abandon the problematic one, or just change it to fit better into the round.

"Better" in this case has the following qualities:

• Unlikely to round remove numerous players
• Unlikely to be made worse by simplemobs or basic events like a Rod or Anomaly
• Likely to be seen or heard by numerous players
• Has a clear stopping point: "I'll give up if I'm captured, disarmed, etc." No killing sprees, no "escape at all costs" etc.
• Has clear limitations established on targets.

Step 5: Approve or Deny objectives and the OpFor itself.

• This accepts responsibility for the player's OpFor by the approving admin.
• Make sure the player is aware of limits that you want them to follow, knows what is not okay, and understands the ultimate goal is to make an interesting situation.
• Especially with equipment but for objectives as well, make sure that the player has given very clear reasons for everything in the opfor.
• If someone asks for an explosive, for instance, but just has theft objectives, they need to explain why they need an explosive.
• If you don't recognize a piece of equipment, ask other staff if they know, or go to Central to look into it before approving.

Step 6: Ask the player to get someplace safe to have equipment issued, this can give them away, so they ought to be somewhere private and lockable if possible.

• Once safe, issue equipment.

Step 7: Keep an eye on the player from time to time to make sure they're sticking to their objectives. Communicate with staff about the OpFor at all times, but especially so if it's going to be above severity 3. Then just have fun watching the fireworks!