I just got the +10 endurance datatron from makeb. I checked my codex under Achievment datacrons and it should say 68/69 but it still says 67/69. Is anyone else having this problem if so is there away i can check to see if i got credit because after i clicked it i watched the cut scene then it said i recieved +10 endurance . After the cutscene ended i clicked the datacron 6 more times to make sure i got credit. each time itr said i couldnt access that datacron anymore.
#1 4/13/2013 9:33:00 PM
#3 7/9/2013 9:41:00 AMHi ClaudeTaylor,
In Game Update 2.2.2, we're fixing a bug that causes the Codex entry for "Galactic History 88: The Unlikely Champion" (a Makeb Datacron) to be listed incorrectly under Alderaan rather than Makeb. Will you please double check this and see if this is the issue that you're having? If so, please watch for this fix tomorrow morning. If not, will you please post to let us know?
#9 7/23/2013 4:27:00 AMAs a followup to this, the Codex entry for "Galactic History 88: The Unlikely Champion" does indeed appear to have been removed from Alderaan's section. However my Alderaan Codex is still showing 5/6 Datacrons, which means the Codex entry for "Galactic History 89: Capturing the Dread Masters" is still listed under Alderaan instead of Makeb.
Also, I still don't have the actual Codex entries in question even though I have obtained both Makeb datacrons. My Achievement: Datacrons section still reads 67/69.
Finally, Makeb doesn't even have a Codex entry in the Planet section to begin with. So while Alderaan has lost one its phantom datacrons, I have no idea if it was actually assigned to Makeb or not. So I'm not really sure what the point of this 'fix' was.
First of all, I really want to complement you for providing details like this. What you've given is exactly the type of information that helps me get to the bottom of these things for you guys.
As you may have noticed with the last few patches, we're working on getting the Codex cleaned up and corrected. We'll be sure to pass along what's been provided in this thread, and as any updates come about, we'll be sure to get them posted here.
Thanks to everyone for your ongoing patience, for communicating your reports to us, and for being a part of the community.