Lvl 60 TOS toon. Wolf 359 is there but no where to enter it. Is this a bug to be fixed some other day, meaning that my TOS toon I selected to go for the ship will have to be changed to someone other than them?
I tried having a non-tos toon do the mission first, no change.
Tried having a tos toon go straight to wolf 359 do not pass go do not collect $200 - nope
I even tried circling all the way to the top of the "galaxy" and then to the bottom of Wolf 359 so there is no secret entrance above or below Wolf 359.
So if they have to put this in a patch, they should allow which they won't, the tos toon to repeat the Omega Mission with the 40 vouchers equal to the number of days the problem remains unfixed.
So dropping mission will not result in a cooldown?
Nope just tried it didn't work. However it gave me new locations to visit andoria, dil mining and k7, so lets see if they work.
Okay those locations did work. So I guess for all AOY that get the wolf 359, since we know how patches get done in sto, drop the mission and roll the dice for something other than 359.
Drop the mission, and then go to the Wolf 359 system, enter the system and then hail Q for the daily mission.
I was having the same problem, but this worked for me, hope it works for everyone else.
The problem is this does not work. When one can't get into the Wolf 359 system to begin with, dropping the mission and reacquiring said mission does nothing.
The problem is this does not work. When one can't get into the Wolf 359 system to begin with, dropping the mission and reacquiring said mission does nothing.
You're assuming the mission uses a set list. It doesn't. It uses a large list that randomly generates a few locations to go to.
You can't get into Wolf 359.
The location is one of many selected randomly when you acquire the mission. If Wolf 359 pops up on your list, you WON'T be able to complete it. Drop the mission. It's just taking up space on your list and can never be completed until you get a list of locations you CAN get into.
Here's a list of the known locations. Wolf 359 was closed around the time they got rid of some other stuff. I actually don't know if anyone has been able to get in since then. As I haven't bothered with it, since it was a dead area anyway, I can't say for certain. Trying to remember if a mission was attached to it or not. Drawing a blank.
The problem is this does not work. When one can't get into the Wolf 359 system to begin with, dropping the mission and reacquiring said mission does nothing.
You're assuming the mission uses a set list. It doesn't. It uses a large list that randomly generates a few locations to go to.
You can't get into Wolf 359.
The location is one of many selected randomly when you acquire the mission. If Wolf 359 pops up on your list, you WON'T be able to complete it. Drop the mission. It's just taking up space on your list and can never be completed until you get a list of locations you CAN get into.
Here's a list of the known locations. Wolf 359 was closed around the time they got rid of some other stuff. I actually don't know if anyone has been able to get in since then. As I haven't bothered with it, since it was a dead area anyway, I can't say for certain. Trying to remember if a mission was attached to it or not. Drawing a blank.
This is not a work around... the location for the scans is fixed at each given time... if you see Wolf 359, no matter how many times you drop and reacquire... it will still show Wolf 359. You need to wait for the locations to change in the next cycle. Not sure what the time frame is for the locations to change. Could be an hour or 2 or 4...
This bug with Wolf 359 also only affects TOS Fed toons... regular and Delta Recruit Feds do not have this problem with Wolf 359.
makes sense, but as said I didn't pull wolf 359 yesterday on my TOS. if the rotation is fixed, it would be nice to know the rotation, true. its an old problem.
It'd be nice if this was fixed. I hate having my time wasted. It sucks to have to start over, and it would suck worse if you failed to get it for this an error on the part of Cryptic.
If it doesn't use a set list, why am I getting the same choices after dropping the mission twenty times?
It's a set list, you need to wait for the quest to refresh on server side to change locations... no idea on time frame... could be 4 hours... that's how long it takes for sector space doff assignments to refresh.
Basically, the thing to do is to play through the FE on a non-AOY character and start a new ship grind. Waiting on the server change to reacquire the mission is an option, but over the course of the event it may get tiresome (and depending on timing and playstyles, cost you days.)
There's still plenty of time to make the change over and grind with a new character, provided you take action now. Consider this being warned. Cryptic may or may not fix Wolf 359 access problems in the near future, and that may or may not be a sufficient roadblock to prevent you from getting the ship. Don't hesitate and thereby risk a bad situation. Just swap characters.
Bipedal mammal and senior Foundry author.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
My TOS Level 60 was the designated Character to unlock the Anniversary, given that honor for unlocking the Winter Event Ship. Wolf 359 was pulled the second day and has no way to get in.
I have my only non-60 Character, a Federation Engineer Level 31, taking over. Already has two dailies done and will do the FE tomorrow. Could use XP on that Character anyway and will get some decent equipment that will freely upgrade to XII.
There seems to be a bit of the behind the scenes things broken on TOS Characters. Originally no home to be deposited with a forced ejection from Winter Wonderland, Wolf 359, inability to transfer equipment automatically to a new ship, etc.
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
That's the best advice going at this point in time, and in fact what I did so as to avoid further complications.
In the past, they've extended it for problems, bugs, etc, etc.; clearly, no guarantee they'll do ANYthing in the future. I'd just like to hear from a Dev on this - no offense, but advice from a fellow forum person is only worth so much. It seems an easy fix would be for them to remove Wolf359 from the "random generated" list. If it follows the doff system, they referesh on something like a 20 hour schedule. Be awfully sh!tty for them to allow folks to continue having issues over this.
Oh, and I'd like my lost day back, too. I'll take it in lobi, please & ty.
It's frustrating to think that this can simply be fixed within a few seconds by a developer going into that great big IDE they use and adding the TOS faction to the allowed list on the system settings/info panel.
Well I'm assuming it's that easy, considering every game I've worked on or modded has an SDK with GUI editor of some form it would be surprising if STO was being coded with just 3Ds Max, text files and compilers... Even if hilariously; the game heavily relied on someone opening up notepad++ it'd still just be a matter of finding the description file for the system and adding the TOS faction to that list then recompiling...
The only reason I posted this was to make people realise how easy it can be to edit things like this and how unacceptable it is that these bugs seem to sit around for so long, I mean technically it's not even a bug, the thing is working as intended, somebody just hasn't set it up correctly...
Can you drop the mission, and pick it up from Q again, with a different set of particles to collect?
That worked for me, didn't have a cool down and grabbed the mission from Q again with different locations.
I tried doing that for hours, kept getting the exact same locations. Sucky thing is that I am going ....elsewhere....where I will have NO internet access whatsoever during the event. The timing was perfect, IF I managed to get in and do the event before leaving on my departure date I would have just enough to claim the ship.
Of course now, having lost a day due to the Wolf 359 bug, I will be 40 (or more) tokens short. I am running the event on a non AoY toon now, but at best, that toon will be 80 tokens short.
2-6 tokens for 5 lobi to make up the difference. Let's see, if the RNG gods award an average of 4 tokens, that means opening at least 10 lock boxes .....assuming I average 5 lobi per box....which never happens for me. Which means buying at least 10 keys (assuming my AoY toon does not get Wolf 359 again between now and then, at least 20 keys otherwise). So, if I want the "free" ship, it's going to cost me anywhere from 50-110M EC to get keys from the exchange, or whatever the cost of keys is in Zen at the time I actually have some extra money to spend.
I seem to remember that last year there was a problem with getting Omegas at Rura Penthe (I think that was the location) and after fixing it, they awarded everyone X number of Anniversary tokens to make up for the missed days. Granted, this time it only affects AoY toons, but something similar would be nice this time. Award tokens only claimable once per account and only claimable by AoY toons......
No, she posted later that it was one of the K-bases & she had the incorrect one.
Yes,
She had trouble finding Omegas at K-13 because they were actually at K-(9?).
I was joking that:
She had trouble getting into Wolf 599 because they actually needed Wolf 359.
Then again, explaining a joke is like dissecting a frog. You'll understand it in the end, but the frog never comes back from it.
"Logic is a little tweeting bird chirping in a meadow. Logic is a wreath of pretty flowers which smell BAD." - Spock
No, she posted later that it was one of the K-bases & she had the incorrect one.
Yes,
She had trouble finding Omegas at K-13 because they were actually at K-(9?).
I was joking that:
She had trouble getting into Wolf 599 because they actually needed Wolf 359.
Then again, explaining a joke is like dissecting a frog. You'll understand it in the end, but the frog never comes back from it.
I ran into this problem today. I dropped the mission several times and kept getting the same mission again. I waited a couple of hours and got a new set of locations and they did not include Wolf 359! It is a clumsy work around, but it worked for me!
As I said earlier, they are aware, as they Tweeted that. They are working on a fix.
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
Comments
Tried having a tos toon go straight to wolf 359 do not pass go do not collect $200 - nope
I even tried circling all the way to the top of the "galaxy" and then to the bottom of Wolf 359 so there is no secret entrance above or below Wolf 359.
So if they have to put this in a patch, they should allow which they won't, the tos toon to repeat the Omega Mission with the 40 vouchers equal to the number of days the problem remains unfixed.
Remember that you only need to unlock the ship on one character. It's then claimable for all other characters including ones you create in the future.
Drop the mission, and then go to the Wolf 359 system, enter the system and then hail Q for the daily mission.
I was having the same problem, but this worked for me, hope it works for everyone else.
Nope just tried it didn't work. However it gave me new locations to visit andoria, dil mining and k7, so lets see if they work.
Okay those locations did work. So I guess for all AOY that get the wolf 359, since we know how patches get done in sto, drop the mission and roll the dice for something other than 359.
The problem is this does not work. When one can't get into the Wolf 359 system to begin with, dropping the mission and reacquiring said mission does nothing.
You're assuming the mission uses a set list. It doesn't. It uses a large list that randomly generates a few locations to go to.
You can't get into Wolf 359.
The location is one of many selected randomly when you acquire the mission. If Wolf 359 pops up on your list, you WON'T be able to complete it. Drop the mission. It's just taking up space on your list and can never be completed until you get a list of locations you CAN get into.
Here's a list of the known locations. Wolf 359 was closed around the time they got rid of some other stuff. I actually don't know if anyone has been able to get in since then. As I haven't bothered with it, since it was a dead area anyway, I can't say for certain. Trying to remember if a mission was attached to it or not. Drawing a blank.
http://sto.gamepedia.com/Mission:_Omega_Molecule_Stabilization
This is not a work around... the location for the scans is fixed at each given time... if you see Wolf 359, no matter how many times you drop and reacquire... it will still show Wolf 359. You need to wait for the locations to change in the next cycle. Not sure what the time frame is for the locations to change. Could be an hour or 2 or 4...
This bug with Wolf 359 also only affects TOS Fed toons... regular and Delta Recruit Feds do not have this problem with Wolf 359.
Can we get someone to weigh in officially?
It's a set list, you need to wait for the quest to refresh on server side to change locations... no idea on time frame... could be 4 hours... that's how long it takes for sector space doff assignments to refresh.
There's still plenty of time to make the change over and grind with a new character, provided you take action now. Consider this being warned. Cryptic may or may not fix Wolf 359 access problems in the near future, and that may or may not be a sufficient roadblock to prevent you from getting the ship. Don't hesitate and thereby risk a bad situation. Just swap characters.
Notable missions: Apex [AEI], Gemini [SSF], Trident [AEI], Evolution's Smile [SSF], Transcendence
Looking for something new to play? I've started building Foundry missions again in visual novel form!
I have my only non-60 Character, a Federation Engineer Level 31, taking over. Already has two dailies done and will do the FE tomorrow. Could use XP on that Character anyway and will get some decent equipment that will freely upgrade to XII.
There seems to be a bit of the behind the scenes things broken on TOS Characters. Originally no home to be deposited with a forced ejection from Winter Wonderland, Wolf 359, inability to transfer equipment automatically to a new ship, etc.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
In the past, they've extended it for problems, bugs, etc, etc.; clearly, no guarantee they'll do ANYthing in the future. I'd just like to hear from a Dev on this - no offense, but advice from a fellow forum person is only worth so much. It seems an easy fix would be for them to remove Wolf359 from the "random generated" list. If it follows the doff system, they referesh on something like a 20 hour schedule. Be awfully sh!tty for them to allow folks to continue having issues over this.
Oh, and I'd like my lost day back, too. I'll take it in lobi, please & ty.
Well I'm assuming it's that easy, considering every game I've worked on or modded has an SDK with GUI editor of some form it would be surprising if STO was being coded with just 3Ds Max, text files and compilers... Even if hilariously; the game heavily relied on someone opening up notepad++ it'd still just be a matter of finding the description file for the system and adding the TOS faction to that list then recompiling...
The only reason I posted this was to make people realise how easy it can be to edit things like this and how unacceptable it is that these bugs seem to sit around for so long, I mean technically it's not even a bug, the thing is working as intended, somebody just hasn't set it up correctly...
That worked for me, didn't have a cool down and grabbed the mission from Q again with different locations.
I tried doing that for hours, kept getting the exact same locations. Sucky thing is that I am going ....elsewhere....where I will have NO internet access whatsoever during the event. The timing was perfect, IF I managed to get in and do the event before leaving on my departure date I would have just enough to claim the ship.
Of course now, having lost a day due to the Wolf 359 bug, I will be 40 (or more) tokens short. I am running the event on a non AoY toon now, but at best, that toon will be 80 tokens short.
2-6 tokens for 5 lobi to make up the difference. Let's see, if the RNG gods award an average of 4 tokens, that means opening at least 10 lock boxes .....assuming I average 5 lobi per box....which never happens for me. Which means buying at least 10 keys (assuming my AoY toon does not get Wolf 359 again between now and then, at least 20 keys otherwise). So, if I want the "free" ship, it's going to cost me anywhere from 50-110M EC to get keys from the exchange, or whatever the cost of keys is in Zen at the time I actually have some extra money to spend.
I seem to remember that last year there was a problem with getting Omegas at Rura Penthe (I think that was the location) and after fixing it, they awarded everyone X number of Anniversary tokens to make up for the missed days. Granted, this time it only affects AoY toons, but something similar would be nice this time. Award tokens only claimable once per account and only claimable by AoY toons......
http://www.arcgames.com/en/forums/startrekonline#/discussion/1227698/k-13-space-omega
No, she posted later that it was one of the K-bases & she had the incorrect one.
Yes,
She had trouble finding Omegas at K-13 because they were actually at K-(9?).
I was joking that:
She had trouble getting into Wolf 599 because they actually needed Wolf 359.
Then again, explaining a joke is like dissecting a frog. You'll understand it in the end, but the frog never comes back from it.
Brain games; mine read what you wrote as 359.
You win.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'