Jump to content
Sign in to follow this  
Egeus

[Q] Battle of Warsong Gulch (Marks of Honor)

Recommended Posts

After the recent BWL patch the quest in question cannot be turned in to NPC Horde Warbringer (as intended). This in turn causes Marks of Honor to stack up to 20 and more. As you know the excess of the marks goes directly into your inbox with the expiration time for each won Mark of Honor (just 1 or a stack of 3) being only 24 hours. This has been a concern to a lot of players since the rep/xp/gold that is rewarded for turning in these marks is one of the substantial reasons why people do the BGs (apart from fun and ardour ofc).

There's been no official statement so far (at least not one that I've seen) on this matter, could the staff please clarify? People say that it's going to get fixed, but the question is when? And also "people say" is not a very reliable source of info. Will this matter be addressed anytime soon and will the players be able to restore their expired Marks of Honor? Thanks for your consideration.

See attached below: 2 pages worth of Marks of Honor in my mailbox that I can't turn in with the expiration dates coming to an end.

6E5Nmv.jpg

b6OPVH.jpg

Share this post


Link to post
Share on other sites

There is an announcement of some sort on Discord

 

Akira - Today at 9:40 AM "@everyone The fixes for AV quests, BG marks and the R14 weapons will be applied on Elysium PvP this evening, please, stay patient!"

Share this post


Link to post
Share on other sites

Not fixed all horde warbringer gives me is the Invaders of alterac valley quest and I got 23 warsong mark of honor medallions that can not be turned in I'm bummed

Share this post


Link to post
Share on other sites

Spionida, how many time in last month you had report this bug?

Meanwhile its not a bug, its sabotage, these quests have worked recently. 

This bug have been around month, and really critical for players who want PvP progression.

Share this post


Link to post
Share on other sites

I have seen these bugs reported. I have seen that there have been some fixes. I have seen that they are not completely working. 

It's a private server, there will be/are bugs. If the debs/coders are not careful, a fix can create all sorts of other problems. It's far from as straightforward as may be imagined.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×