I am currently playing version 1.5 in coop mode. I have done all the tutorials and have completed chapters 1 and 2 of the story mission and I am trying to get chapter 3 to start but it wont. The mission directions said to make sure I was neutral with the free colonist and also have story mission chapter 2 complete and both are true of my character and the mission is not starting. I followed the direction and went to the Sky Guys bar at my starter planets orbit trading station and also made sure to have all the quest items I received so far on my character and noting still didn't happen. Not sure if I am doing something wrong or if the quest is bugged. Need some help on how to get the quest started if anyone has any ideas please share. The name of the quest is "Totally Overpowered"
... I just came looking for a fix for the same issue. Can't get it to start in MP, no matter how many times I buy a beer or sit down. However, I skipped getting the SV from the Zirax (I don't need it). Not sure if that part matters... Edit: I even went to a different starter world (all 4 are present in the MP game), and can't trigger it at a different station
I believe @Hummel-o-War stated somewhere that those Missions are not meant to work in Coop/MP but I can be wrong.
In case anyone has this problem, I was in coop playing the game with my hubby, I kicked him out and restarted my sav solo and the mission started instantly. I really only play this game with my hubby so it would be nice if there was a way to start the missions with out having to log out and log back in. I am hoping that when we sign back in together he can help me finish the mission even if he cant get it. I love the game but I cant play it solo because the flying makes me sick so my hubby does it for me. I hope this is something they can fix in the future. Also the first 2 chapters worked fine in coop and as a matter of fact me and my hubby has been playing this game together since they put in coop many alphas ago and we were able to do all the story missions. I wish the devs would chime in on this.
They may not be, but interestingly, most of them do very well. I'm wondering if there is a way we can use @Siri s trick for the players on our server, somehow...
My server admin doesn't seem keen on trying this, but @Siri might want to try it for her hubby: it may be possible for the server admin (coop host) to backup all the .ply files, copy the .ply file of a character that is "stuck" to their own id, load the server in SP, advance the quest, then shut down and copy the updated file to the correct player ID, and restore their own player ID file. ... but you need to understand the .ply files and what you are doing, and backup everything before you start, or you can screw up your players in your saved game.
I am the server admin who doesn't seem keen on trying this - so I tried it..... I went to the bar in MP, then Logged out and shut down the server with "saveandexit 0" copied the complete savegame folder from the server machine to the Saves\Games folder on my PC started the savegame locally As soon as it got loaded I got IDA's introduction to the new mission - however I was not in the bar at the top, but in the hangar at the bottom of the station. I went to the bar, but did not proceed with mission. I stopped my game, then copied my PLY file back to the server machine and started the game server. Then I was able to proceed with the mission as expected. Let's see how far I can get before the next hack will be necessary
That's the exact answer I was looking for Siri, since in my scenario I am "Hubby" and we were having the same issue. I also hope that the devs fix this so Coop players can play the storyline together!
Possible alternate fix: Stumbled into this; not sure if it actually works every time. The person who isn't able to trigger the quest: log out in the playfield for the questline. e.g., log out at the trading station or at the bar. If anyone else is in the same playfield, they also must log out, so the playfield unloads. After the playfield unloads, log back in. This triggered the quest for me on a MP server where it wasn't before. The server also likely had a restart between when I logged out and back in; not sure if that is an impact as well.
