Logo Platform
logo amplifiers simplified

[Vaulter DLC] Cannot complete Vaulter racial quest "Reunification"

Reply
Copied to clipboard!
7 years ago
Jan 27, 2018, 3:16:51 AM

So I got the Reunification questline to level opbot to 10 and have him orbit Auriga 2.0. I leveled Opbot to 10 and he's been sitting in orbit of Auriga 2.0 for about 3 turns now and the quest doesn't seem to update.



Am I missing something?

Updated 7 years ago.
0Send private message
7 years ago
Jan 27, 2018, 3:48:30 AM

I mean, it's colonized by you already, check your Completed Quests, you probably already completed it without knowing it lol 

0Send private message
7 years ago
Jan 27, 2018, 4:04:23 AM
Suis3i wrote:

I mean, it's colonized by you already, check your Completed Quests, you probably already completed it without knowing it lol 

Are you attempting to troll me? The screenshot has the quest pinned in the upper right. Completed or failed quests can't be pinned. If you require more here is the questlog.


0Send private message
7 years ago
Jan 27, 2018, 5:38:09 AM
Lack wrote:
Suis3i wrote:

I mean, it's colonized by you already, check your Completed Quests, you probably already completed it without knowing it lol 

Are you attempting to troll me? The screenshot has the quest pinned in the upper right. Completed or failed quests can't be pinned. If you require more here is the questlog.


I'm not trolling you, just trying to help :/ 

You cannot colonize the system unless you've completed the Quest, as it is the reward for the Quest. I did not look at your pinned quest. 


If anything your game may be bugged. 


Only one planet on Auriga 2.0 should be colonized before you complete the quest, and that'll be by an AI (similar to the ENFER Incandescence system), populated by 4 or 5 Foundlings, I cannot remember the exact number right now. 

Updated 7 years ago.
0Send private message
7 years ago
Jan 27, 2018, 5:50:14 AM
Suis3i wrote:
Lack wrote:
Suis3i wrote:

I mean, it's colonized by you already, check your Completed Quests, you probably already completed it without knowing it lol 

Are you attempting to troll me? The screenshot has the quest pinned in the upper right. Completed or failed quests can't be pinned. If you require more here is the questlog.


I'm not trolling you, just trying to help :/ 

You cannot colonize the system unless you've completed the Quest, as it is the reward for the Quest. I did not look at your pinned quest. 


If anything your game may be bugged. 


Only one planet on Auriga 2.0 should be colonized before you complete the quest, and that'll be by an AI (similar to the ENFER Incandescence system), populated by 4 or 5 Foundlings, I cannot remember the exact number right now. 

You can totally colonize it using Pacific conversion. I did it to stop a rival grabbing it.

0Send private message
7 years ago
Jan 27, 2018, 6:13:36 PM
Lack wrote:
Suis3i wrote:
Lack wrote:
Suis3i wrote:

I mean, it's colonized by you already, check your Completed Quests, you probably already completed it without knowing it lol 

Are you attempting to troll me? The screenshot has the quest pinned in the upper right. Completed or failed quests can't be pinned. If you require more here is the questlog.


I'm not trolling you, just trying to help :/ 

You cannot colonize the system unless you've completed the Quest, as it is the reward for the Quest. I did not look at your pinned quest. 


If anything your game may be bugged. 


Only one planet on Auriga 2.0 should be colonized before you complete the quest, and that'll be by an AI (similar to the ENFER Incandescence system), populated by 4 or 5 Foundlings, I cannot remember the exact number right now. 

You can totally colonize it using Pacific conversion. I did it to stop a rival grabbing it.

Then that's where your mistake was, you're not suppose to colonize it before completing the Quest lol 

0Send private message
7 years ago
Jan 27, 2018, 9:44:26 PM

Presumably you shouldn't be able to. Or at least the quest should fail gracefully.

0Send private message
7 years ago
Jan 27, 2018, 11:41:11 PM

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

0Send private message
7 years ago
Jan 27, 2018, 11:43:01 PM
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

They'll probably fix it in the next update; if I were you I wouldn't worry too much about this. 


Btw the Vodyani "pirate" fleets still spawn in systems that aren't connected to your starting constellation but the AI generally doesn't attack the fleets (I'm not gonna say 100% b/c other players could have seen the AI disrupt their quests)

0Send private message
7 years ago
Jan 27, 2018, 11:50:00 PM
Suis3i wrote:
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

They'll probably fix it in the next update; if I were you I wouldn't worry too much about this. 


Btw the Vodyani "pirate" fleets still spawn in systems that aren't connected to your starting constellation but the AI generally doesn't attack the fleets (I'm not gonna say 100% b/c other players could have seen the AI disrupt their quests)

So you are saying I shouldn't worry about reporting a bug that could be fixed in the next update, in the bug report forum. Got it.

Updated 7 years ago.
0Send private message
7 years ago
Jan 28, 2018, 12:37:34 AM
Lack wrote:
Suis3i wrote:
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

They'll probably fix it in the next update; if I were you I wouldn't worry too much about this. 


Btw the Vodyani "pirate" fleets still spawn in systems that aren't connected to your starting constellation but the AI generally doesn't attack the fleets (I'm not gonna say 100% b/c other players could have seen the AI disrupt their quests)

So you are saying I shouldn't worry about reporting a bug that could be fixed in the next update, in the bug report forum. Got it.


Lack wrote:
Suis3i wrote:
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

They'll probably fix it in the next update; if I were you I wouldn't worry too much about this. 


Btw the Vodyani "pirate" fleets still spawn in systems that aren't connected to your starting constellation but the AI generally doesn't attack the fleets (I'm not gonna say 100% b/c other players could have seen the AI disrupt their quests)

So you are saying I shouldn't worry about reporting a bug that could be fixed in the next update, in the bug report forum. Got it.

Look stop being an ass first of all. Second I said don't worry about it for now since you now know how to avoid the bug until the DEV's fix it. 


I'm sure they've seen this post (as they don't respond to every post they see) so there's no point in worrying about it anymore. You reported it, it's not a super big deal, there are ways around it, life is good, the world isn't gonna end. 

0Send private message
7 years ago
Jan 28, 2018, 3:14:53 AM

As I understand it, this happened because you aquired the System via Pacific Conversion, before you put OpBot into position.


Something that might help: De-Colonize the System. Or maybe loose/gift it to a AI. Ideally while still having OpBot over the System. It is worth a try at least.

0Send private message
7 years ago
Jan 28, 2018, 5:37:37 AM
zgrssd wrote:

As I understand it, this happened because you aquired the System via Pacific Conversion, before you put OpBot into position.


Something that might help: De-Colonize the System. Or maybe loose/gift it to a AI. Ideally while still having OpBot over the System. It is worth a try at least.

I bypassed the issue by just going back to an earlier manual save. However, I kept the bugged ones and tested evacuating and gifting the system. Neither seemed to kick the quest log forward unfortunately.

0Send private message
7 years ago
Jan 28, 2018, 10:06:02 AM
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

Just one question, the AI that destroyed your pirate quest fleet was a Major faction, or a minor faction, like epistis?

0Send private message
7 years ago
Jan 28, 2018, 10:08:40 AM

did the AI builded attack ships just to attack that pirate fleet?

0Send private message
7 years ago
Jan 28, 2018, 7:44:28 PM
Velorace wrote:
Lack wrote:

Then this is a poor implementation. I recall a while back I had a similar issue with the Vod main quest that spawned a pirate fleet in a proximate system. Unfortunately the system was unconnected to mine and I couldn't get there before an AI faction destroyed them which also stuck the quest in permanently ongoing state. Either disable the ability for the player AND the AI to go out of bounds of quests or setup more robust fail states.

Just one question, the AI that destroyed your pirate quest fleet was a Major faction, or a minor faction, like epistis?

Nah this was about 7 months ago. Back then minor facs just spawned generic "Reapers" which didn't bother with quest spawned pirates. I think it was the Riftborn that knocked out the pirates though.

0Send private message
?

Click here to login

Reply
Comment

Characters : 0
No results
0Send private message