Forums » Bugs
Well, I completed the first Centurion Superlight mission, and "unlocked" the second mission, but it's nowhere in the mission menu. My UIT standing is better than "hate" as required according to incarnate. My UIT standing is Dislike (-596) And by the way, I'm talking about the Courier Mission, here.
lucky you it did not recognice my kills in the first mission hunted by an army of bots i killed loads of assaults and guardians but the mission objectives never updated. most funny was that the queen did follow me also into the station sector...
anyway 8 assaults for part 2 and a armada for part 3, collectors queen, 5+ oruns x assaults. you guys are mad *shackes his head*.
if part 2 happens to be in a ionstorm i just fly back and abort to retake it.
Just the hits you get because one of the bots was lucky manage to kill you quickly... sorry no fun i that just to see how the quest bugs...
anyway 8 assaults for part 2 and a armada for part 3, collectors queen, 5+ oruns x assaults. you guys are mad *shackes his head*.
if part 2 happens to be in a ionstorm i just fly back and abort to retake it.
Just the hits you get because one of the bots was lucky manage to kill you quickly... sorry no fun i that just to see how the quest bugs...
I had problems with the second mission. I was in the sector the whole 6 minutes, killed the 2 bots it ask for and picked up the scrap metal from one. mission did not update until i went back to the station.
Ed
Ed
I had the same problem as blacknet...did everything and the mission didn't continue. Got bored of waiting and went back to D-14 were the mission terminated for not following instructions.
I was taking the mission before last night's update (yes, it WAS available if you'd met the prerequisites), and it was working perfectly fine for me -- got to the third area, but it was in an ion storm and I didn't have time to react to the assault and guardian bearing down on me. I did manage to kill the assault just before I died, though... XD
maybe i am just a whiny bitch, but such a mission without repairs is a fucking bad idea. you keep it like this then add the line "bring friends before you start (one with a repairgun is essential!)"
i mean c'mon we cleared queen sectors, loads of them but this mission actually is more luck based than anything else in comparission to that. normally you jump out get repairs and a friend takes over and keeps the bots busy but that mission is like "well we are out of ideas on how to make a real challanging mission so we thought something impossible might be fun" - it's not.
it only takes one lucky bot rushing in from a strange angle and landing a few hits and you know you will never make it alive. - starting over... if it is in a ionstorm you better start over now. what bs is that?
i mean c'mon we cleared queen sectors, loads of them but this mission actually is more luck based than anything else in comparission to that. normally you jump out get repairs and a friend takes over and keeps the bots busy but that mission is like "well we are out of ideas on how to make a real challanging mission so we thought something impossible might be fun" - it's not.
it only takes one lucky bot rushing in from a strange angle and landing a few hits and you know you will never make it alive. - starting over... if it is in a ionstorm you better start over now. what bs is that?
dunno .,. the missions seemed doable. although I misunderstood the mission text and docked between stage 2 and 3. :P
you just have to kill 4 bots overall though, of which only the orne is a bit of a problem.
you just have to kill 4 bots overall though, of which only the orne is a bit of a problem.
Hmm, well I managed it in a mid range trade ship ...
Stick close into the 'roids and use them as cover , kill the bots needed then double back along the chain to pick up the scrap .
Stick close into the 'roids and use them as cover , kill the bots needed then double back along the chain to pick up the scrap .
Part of the problem people are having is that sometimes the mission sends you into a sector that already contains hive bots -- sometimes bots of the same type that are being spawned by the mission -- which is a result of the mission editor's inability to black/whitelist certain sectors, like ones containing ion storms or bots of X/Y/Z type.
In my case, this resulted in me being sent to a sector that already had Dentek Assaults in it; when the mission spawned some and told me to kill two of them, I had to kill three or four before I got two from the group. My suggestion to "fix" this is to change the line in the mission that says (X/x used as examples, I don't know what the numbers are in these cases):
Objective X: Destroy N in group... (2) (npcgroup_x)
to
Objective X: Destroy N in group... (2) (NPCs of type...) (Dentek Assault)
This should probably also be the case for other similar lines in the mission code. It's not necessarily a foolproof way to get past the issue, but it should be sufficient to handle the edge case where the player is sent to a sector that already contains bots that he or she is being asked to kill. Of course, I don't know if it might mess with the code that ends the mission prematurely when you leave/dock. It shouldn't, I think.
In my case, this resulted in me being sent to a sector that already had Dentek Assaults in it; when the mission spawned some and told me to kill two of them, I had to kill three or four before I got two from the group. My suggestion to "fix" this is to change the line in the mission that says (X/x used as examples, I don't know what the numbers are in these cases):
Objective X: Destroy N in group... (2) (npcgroup_x)
to
Objective X: Destroy N in group... (2) (NPCs of type...) (Dentek Assault)
This should probably also be the case for other similar lines in the mission code. It's not necessarily a foolproof way to get past the issue, but it should be sufficient to handle the edge case where the player is sent to a sector that already contains bots that he or she is being asked to kill. Of course, I don't know if it might mess with the code that ends the mission prematurely when you leave/dock. It shouldn't, I think.
again 2nd step in ion storm, killed two assaults collected the scrap waited but NO mission update.
more funny ionstorm again i can't find the bots and they can't find me how genius.
ah even better we pick sectors used for HS missions with our men abandoining it already and all the crowd chasing ya...
but sure it has to be sedina *pity for lack of ideas*
more funny ionstorm again i can't find the bots and they can't find me how genius.
ah even better we pick sectors used for HS missions with our men abandoining it already and all the crowd chasing ya...
but sure it has to be sedina *pity for lack of ideas*
It's worked almost every time for me...
I got the Widow neuts, did the first Superlight mission, got a sufficient UIT standing - No idea what is happening here.
I'v done it twice now on 2 seperate chars all the way up past the courier mission and had no problems whatsoever
so now i have the shopping list to make the SL
so now i have the shopping list to make the SL
Im having the same problem as you physhi, got all requirements, yet its not showing
PLZZZ DEVS!
Fix this already :(
Fix this already :(
I took the first part of the mission (killing bots and taking the remains) then lifted my UIT standing to -590 but cannot see the next part of the mission... Maybe you need the UIT standing at the start of the first mission to see the second?
Courier mission was bugged for me, the 'client's representative' never showed up (i waited half an hour).
ahh so we have to not be uit hated, lame
Hmm, no, the only UIT standing requirement is in the 2nd mission. It's set for "Minimum Faction" "UIT" "Disliked". I've asked Andy to look into why it might not be posting.. it might be some problem with the mission system.
I figured out why. "Disliked" means -200, which is the top end of the range between -600 and -200 which is considered "Disliked". So it means the minimum faction it's checking is -200.
This is presented in a confusing way, obviously, so I changed the editor backend and we'll roll out a fix ASAP.
I'm also going to prevent it from picking storm sectors at some point this week. (I was hoping to have it work on monday but there was an unforseen setback I need to work around)
This is presented in a confusing way, obviously, so I changed the editor backend and we'll roll out a fix ASAP.
I'm also going to prevent it from picking storm sectors at some point this week. (I was hoping to have it work on monday but there was an unforseen setback I need to work around)