test content
Logo
What is the Arc Client?
Install Arc
Options
[bug] assignments with doffs cannot be started
malazancommander
Member Posts: 0 Arc User
Even though I seem fulfill all requirements, at least according to the game, I can't begin some assignments with my KDF character. For example, I cannot start this assignment:
Image is here!
Image is here!
Post edited by malazancommander on
0
Comments
It seems to be related to assignments lasting more than 45 minutes and less than 4 hours, especially scientific and exploration assignments.
In these cases, even if all requirements are met, the button is disabled.
Not necessarily. I wanted to star the Suliban Cell Ship mission which is 5 days long with only doffs being a requirement to start the mission, and it still wouldn't start.
Last I checked, 5 days does not fit in to "more than 45 minutes and less than 4 hours".
Plus a Recruitment mission not only required 1 "Any Officer" but also required 5 colonists? Is that intentional?
That's why i wrote a "Not necessarily." in front of that sentence. To indicate that this mission is outside the observed norm.
I noticed that the game tried assigning a hologram from the character's crafting pack to the assignment, and their portrait was red. Swapping the hologram with a regular character didn't enable the assignment, though.
This character's level 16. I haven't seen the bug on any of my level 50 characters.
Update:
It's mostly with uncommon or rare science assignments.
RnD and upgrade needs less RNG. Less lottery. Something has to change.
I have 4 toons at level 50, and the bug still happens from time to time ... Zoning doesn't work, changing characters doesn't work, logging out and back in doesn't work., closing and restarting the entire client/game doesn't work ...
I've also had it happen on Marauding, Engineering, Espionage and Development missions, from "White" to "Purple" missions.
+1 Yes that! Happens on my three Federation toons (level 11, 50, 50), and specifically the Sci & Exploration ones.
Also others in the fleet are saying the same thing.
Hot fix this ASAP!
It's still listed in the "Known issues" of even the latest patch notes, so I guess that means we can't expect a fix any time soon ...
Because historically, once something is listed as a "Known Issue" for more than a couple of patches, it becomes a 'feature' which is 'Working as intended"