Sparkle

ACCEPTED. Apologies to the delays in processing this application. Please speak to myself (Sparkle) or Jack to receive your training and whitelist.

DENIED. Failed to complete roll call.

ROLL CALL HAS CONCLUDED. No posts after this will be considered. Audits will be begin immediately!

Obviously the contradiction above has to be fixed if accepted. My input from a Utility perspective. The 5 minutes is meant to used to do RP preparation for the next roll. If no other breaches or events are happening, their current position would be the focus. As already mentioned, the rule is hardly enforced cause it doesn't make sense to be enforced. Movement to other calls should be happening if such calls are available. Also, if rolls fail enough (as rigged as they are lmao), there shouldn't be a reason personnel stays longer putting themselves in danger. The rule clarification on puppy guarding is still +Support Just not convinced on the Maintenance part especially if they are alone on fixes.

Utility Roll Call (Summer 2021) July 10th - July 17th Rules: All Utility personnel, Maintenance and Medical, are required to post. Only those trained and in the branch before July 10th are required to post. Those on LOA from start to finish (entire duration) of roll call are exempt Those going on LOA during this roll call MUST respond to avoid removal You must reply by July 17th, 11:59:59pm EST. Failure to post will lead to removal. Be truthful in your response. All items will be audited. Lying will result in removal. Please include ALL information possible. Any items left unwritten will be removed in the audit. If you have issues making a post, you MUST contact command to assist you. It is YOUR responsibility to ensure you complete this roll call. Failure will result in removal. Both rosters will contain a section (RC) indicating if a post has been made. It is YOUR responsibility to check this section to avoid removal. Whitelists and Discord tags will be audited and removed upon closing. We thank you for participating in giving Utility an accurate head count. Format: ``` RP Name: SteamID (i.e. STEAM_0:1:55975235): Discord Tag (i.e. Name#0000): Branch(es) (Maintenance, Medical, Both): Rank(s) (Include both branches, if applicable): Subdivisions/Whitelists (FTO, CS, MMF, HLPR, ACM): ``` Example: ``` RP Name: Sparkle SteamID: STEAM_0:1:59197292 Discord Tag: RDSparkle#7954 Branch(es): Both Rank(s): DoL Subdivisions/Whitelists: FTO, CS, MMF, HLPR, ACM ```

+Support I'm good with this.

You fiend. Give him back. We'll miss you Gordan, come back to Utility one day.

-Support Most the staff did was mute which is entirely in his right. You basically got away with a verbal. You don't have any evidence on your side to support your story. You being argumentative here does not help your case.

When you said something yesterday, I thought you had posted a bug report and I was looking for it. +Support I guess

Let the records show that this will forever be in his post history. I have sworn testimony he has watched the show. I rest my case your honor.

Gotta make sure you get negative profit with a downvote

+Support A ban is a bit much especially for a bind with zero reference to another community.

+Support Former ET boyo. Still as creative as ever.

Have a good time sir. Hope you enjoy the time you have with him.

+Support Never thought of using this area. Very good idea.

-Support I'm gonna be completely honest sir. While I'm glad you are getting a second chance at RP in MTF, I seriously feel it is way too soon for return to staffing. The report made against you contained severe offenses only within your first day. This isn't something you can just wipe away with a blanket "second chance". You got to earn it back through showing you are capable of following the rules and respecting other players. Trust is something you have to build back before you return to staffing cause your actions caused a dent that is not easily fixed.

Console is just flexing at this point +Support

+Support I saw this and was like "That's heckin wild". But clearly context wins.

I don't like the application of self-defense in this situation. Very much the fact you went towards the danger after your threat went away which kinda crumbles the principle of self-defense. But the MOTD is technically satisfied so... +Support but I still don't like it.

Has this been an issue recently? I haven't heard much for a good bit.

Can't even trust you with LOA titles smh.

-Support However, I want to bring attention back to this point for a moment. He is correct about this point. Class Specific Rules -> All Players -> Rule 12 states: "Personnel calling a RP Arrest on Sight / Kill on Sight (AOS/KOS) are required to provide and advert a legitimate reason with the AOS/KOS order. This is especially required for actions taken against Dr. Maynard and Sleuths." While I agree that the foundation should be doing more to protect the interrogation (as noted in the previously mentioned video), they technically cannot do much when the invasion from Maynard begins. As soon as Maynard breaks through, you have all of maybe 5 seconds if they rush it to get an entire advert plus reasoning to justify an AOS/KOS. Makes it way too easy for Maynard to get the kill within that time. Also, nobody wants to be the spark of a potential conflict hence the hesitations. Provided MTF has people to cover the entrances and the above can be excluded for such purposes, then we have the problem covered nicely.