Original Post — Direct link

I am unable to discover my last Mystery in Sciropescire. This is the Fly Agaric located south of Dudmastun Lake. I am working on 100% for this game and I have came across two mysteries that are bugged for my specific play through. Attached is a video of my issue. Please help, thank you!

">

over 2 years ago - UbiStorm - Direct link

@guest-VNMNelmG Hey there! I apologize for the very long delay in getting back to you about this issue with Mysteries! I'd also like to know if you still encounter this issue?

@JesseTheInsane Have you been able to interact with mushrooms located beneath the tree?

over 2 years ago - Ubi-Orion - Direct link

Hey there folks.

Thanks for your reports on this issue. If possible can you provide an up to date video demonstrating this issue we could take a look at? The video already in this thread was taken on an older version of the game so we need to see this happening on the latest version. Please also double check that your cloud saves are up to date with a save where this issue is present. Thanks.

over 2 years ago - Ubi-Gizmo - Direct link

Hey guys, thanks for the additional reports. I have gone ahead and forwarded this information over to the development team so that they can look into this further. Once we have more information on this, we will let you know.

@Rich4thestars - can you please let me know if you're playing on the PlayStation 4 or 5?

Please also let me know if you have any questions!

over 2 years ago - Ubi-Gizmo - Direct link

Hey again @rich4thestars, it is absolutely no problem; I want to also apologise for the delay regarding this bug, as I understand it has been in the game for quite some time. I hope you can get platinum soon, and let me know if you have any questions! 🙂

about 2 years ago - Ubi-Viral - Direct link

@punisherman420 Sorry to hear that you are also experiencing this issue. It is known and is being looked into.

Thank you.

about 2 years ago - Ubi-TheBerry - Direct link

Hey there @cooikizo ,

Thanks for reaching out to us!

Just to confirm - are you having this issue the current patch (1.5.0.1) too?