Commander Report: Patton 'Hardtack' Moore

[FGRSentinel]

Your Byond Key: FGRSentinel

Your Character Name: Goddard 'Patton' Pearsall

Accused Byond Key(if known): Taketheshot56

Character Name: Patton 'Hardtack' Moore

Approximate time and date of the incident (Central US Time for fastest results): 10:40 PM 8/5-12:10 8/6

What rule(s) were broken:
Rule 3: no Griefing

Description of the incident:
I was an SO during this round. From the beginning of the round, Hardtack was providing the bare minimum that seemed to be required to lead the Marines. Randomly at one point about 40-50 minutes in, in a round where we were having a hard time keeping everything together, he decides to call the CE up to the CIC, locks literally everything down (we got reports of the hangar being locked down), and starts accusing the CE of "stealing the nuclear launch codes." I leave it alone for a while and eventually things start falling apart. We keep trying to get ahold of Hardtack and the CE begins asking if he's still marked for arrest. Turns out that the CO ordered the CE's arrest and was hunting him down. During this time, nobody could get him to respond to anything we said and he acted like the OP wasn't going on except to continue to pursue him. Suddenly while I'm trying desperately to find an aSL for Delta, the power in the CIC goes out. We start getting angry at this point and the CO just so happens to get the SMES units powered back up in about... I think 30 seconds?

Either way, he continues to demand the MPs hunt down the CE, calling him a traitor and other things while the op slowly falls apart. The XO is unwilling to make calls where needed at times and the CO is unwilling to do their job whatsoever. As the round goes on, things start getting worse. A squad calls in for OB but the cannons aren't chambered. Nobody can load them because the CO's chasing the CE around the ship like a lunatic and the MTs are either SSD or dead. T-comms is under siege. Another call for an OB goes up. CO half loads the cannon and goes off to continue hunting the CE, who at this point has been prevented from doing his job for more than half the round. T-comms is breached and we start begging the XO or CO to order evac. CO finally issues the order, but Alamo launched just before he does so, dooming everyone on the surface because they didn't know to hold.

Out of everything that happened that round, only three members of Charlie and four out of Delta survived due to the XO's hesitance and Hardtack's (more or less) outright sabotage of the Marines' main heavy support weapon.

The best part? After he died Hardtack eventually admitted it was an "event" he did. The CE never stole anything from him. The CE never did any of what Hardtack was chasing him for... Which means that either an MT didn't set up the power or Hardtack quite possibly killed it for his "event," which seriously hurts the marines once they no longer have the ability to rely on CIC's support (this last part isn't something I'm certain of, however). Not only that, but he basically denied the Marines use of the OB for half the round just because he felt like it. Considering the fact the CE didn't sound too thrilled in dchat, I don't think he was in on the "event" either...

Evidence (screenshots, logs, etc): none, but I'm sure others who were there and the logs can add to this.

How you would punish the accused:
Honestly at this point Hardtack's antics are getting to be too much. I'd be fine with it if he got a lecture to tone the madness down, but at this point I'm not sure. Something more serious might have to be done if he continues this

[Minimike]

I was the CE in this.

I had in fact stolen all the contents from the CO's safe.

I was indeed aware of what's going on, as I'm the one who caused it.

I baited the CO into chasing me down, so if anything this is indeed my fault.

[Lumdor]

During this round only a few ahelps came in about this, and most were handled I believe.

From what I heard from people and the few ahelps I saw before they were taken, and this was not an event lead by any staff. Other staff online confirmed this.

Although from what I heard it was more something the player's involved put together into their own little thing.

The whole CE thing was left IC from what I saw and heard.

From what Patton told me he left the XO in charge, which left some SO's angry as the XO I'm guessing was not doing so hot, which is understandable.

Also, I questioned the CE after the round and they did indeed steal the codes but lied about it during the round.

Later on I saw a ahelp from the CE requesting from admins to get the Russian language, and Spooky gave him skrell.

Really I see no rule break here, but mostly just a big cluster-fuck that made some people un-happy.

[FGRSentinel]

Ah, perhaps I just misunderstood what was said in dchat. Sorry.

[taketheshot56]

First of all event was more of a poor choice of words on my part, no there was no staff influence aside from the language the Ce was given, which was quite cool. It was more of a player started scenario done by the CE.

The CE did indeed rob my safe, and run off to avoid justice. We did indeed have issues with power which mike didn't cause, the SMES simply reset and had to be fixed alongside the engines. CIC was staffed by the XO and SOs. Time and time before have COs left the XO in charge of the OP. I voiced this numerous times to the XO. "I have to go deal with our stolen launch codes, you have full control of the ground op." The role of the CO is to command and delegate and in a perfect world the XO should be leading and executing the COs bigger picture.

I called the CMP to my office upon him waking up and the CMP Sherman and I decided we needed a plan of action to get back the Almayers launch codes and that alot was at stake. Using the biomonitor both in medical and the CIC I used the computer to track Victor to a small storage room. Now at this point we have no MTs aboard, no synthetics, and all the squad engineers are engaged with the CE behind a bolted door. After some rummaging around myself the CMP and an MP find a block of plastic explosives, and the CMP unable to use explosives handed it to me where in I used it on the door and stepped back to allow the MPs and CMP to move in to deal with him.

Now i did not at any time Deny the use of OBs. I ensured the XO knew he was in charge while i worked to sort out the situation ship side. The XO was also fully capable of loading the OB cannon having the same level of engineering as myself.
Now in the end this round didnt turn out great. Despite my involvement on the shipside situation I kept a tab groundside and ordered marines to fall back to FOB to which fighting continued around bar for about 20 minutes more before we finally fell back to the LZ. After finding out the XO had jumped ship without my permission to head planetside I returned to the CIC to fix the OB cannon. I loaded and chambered it, unfortunately with the cool down I hit chamber but it did not properly chamber. At this point it was time to evac and I ordered it as such and the PO took off just after I made the announcement. I then went down to go fix power in engineering and was in the process of repairing reactors when the dropship came, at which point I headed back up to the CIC, directing the CMP to bring the now captured CE to CIC, where upon which the beacon was launched and I gave the order to abandon ship.

As CO i shouldnt be 100% breathing down the neck of the XO when Ive directed him to lead operations, and quite frankly, it is important to let the XOs run the show, otherwise we never really get a chance to see how they command.
Information is lost in transit and things arent properly communicated RPly. You are a good SO so i no doubt believe you will try for CO whitelist eventually and you will realize that sometimes despite how well you delegate tasks to deal with other stuff. Things wont go as planned.

[FGRSentinel]

Yeah, sorry about that, Hardtack. It was a bad round on all sides. The XO really didn't seem to want to make decisions, which just kind of made it easier to assume they were told to let you decide first or something. Considering that, I really don't see a point to press this.

[Mizari]

Ok so after reading this I assume this has been resolved. Will be getting this locked.

[Emeraldblood]

Resolved - No action will be taken; events considered IC