|
|
Post by Spy227X on Feb 10, 2014 20:34:22 GMT
I freaking HATE IT when the heads hog the events. I mean, some events aren't to be public to general crew, but when they start telling silicons, IAA, staff of a department that should be involved, and stuff to fuck off? This is just crossing the line for me. Seriously. This has happened to me about 20 times by now, and at least 5 of those on this server.
|
|
|
|
Post by pkisbest on Feb 10, 2014 20:43:00 GMT
I mostly agree with this. Most of the time heads like the CMO don't even get involved. It's mainly the Captain,HoP, HoS and some sec officers.
|
|
|
|
Post by Skull132 on Feb 10, 2014 20:44:53 GMT
The SPECIFIC issue in question requires medical involvement at the start. A controlled environment, which the heads are capable of providing. The plan is/was to follow this up with later actions with the crew.
|
|
|
|
Post by Spy227X on Feb 10, 2014 20:56:50 GMT
Yeah, but when the heads start not trusting totally trustable crew members...
|
|
|
|
Post by Skull132 on Feb 10, 2014 21:10:40 GMT
They weren't. I am observing this round, I am fully aware of what's going on. It's a matter of operational security and sensitive cases. They didn't want a borg due to what they knew about the subject; they didn't want an alien due to what they knew about the subject.
|
|
|
|
Post by Spy227X on Feb 10, 2014 21:15:23 GMT
They weren't. I am observing this round, I am fully aware of what's going on. It's a matter of operational security and sensitive cases. They didn't want a borg due to what they knew about the subject; they didn't want an alien due to what they knew about the subject. Other rounds. Other ones. They have not trusted staff that knew about the subject, and other things. |
|
|
|
Post by Skull132 on Feb 10, 2014 21:28:59 GMT
Alright, unfortunately that is something I, personally, cannot answer for.
ALTHOUGH! Gents, keep one thing in mind! Assisting with event development is a two way responsibility! Ranting does not help! Providing CONSTRUCTIVE feedback, often accompanied by SPECIFIC examples, in my opinion, will help the best!
|
|
|
|
Post by sgtsammac on Feb 10, 2014 23:03:18 GMT
Explanation of today's event: yes it WAS head exclusive at first, because that's how NanoTrasen is, it's an unresearched subject, safety is unknown. She was woken up, not a word of galactic standard English known, no point loosing her on the crew, so we try to find out more. We then move her to medical. ( this is when we got all the lag and connection issues). There were plans in place to involve the rest of you, but the RP really was advancing slowly, and quite realistically and possibly a future extension to the event.
There were some issues at the end, but not really to do with the event.
|
|
|
|
Post by Spy227X on Feb 11, 2014 1:14:46 GMT
Other rounds. Other ones. They have not trusted staff that knew about the subject, and other things. |
|
robotik
Surgeon
http://puu.sh/1AJEA
Posts: 86 
|
Post by robotik on Feb 11, 2014 1:15:40 GMT
From what I know about how NT likes strangers on the Aurora, they don't. Vox, they kick out. Aliens, they treat like shit. NanoTrasen doesn't really have a favorable history with strangers on their station. The fact that some frozen human managed to come in to the station, and we make sure his/her confidentiality is secure, is beyond ridiculous. This is a research station, not a 24/7 galactic motel.
|
|
farcry11
Moderator 
God Emperor of Pleb Kind
Strictly Platonic
Posts: 1,347
|
Post by farcry11 on Feb 11, 2014 4:55:00 GMT
Fuck's sake, stop focusing on the one event. Spy has repeatedly tried to put this back on track.
And yes, I'm gonna agree with him here, heads tend to keep events to themselves, which is kinda dumb. They have henchmen! They should use them!
|
|
lk600
Head Of Security
Procrastinator by trade...
Posts: 300
|
Post by lk600 on Feb 11, 2014 4:59:13 GMT
The native event today was not as planned as it should have been. It was obviously too slow for 'some' people's likings what saddens me slightly. But one thing for sure that we must keep in mind, this is and RP server. We keep in character. If a crew member orders a cyborg away... the cyborg will comply. If a situation that involves reviving a native that no one knows fully about means it should be done slowly and carefully... its how it is done.
|
|
|
|
Post by pkisbest on Feb 11, 2014 5:29:25 GMT
It's not just in the event today(I wasn't there haha) it's in nearly every event. Characters who are always played,Cap,HoS and sec are ALWAYS hogging the attention. The HoP,CMO,RD and CE are rarely involved even. Let alone any other job being directly involved.
|
|
|
|
Post by Spy227X on Feb 11, 2014 15:37:44 GMT
Other rounds. Other ones. They have not trusted staff that knew about the subject, and other things. PLEASE LISTEN |
|
lk600
Head Of Security
Procrastinator by trade...
Posts: 300
|
Post by lk600 on Feb 11, 2014 15:44:53 GMT
Again... its situational. Like my point I made, Heads are there to take charge of delicate situations. If you had to run a high-tech science station, would you want the cook, janitor, botanists and the like to get involved in such things as fire fights, first contact, classified documents? Yes... it may seem hogged, at first. With the event yesterday, we were trying to make our way out to the crew and involve others to the point that alot of RP was rushed because of the bitching complaints that kept coming through OOC. But... someone called a vote because they did not want to wait. RP is not magic, we have to make it ourselves and that can take time.
|
|
|
|
Post by Nightmare on Feb 11, 2014 17:27:12 GMT
Im curious. What event are you taking about spy. Please give examples.
|
|
|
|
Post by Casperf1 on Feb 11, 2014 19:11:18 GMT
You need to think about it relative to your job though. As LK said, why would you have a cyborg watch some unknown individual that was coming out of cryostasis for the first time in god knows how many years? If that person was from Earth 500 years before and had no idea what a cyborg was, I thin it'd come as quite a bit of a shock.
It's the same principle with any other event though, the Chain of Command. Central Command are going to speak directly to the Captain and those below her, via discrete faxes etcetera. They won't just directly undermine this established Command hierarchy and talk directly to the engineers, or the detective. It just doesn't make sense.
I do agree that the event regarding the blonde woman in 'stasis could've been so much better, and was almost exclusively head-only, but think about it. It's a Research station with a clear Chain of Command, you're not just going to send some frozen individual, whom you have no idea about, and go "Scientist and cyborg, talk to this frozen body that we found please."
Events tend to involve some form of direct Central-interference, regarding the source. So more-than-likely, you're going to have security there in case things goes south, the Captain for 'first-contact' and the Command staff WILL naturally be briefed before, and take priority over, the bartender.
|
|
|
|
Post by yeahchris on Feb 11, 2014 22:14:20 GMT
The issue here is that command should be interfacing with the chain of command, but that those in command positions onboard the station should then take those orders and delegate them to their staff. That second part regularly fails to happen, and instead we have command staff which simply does everything on their own while keeping their staff in the dark.
|
|
|
|
Post by pkisbest on Feb 11, 2014 22:22:00 GMT
The issue here is that command should be interfacing with the chain of command, but that those in command positions onboard the station should then take those orders and delegate them to their staff. That second part regularly fails to happen, and instead we have command staff which simply does everything on their own while keeping their staff in the dark. This. As CMO in any time I try to delegate my staff to do things. Whether it's chemistry,viro or genetics I find something for them to do |
|
|
|
Post by Spy227X on Feb 11, 2014 23:27:06 GMT
|
|
