Allow POs to disable external launches

[Butterrobber202]

Summary (a quick, 2-3 sentence summary):I was a PO and my choices mattered a solid 0% because the Bridge Staff keep launching the Auto-Pilot. Even when I told them the LZ1 was fucked. What I is for POs to use the console on the Rasp. to disable external Auto-Pilot toggles.

Benefits (How this will benefit the server and game as a whole): POs won't be pushed around so often and will have a good say.

Details (Description of how you think this would work, the benefits, etc): Make it were POs disable external Auto-Pilot activations.

Implementation (Optional, if you have an idea how to implement it): Code, and ID locks.

( Just thought about it, maybe add a 20-second delay to the Auto Pilot so the PO has time to cancel it. )

[Jay Burns]

+1 yeah, the pilot job was quite necessary at one point, but now with bridge staff being able to use it, it makes the pilot redundant.

[Bigchilly]

+1, The time I've played as PO command would randomly auto pilot the shuttle alot, and would not say a word. And whenever i launched it manually i would say things like: "Rasputin dusting off" or "On station at LZ". When the pilot leaves the shuttle or vitals show KIA it should shut off.

[Warnipple]

The problem with PO being able to deny launches is that if the PO dies, the Rasp remains locked. This is a huge issue.

You may be wondering, well why don't we just auto unlock it when PO dies? Well there are a couple obvious answers to this.

[Butterrobber202]

The problem with PO being able to deny launches is that if the PO dies, the Rasp remains locked. This is a huge issue.

You may be wondering, well why don't we just auto unlock it when PO dies? Well there are a couple obvious answers to this.

Yeah I was thinking along those lines. Once the PO's vitals hit 0 its suit would signal the Rasp. to unlock

[Sarah_U.]

*Cough* Blue alert unlocks it.
*Cough* BO override.
*Cough* Taking syrup now kay *Cough*

Also, warnipple's problem is a bit about the meta I believe.

[Butterrobber202]

bump.

[Renomaki]

I remember before the PO was a thing, it was awfully stressing making sure the dropship and pod moved steadily while being berated for marines for not launching fast enough...

Now that we have the PO, it means command doesn't have to multitask as much as they used to.. Although it seems in some cases, they tend to forget that the PO exist. Communication is key, and if we can't be arsed to communicate, then we can't be a good command force.

But alas, some people are just ignorant I guess..

[Warnipple]

Right when PO was added, the PO was the only person who had access to the shuttle.I can't remember how it worked but I was playing as Commander and I didn't have access to the shuttle cockpit or controls at the bridge. Which is funny because why have controls at the bridge if you can't access them? And why doesn't the Commander have access to the Rasp?

Anyway, what I ended up doing to unlock the shuttle was make a new pilot ID to access it. Incredibly stupid method of fixing this issue, not to mention I broke a rule. I don't think this idea will ever be implemented and if it is then theres probably already one solution already in the works.

I'd lock this thread if I could but I can't.

[ZDashe]

I believe that this suggestion is unnecessary, mainly because PO is still relatively new and players have not adjusted sufficiently to work alongside the PO, rather than against him.

Command just needs to work together and communicate better. Even before we had POs, there were instances when SLs, CLs or MPs would just launch without prior warning or communication. Allowing anyone to lock down launches, regardless of who, is going to pose even more problems.

Suggestion: More communication.

[Butterrobber202]

To everyone with 'More communication'. Tell that to the BOs, that is the fucking problem, if I want to play PO I don't want Bridge staff wordlessly sending the Pod or Dropship, because it ruins my Job. My Idea is made in a way that Bridge staff can still use the Dropship and Pod, but gives the PO more control, I'm not asking for the old way to be returned, stop talking like I am.

[ParadoxalObserver]

I actually suggested this a few weeks ago (with a few added features). In my opinion, make it so that if you attempt an external launch while the PO is on the ship AND active the launch comes up as a request. The warning should come from the PO's helmet (has a visor, after all!). And if the PO is off the ship, there should be an extra minute before launch (that the PO shouldn't have). So if it's some random SL chucklefuck he can have time to rush back and cancel it.

Anyhow, the PO needs control over his ship. +1

[Wubs4Scrubs]

bumperino