Incoming Blessing of the Worthy Patch
Hello everyone!
Through the helpful efforts of the community, we were alerted to a text description discrepancy with the Blessing of the Worthy Legendary Gem. At a certain rank, the gem's description changed from "maximum life" to "current life" verbiage, leaving players reasonably confused on which of the two descriptions was intended.
I'm here to tell you that was have patched this bug and will be pushing through the following text update for the Blessing of the Worthy Legendary Gem once our next Content Update goes live. This information will also be mentioned in our upcoming Content Update blog.
Blessing of the Worthy
- The Rank one and two description text for the Blessing of the Worthy Legendary Gem has been updated to correctly reflect the existing functionality of the unleashed retribution damage effect scaling off current life at all ranks. This is a text correction only and has no bearing on the functionality of the gem.
Thank you everyone for your patience as we crafted a solution to this problem.
After_Ad_1583Hello SinfulScribe,
Good day! I have recently transferred my character to another server. I am allied immortal on my previous server before transferring. I did the requirements before transferring which is leaving the warband and clan. Now, I have this issue in the new server I transferred which is I cant join to shadows after completing the shadow mettle quest, nothing happens. I tried also to be invited on being Immortal on the new server I transferred but still I can’t able to join. Why is that? PLEASE HELPPPPP US!
Many of us transferees who are immortals from previous server experiencing this issue. Thank you and hoping for your immediate response and action on this because we are losing ton of exp rewards and clan buffs.
For your reference please see bug report post https://us.forums.blizzard.com/en/blizzard/t/adventurer-forever-mobile-player/35867/9
FuenteHey After,
We pushed through a bug fix for this issue today. If you are still experiencing this issue, I recommend making a bug request here.