PhenixDeLumiere.7263 Posted September 12, 2022 Share Posted September 12, 2022 (edited) Hello, - I've signaled this bug a few times via email and with the IG support since May 2022, but the problem still exists, and the support suggested I should also post on forums, so here I am! (I previously posted on the French forums, but seeing the lack of response, some people suggested I also post it on the English forums.) - I know the "conditions" in order to complete this achievement: to have ongoing living story "9. To catch a spider", to complete the karma heart of the Brotherhood Woodlands, to NOT OPEN THE MAIL sent automatically by the game after completion of the heart. Unfortunately, I wasn't aware of this last condition, thus my issue... At the time, I had opened that automatic email precisely between the step 2 (locate the Jade Brotherhood supply cache) and the step 3 of the story (examine the Jade Brotherhood supply cache). Therefore, i had found the supply cache, but i didn't had time to interact with it because I had just opened the automatic mail sent for the progression of the living story. I literally saw that supply cache disappear before I could interact with it. - As step 2 is validated, the supply cache since then refused to reappear... I did the EOD story from A to Z with 4 or 5 toons since then, I tried starting another living story chapter at this specific step then restarting the ongoing EOD living story to check if it would have any effect following some suggestion of the support, I also stayed 30 minutes next to the spot of the supply cache, but so far the supply cache never reappeared. I therefore post here as a last gesture of despair and in the hope that maybe this bug will be more visible to the technical support! - Also, as a last resort, I was wondering if we could "reset" the progression of this achievement in order to be able to complete this achievement with no trouble? You will see in the following screenshots that I was to the precise spot of the supply cache with different toons with active story ongoing: https://zupimages.net/up/22/31/rn08.jpg https://zupimages.net/up/22/31/dfrs.jpg https://zupimages.net/up/22/31/w9ej.jpg https://zupimages.net/up/22/31/hbns.jpg https://zupimages.net/up/22/31/u7yb.jpg https://zupimages.net/up/22/37/tu7m.jpg https://zupimages.net/up/22/37/mlcn.jpg https://zupimages.net/up/22/37/vgbc.jpg Thanks for your help Edited September 12, 2022 by PhenixDeLumiere.7263 Link to comment Share on other sites More sharing options...
PhenixDeLumiere.7263 Posted October 6, 2022 Author Share Posted October 6, 2022 Is it possible to ge tthe support to look into this please ? thanks Link to comment Share on other sites More sharing options...
Linken.6345 Posted October 6, 2022 Share Posted October 6, 2022 5 hours ago, PhenixDeLumiere.7263 said: Is it possible to ge tthe support to look into this please ? thanks If you want support to look into it you have to create a support ticket. Link to comment Share on other sites More sharing options...
Inculpatus cedo.9234 Posted October 6, 2022 Share Posted October 6, 2022 2 hours ago, Linken.6345 said: If you want support to look into it you have to create a support ticket. If the original post indicates anything, the OP has already contacted the CS Team and they suggested he/she post on the forums (as usual with bugs). 1 Link to comment Share on other sites More sharing options...
Double Tap.3940 Posted October 6, 2022 Share Posted October 6, 2022 Hello! We're aware of this issue and looking into it. Thank you so much for notifying us! 1 Link to comment Share on other sites More sharing options...
Persie.4701 Posted February 11, 2023 Share Posted February 11, 2023 Is this already solved? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now