Another week of Gallagio Loyalty Rewards Club Rep stuck 1 at 1lvl lower than the rest with no catch-up option

Since week 1, I’ve been stuck 1 level of rep behind everyone else when it comes to Gallagio Loyalty Rewards Club reputation even though I’ve been full clearing heroic/normal and a few mythic bosses. Now on week 4, I’m sitting at lvl4 0/2500 and can’t gain anymore rep from boss kills, while all my guildies/friends are at lvl5.

I’ve seen similar posts last week when the 3% buff was attainable. And that poster even went as far as to try to correlate a cause from all the users with this bug, which seems to match my situation: majority of the users, if not all, were summoned to raid before doing the story in week 1 and the theory is that their rep started at lvl 0, while those with story started at lvl1, hence the forever 1lvl behind. Not sure how true the lvl0 part is, but i know for a fact that I’ve been 1level behind the rest for a few weeks now. And, unfortunately, this missed level never gets made up when yo finish the story (as I did that already). So now it seems that those of us who are stuck with this bug will likely be in a similar situation of having to wait an extra week for every player power buff week, which is ridiculous.

I wish that we would at least get an acknowledgement that Blizzard is even aware of this issue, let alone when they plan to fix it. Very frustrating.

1 Like

There are at least a few threads about this but I want to bring additional attention to this since I have had the problem with the loyalty renown being stuck one level behind each week as well.

In my case it ends up exactly 1 point off, so 2499/2500 taunting me each week that there’s some rounding error or something preventing me from reaching the appropriate level each week.

Mostly it’s not a big deal, but since the stacking damage buff is attached to the renown track, I’m infuriatingly stuck with a significant disadvantage for one week when those come up on the track until I’m able to progress to the next week.

No amount of relogging or anything fixes the issue, and it’s been happening since at least week 2 of the raid being out, so multiple weeks now.