Th frustration was/is real, fix that Egosoft please.

[Grimmrog]

Seriously has anyone even tested the rift mission outside the intented path?

don't read furthe rif you ahvent doen the quest as it contains spoilers.

So I follwoed that quesline where we wanna blow the rift with those antimatter stuff.

Naturally one appears here with a single ship if doing the missions early.
So remotebuild a cheap ship elsewhere and collected the matters with my current ships.
So far so nice.

we then had a renedvouz nar thta rift, i dropped the anitmatter and told the pilot to copllect it, then stationed his ship at the rift. and nothing happens. Logically most players will send a spare ship and not the one they sit in. So i flew at the rfit too, and exploded. (sure beause my ship needs to be there for the trigger, makes no sense) even less that it explodes without having the antimatter in it and being away from the rift, as the Quest giver told me to get away. Really annoing that th quest at this point is railed like this.

Next attemp flying to a station switching ships with the pilot of the second ship, so that I cna fly the cheap one into the rfit and then I step into my ship again.

Result: the pilot was too stupid changing the ship at the close refinery, as all he did wa sstanding buggd in the ship after having him assigned there. So just another reload sessions which hopefully fixes that, and it did.

Ok, now back to the rift, in with the cheap ship and surprise surprise. it's not the cheap one that got lost, it was still my first shiop which now was under the NPC pilots control. WTF is this? seriously how is that sooo badly designed.

So I tried a bit around with the save game but even if I keep the good ship at a station and use the cheap at the rift, then suddenly both are gone.
Why is this, what magically nonsene marked that old and better ship to be the one havign to be destroyed?

This is not fun, nor logical at all so please make this act at leats logical to make the ship with the natimatters explode in which the player is at least and not whatever causes this marker on my old ship.

[Kadatherion]

From my understanding - and yes, this is an oversight in the quest scripts - the first ship that has the antimatter cells in its cargo to get near the mission mark (which often is yours, as most players will go buy the antimatter personally), is flagged as the ship that will blow up. And stays as such, any further transfer of cargo doesn't change anything. So you need to stay the hell away from there before you have the cells on the correct ship, or you have to reload.

[astroshade]

The ship you're in on approaching the rift is always going to blow up. So send both to the rift, as soon as he says to get out of there get into your space suit and hop into the other ship and get out of there. Basically be piloting whichever ship you don't mind losing on first approach.

[Revenant342]

This mission worked properly for me when I built a new ship to sacrifice and had it pick up the antimatter cells remotely. Quest advanced when he flew up to the mission marker, while I stayed clear in my own ship (RIP Zuzuamis Lalundus Tumulis VIII, your sacrifice will probably be forgotten). Seems like the solution is to never be in the ship with the antimatter cells yourself.

[Kadatherion]

This mission worked properly for me when I built a new ship to sacrifice and had it pick up the antimatter cells remotely. Quest advanced when he flew up to the mission marker, while I stayed clear in my own ship (RIP Zuzuamis Lalundus Tumulis VIII, your sacrifice will probably be forgotten). Seems like the solution is to never be in the ship with the antimatter cells yourself.

I did buy the antimatter cells myself, I just stayed away from the mission mark and went there with the "sacrifice" ship only once the cells were in her cargo hold: all worked fine. That's why I believe the flag is set only when getting closer (as I had already seen happening on stream).

[Grimmrog]

The ship you're in on approaching the rift is always going to blow up. So send both to the rift, as soon as he says to get out of there get into your space suit and hop into the other ship and get out of there. Basically be piloting whichever ship you don't mind losing on first approach.

this is exactly what did not happen, i was in the cheap ship with the old one at some distance of 9km, and the ship i was in survived basically next to me, but it was the cheap throwaway one not my expensive old one.

[Grimmrog]

@reventant, when you remote bought them, does that mean you bought them into the trhow away ship?

I bouhgt the matters with my old ship and swapped cargo but it looks like the flag of which ship has to blow up is set where the cells go first. even had it at the station in an attemp which is 64km away both ships then were gone after approaching the rift.

[CaptainX4]

why even flag the ships? blow the one at the position when it has the antimatter. i seriously dont understand these developers...

[Kadatherion]

why even flag the ships? blow the one at the position when it has the antimatter. i seriously dont understand these developers...

I do. In a sense it's what seem to happen. The ship that has the antimatter *when it gets into position* (actually, when it gets in a range of at least a few clicks) is the one that's going to blow up. They simply didn't expect a player could transfer the cargo pretty much there, because - this is my guess - the coder that made that mission would never have expected the game to *NOT HAVE A FRIGGING TRANSFER CARGO BETWEEN SHIPS WHEN DOCKED* basic feature at release.
Thus he didn't realize the apparently easier solution (just flag the ship that gets there with the antimatter, instead of doing a more complex scan) could in many typical playthroughs lead to confusion. Still an oversight (could have happened anyway even with more sensible transfer cargo options, players are unpredictable), and might also be only a part of what happens (as other have reported a behaviour different and even more borked than what I experienced: even both ships blowing up??).
Also note that when coding the actual mission, the coder might not have known what the mission dialogue would precisely say in the final product, as it might have been recorded and written later, thus not knowing the worded mission guidance was going to be quite vague and he gave for granted that guidance would be enough to let him "get away" with an easier flag, just triggering the next step when the next waypoint is reached by the player, rather than having to code a real time scan for the ship to blow up or a manually triggered one (via dialogue choice/confirmation, IE: click on "1 - Ready, fire it up now Boron Moron!").

It's the kind of little silly miscommunication that Egosoft excels at. They are very enthusiast about their ideas, but their implementation is often a bit hurried.