From Release Notes:
Dust to Dust is now a standard episode.
This is found as the last episode in the Delta Quadrant arc.
This mission is now set to level 60.
The Mission starts with Vaadies attacking Kobali, but the last mission in main arc (leve 59) basically ends the conflict since we got rid of the main orchestrator of the aggression against the Kobali. Additionally, Dust to Dust has more of a connection to the last mission in the Kobali Prime ground story arc than the Vaady main arc.
For those reasons, it should be at the end of the Kobali Arc (level 58) so it is in between the last Kobali story (we see Ensign Kim in the container) and the last Vaady Mission (level 59) that ends the whole Vaady aggression. The last mission in the overall Delta Arc should continue to be the one that has us finding Sela and discovering the connection to Iconians. Anything after that (like Dust to Dust) is anti-climatic.
From Release Notes:
Dust to Dust is now a standard episode.
This is found as the last episode in the Delta Quadrant arc.
This mission is now set to level 60.
The Mission starts with Vaadies attacking Kobali, but the last mission in main arc (leve 59) basically ends the conflict since we got rid of the main orchestrator of the aggression against the Kobali. Additionally, Dust to Dust has more of a connection to the last mission in the Kobali Prime ground story arc than the Vaady main arc.
For those reasons, it should be at the end of the Kobali Arc (level 58) so it is in between the last Kobali story (we see Ensign Kim in the container) and the last Vaady Mission (level 59) that ends the whole Vaady aggression. The last mission in the overall Delta Arc should continue to be the one that has us finding Sela and discovering the connection to Iconians. Anything after that (like Dust to Dust) is anti-climatic.
The very beginning of the episode gives a possible (but not completely true) explanation about why the Vaadwaurs are attacking (the new leader being uncooperative) despite their former leader being gone and Lindsey gives you the real reason later in the episode (a Vaadwaur alarm got triggered).
Yes, it should be placed before takedown to maintain continuity for new players.
Edit:
At the beginning of Dust to Dust, Kim makes a remark about how Eldex isn't responding to communications about the renewed Vaadwaur attack on Kobali Prime.
D'oh. Good point. But I agree with sentinel64 that it works better to end the story with the Sela mission.
It can be before or after "What's Left Behind" (the Sela mission), since it neither mission references the other, but it should still be after "Takedown". At the beginning of Dust to Dust, Kim makes a remark about how Eldex isn't responding to communications about the renewed Vaadwaur attack on Kobali Prime. This makes the assumption that Eldex is in charge of all the Vaadwaur.
Personally, I think it should be just after "Takedown" at level 59, just so that getting from level 59 to level 60 is a bit easier.
Support 90 degree arc limitation on BFaW! Save our ships from looking like flying disco balls of dumb!
There's a line at the beginning that states that Eldex has been uncooperative since Gaul's defeat and is now leading their forces. It suggests the truce was only a temporary one to route out Gaul and any Vaadwaur infected with the neural parasites. The Vaadwaur conflict with the Kobali continued, but at the end of the mission, the Kobali made the list of Vaadwaur in their temple public knowledge and would allow any of them to be returned to their people.
It can be before or after "What's Left Behind" (the Sela mission)
IMO, each approach is possible and as valid as the other:
-before "What's Left Behind" to directly bring an epilogue to the Kobali conflict and then go back to the Iconian conspiracy
-after "What's Left Behind" to take a break from Sela's "holier than thou/never my fault" behavior and to give Jetanian time to have the flagship finished and his crew assembled.
It's made pretty clear that the reason the Vaadwaur keep attaking Kobali space is because the Kobali are murdering the Vaadwaur in cryostorage under their "temple" and then reviving them as more Kobali.
It's made pretty clear that the reason the Vaadwaur keep attaking Kobali space is because the Kobali are murdering the Vaadwaur in cryostorage under their "temple" and then reviving them as more Kobali.
It's pretty clear according to "Dust to Dust" that's not the reason. The Kobali could be doing this, but it's not why they're attacking in this episode.
From Release Notes:
Dust to Dust is now a standard episode.
This is found as the last episode in the Delta Quadrant arc.
This mission is now set to level 60.
The Mission starts with Vaadies attacking Kobali, but the last mission in main arc (leve 59) basically ends the conflict since we got rid of the main orchestrator of the aggression against the Kobali. Additionally, Dust to Dust has more of a connection to the last mission in the Kobali Prime ground story arc than the Vaady main arc.
For those reasons, it should be at the end of the Kobali Arc (level 58) so it is in between the last Kobali story (we see Ensign Kim in the container) and the last Vaady Mission (level 59) that ends the whole Vaady aggression. The last mission in the overall Delta Arc should continue to be the one that has us finding Sela and discovering the connection to Iconians. Anything after that (like Dust to Dust) is anti-climatic.
They do explain in the run down before the mission that they dont know why the Vaadwaur are attacking AGAIN.
I prefer it this way; you are called back to Kobali Prime because of a breakaway faction of Vaadwaur that want the bodies back no matter what. Breakaway because as that one patrol mission in the Delta Quadrant shows, the Vaadwaur aren't as monolithic as you'd think them to be. Eldex has no control of them so cannot be reached. Plot hole? Yes. But take it or leave it.
From Release Notes:
Dust to Dust is now a standard episode.
This is found as the last episode in the Delta Quadrant arc.
This mission is now set to level 60.
The Mission starts with Vaadies attacking Kobali, but the last mission in main arc (leve 59) basically ends the conflict since we got rid of the main orchestrator of the aggression against the Kobali. Additionally, Dust to Dust has more of a connection to the last mission in the Kobali Prime ground story arc than the Vaady main arc.
For those reasons, it should be at the end of the Kobali Arc (level 58) so it is in between the last Kobali story (we see Ensign Kim in the container) and the last Vaady Mission (level 59) that ends the whole Vaady aggression. The last mission in the overall Delta Arc should continue to be the one that has us finding Sela and discovering the connection to Iconians. Anything after that (like Dust to Dust) is anti-climatic.
the records stated that the vaadwuar attack the first time around was because of the kobali rebirthing dead vaadwuar which is what caused the attack in the first place, the vaadwuar were driven off world with assistance from allies from another quadrant of the galaxy. however the second attack is because ketan tripped a security measure that alerted the vaadwuar to think the vaadwuar corpses were once again being converted by the kobali and they again tried to take the temple. no idea what happened after that, but considering the ships in orbit and how contained the vaadwuar were on the ground as well, it is seriously doubtful they had the means to cause trouble for very long, that and they were running out of people to keep being a threat. in addition, the kobali gave back the bodies to their people as a sign of respect, the vaadwuar if they were defeated again, they are not likely to return.
T6 Miranda Hero Ship FTW. Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
It's made pretty clear that the reason the Vaadwaur keep attaking Kobali space is because the Kobali are murdering the Vaadwaur in cryostorage under their "temple" and then reviving them as more Kobali.
There has never been any indication of the Kobali killing anyone outside the battlefield.
The Vaadwaur used from the pods were already dead because the Kobali only used failed pods.
the records stated that the vaadwuar attack the first time around was because of the kobali rebirthing dead vaadwuar which is what caused the attack in the first place, the vaadwuar were driven off world with assistance from allies from another quadrant of the galaxy. however the second attack is because ketan tripped a security measure that alerted the vaadwuar to think the vaadwuar corpses were once again being converted by the kobali and they again tried to take the temple. no idea what happened after that, but considering the ships in orbit and how contained the vaadwuar were on the ground as well, it is seriously doubtful they had the means to cause trouble for very long, that and they were running out of people to keep being a threat. in addition, the kobali gave back the bodies to their people as a sign of respect, the vaadwuar if they were defeated again, they are not likely to return.
Unfortunately Cryptic will more then likely ignore this and continue to throw waves of Vaadwaur at us in the future. Completely throwing out the fact that the Vaadwaur are not large in number for the sake of 'a better story'.
Just look at every other bad guy we've faced in game. Can you estimate how many Klingons, Romulans, Cardassians and varying other species youve killed over the course of this game? The Vaadwaur will be no different.
Comments
The very beginning of the episode gives a possible (but not completely true) explanation about why the Vaadwaurs are attacking (the new leader being uncooperative) despite their former leader being gone and Lindsey gives you the real reason later in the episode (a Vaadwaur alarm got triggered).
Edit:
D'oh. Good point. But I agree with sentinel64 that it works better to end the story with the Sela mission.
Personally, I think it should be just after "Takedown" at level 59, just so that getting from level 59 to level 60 is a bit easier.
Support 90 degree arc limitation on BFaW! Save our ships from looking like flying disco balls of dumb!
IMO, each approach is possible and as valid as the other:
-before "What's Left Behind" to directly bring an epilogue to the Kobali conflict and then go back to the Iconian conspiracy
-after "What's Left Behind" to take a break from Sela's "holier than thou/never my fault" behavior and to give Jetanian time to have the flagship finished and his crew assembled.
It's pretty clear according to "Dust to Dust" that's not the reason. The Kobali could be doing this, but it's not why they're attacking in this episode.
They do explain in the run down before the mission that they dont know why the Vaadwaur are attacking AGAIN.
The mission is not out of order.
http://www.arcgames.com/en/games/star-trek-online/news/detail/10052253
Why are you not rejoicing?
the records stated that the vaadwuar attack the first time around was because of the kobali rebirthing dead vaadwuar which is what caused the attack in the first place, the vaadwuar were driven off world with assistance from allies from another quadrant of the galaxy. however the second attack is because ketan tripped a security measure that alerted the vaadwuar to think the vaadwuar corpses were once again being converted by the kobali and they again tried to take the temple. no idea what happened after that, but considering the ships in orbit and how contained the vaadwuar were on the ground as well, it is seriously doubtful they had the means to cause trouble for very long, that and they were running out of people to keep being a threat. in addition, the kobali gave back the bodies to their people as a sign of respect, the vaadwuar if they were defeated again, they are not likely to return.
Been around since Dec 2010 on STO and bought LTS in Apr 2013 for STO.
There has never been any indication of the Kobali killing anyone outside the battlefield.
The Vaadwaur used from the pods were already dead because the Kobali only used failed pods.
Unfortunately Cryptic will more then likely ignore this and continue to throw waves of Vaadwaur at us in the future. Completely throwing out the fact that the Vaadwaur are not large in number for the sake of 'a better story'.
Just look at every other bad guy we've faced in game. Can you estimate how many Klingons, Romulans, Cardassians and varying other species youve killed over the course of this game? The Vaadwaur will be no different.