Railjack navigation in groups

[Tofystedeth]

Hello,

I finished my railjack a couple weeks ago and generally have been having a lot of fun flying around in my spaceship pewpewing other smaller ships.

However, one big annoyance is that when I'm hosting a public group on my railjack, it seems anybody can use the navigation console and start a new mission.  That's not okay with me.  It's my ship.  I built it.  I'm hosting them.  I might (haven't, but could) let someone pilot it to shoot fighters while I do other stuff, but that doesn't mean I'd let someone choose the new destination.  If I'm on a roadtrip, I might let my friend drive while I take a nap, but they don't get to unilaterally decide we're going to Vegas instead of Kansas City.

The most egregious thing is that apparently, it doesn't even present the new destination as a voting option.  Or if it does, it provides no alert that I've seen while piloting.  I'm happily noodling around in the asteroid debris scooping resources when suddenly I lose control of my ship and get pulled into a jump to a new mission.  This has happened several times to me.  If people don't want to stick around to roomba every corner of the map, that's fine. They're welcome to find a new group, but don't let them take control of my ship away from me.

In summary, please lock the navigation console to only the railjack owner, or at least require the new destination to be voted on so the railjack owner can stay with their ship doing the thing they want to do while the rest of the group does their thing.

[AltheusVI]

Agreed, please lock the navigation to the host and the munitions to the pilot.

Make the main gun optional as to whether only the host can fire it or anyone can.

[Sentinel-14]

Originally the nav console was locked to the host. However, if the host was glitched out, stuck on a turret, dead and out of revives or just simply AFK no one could access the console to take the group back to the dojo. DE had to open up the console to anyone to ensure the group couldn't get stuck and have to abandon the mission (and the loot). Furthermore, if the nav console is locked to the host (or ship owner, either way) the rest of the group becomes hostage to that one player's whim. DE didn't want that either, so they've elected to leave the console open to the whole squad. If you're worried about people misusing the console, don't host public groups. Play solo, join other public groups as a player (not host) or run with a prebuilt team where you've explained your rules.


As to the other suggestion (since this is the Feedback forum) I agree that some form of mission voting needs to be implemented. Furthermore, I suggest that missions cannot begin until all team members have cast a vote. All too often on the starchart someone selects a mission and then immediately force-starts it before anyone else can vote. This is unacceptable.

[Tofystedeth]

1 hour ago, Sentinel-14 said:

Originally the nav console was locked to the host. However, if the host was glitched out, stuck on a turret, dead and out of revives or just simply AFK no one could access the console to take the group back to the dojo. DE had to open up the console to anyone to ensure the group couldn't get stuck and have to abandon the mission (and the loot). Furthermore, if the nav console is locked to the host (or ship owner, either way) the rest of the group becomes hostage to that one player's whim. DE didn't want that either, so they've elected to leave the console open to the whole squad. If you're worried about people misusing the console, don't host public groups. Play solo, join other public groups as a player (not host) or run with a prebuilt team where you've explained your rules.
 

Hmmm that makes sense, though I could swear I saw that leaving the group/mission after the completion reward you still get all the stuff.

I can understand not wanting people to be held hostage to my whims, and generally, if anybody actually says they want to move on, I can.  But I've been dragged away from rich debris fields full of rares without a word like 15 seconds after the mission ended.  Some of this is, admittedly, a social problem which you can never really fix with engineering.

[Steel_Rook]

1 hour ago, Sentinel-14 said:

Originally the nav console was locked to the host.

It was never locked to the host. I had people pick new destinations for me on the day of Empyrean's release. However, various sync bugs could sometimes prevent clients from interacting with the Navigation console. DE were pretty explicit that this was not intentional behaviour, and it was eventually fixed. I remember, because I had endless arguments with people refusing to believe me that clients were able to use my Nav Console.

With that said - the Nav Console requires a team-wide vote, same as any other mission. Why DE have not implemented this already is a mystery. Obviously letting random pubbies pick the next mission with no input from anyone is going to be problematic, but the game already has a system designed to combat this exact thing. It needs to work in Railjack, too.