Part of Admin/Mentor Conduct Broken (if relevant): Creation of additional Antagonists, Event Protocols
Incident Description: On a very low populated station (8 effective player) in Echo station, spawned 4 blob nodes against false code 5 alarm despite the crews made an effort if the alarm is real or not (The only security officer got alerted and begin to search, while I have raised to code blue and got the emergency access to the maints to search). The said blob nodes were in critical location, nearing in the atmos, which ended up causing a plasma leak, forcing the peoples to leave. The blob nodes was spawned in at shift start 20 minutes point as well, on top of that.
Additional Information: While there is no active blob, mind, it was just some nodes. However, with the location of the said nodes were crucial, to the point of being hazardous as heck (Resulting plasma leak in most hazard-vulnerable station), it was gone way too overboard.
Your statement about them reaching atmospherics is untrue.
This was the blob nodes collective maximum range. You can see it just reaches the spare plasma tank near tcomms. This was unintended, but did not seriously impede the station considering it was right next to atmos with an AI on station. I say maximum because this is the maximum range that I set the nodes to reach to through varedits.
At no point did the blob objects ever actually transverse the z-level to the floor below, so atmos was never touched. The maximum range limit made it so tcomms machines werent damaged, and the rwalls from brig prevented any severe damage making brig unusable.
Event Protocols
You are correct, this was the purpose. I announced that I was going to be running a testmerge yesterday at around noon or later, and it was my intention to scare people into calling the shuttle so I could deploy the changes. According to our round ending policy, admins may encourage rounds to end “to accommodate potentially unstable/important test merges (At a maintainer’s discretion).” I announced the previous day that I would be running a testmerge and needed to end the round to deploy changes.
As for event protocols, the antagonist;
Could be fought off and was fought off without severe player injury and within short order of the round
Did not alter normal round flow other than encouraging evacuation, it caused no actual damage that could’ve just been ignored once the blob was defeated
Were contained by me to stop it damaging critical station infrastructure
I could end the round with a round-ending event for a testmerge, we are allowed to do so, but I wanted to make an enemy that was engaging rather than an arbitrary round ender, but with artificial limits imposed so it could never actually reach any critical areas.
I suppose while plasma flood wasn’t intended, I’m aware of the immediate testmerge protocols, so woe is me who wasn’t aware of it to happen on the next round. Hope the clearance was made there will be a test merge as the round ended, however, so the report wasn’t needed to be made.
I was not informed clearer as I was within the round (The reason of excuse against atmos breach was both in a mix of plasma flooding, and the commentaries of the people’s report through the radio that the blobs were in the atmos), while as even if there was a whole breach and mess, round end for the test merge was coming in, making whole things valid.
I think the report can be closed, unless there are more commentaries to be made.
