WoWCenter.pl
wikass zabił Mythrax the Unraveler (Normal Uldir) po raz 2.     
kuturin zdobył 7th Legionnaire's Cuffs.     
Nikandra spełnił kryterium Loot 200,000 gold osiągnięcia Got My Mind On My Money.     
Tooly zdobył Fairweather Helm.     
Muattin zdobył osiągnięcie The Dirty Five.     
Yoozku zdobył Parrotfeather Cloak.     
Mlody89 zdobył Royal Apothecary Drape.     
Weakness zabił Dazar, The First King (Mythic King's Rest) po raz 6.     
liq spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Osiol spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Wuntu zabił Zek'voz, Herald of N'zoth (Heroic Uldir) po raz 1.     
Olsa zabił Vectis (Heroic Uldir) po raz 6.     
Sarenus spełnił kryterium osiągnięcia Saving for a Rainy Day.     
kajtasus zdobył osiągnięcie Come Sail Away.     
ossir spełnił kryterium osiągnięcia Saving for a Rainy Day.     
mcpablo spełnił kryterium Alliance players slain. osiągnięcia Frontline Slayer.     
Emmm zabił Taloc (Heroic Uldir) po raz 17.     
AsaGorth spełnił kryterium Big-Mouth Clam osiągnięcia The Oceanographer.     

The Elders not giving Gilneas/Bilgewater Rep

blizz -> wysłany:
"Reputation with the Horde increased by 83"

Bilgewater Cartel: 9/12000 Honored.

Hasn't move since I have done 9 elders.

I assume Gilneas has the same problem.
blizz -> wysłany:
Thanks for the reports! We've implemented a hotfix to correct this issue and ensure that Horde players receive reputation with Bilgewater Cartel when completing Lunar Festival coin quests.

The hotfix requires a realm restart, so everything should be resolved after tomorrow's scheduled realm maintenance: http://us.battle.net/wow/en/forum/topic/1921699337
blizz -> wysłany:
01/24/2011 2:47 PMPosted by Cikala
I've unfortunately already finished all the elders for the year, but I didn't receive one bit of Gilneas rep (the only main alliance faction that isn't exalted for me) the whole time, despite the constant 'you've gained rep with alliance' messages I got.



To my knowledge, Alliance coin quests are currently granting the proper amount of Gilneas reputation when completed. Let me talk with our designers, though, to see if there's a cap at which reputation from those quests is no longer provided. It's certainly possible, but I want to be certain before I say one way or another.

This seems to be a bit different than what was happening with the Horde coin quests, by the way. The issue there was that the quests weren't providing reputation with Bilgewater Cartel at all, regardless of a player's faction standing.
blizz -> wysłany:

I did notice the alliance toons were not granted rep as well. Yes I play both sides.



I'll be happy to double-check the information I have. It may take me some time, but I'll make sure your reports are brought to our designers' attention.
blizz -> wysłany:
I spoke with our designers a bit more about the Lunar Festival coin quests and what caps, if any, are placed on the reputation provided from them. At present, these quests should only provide reputation with Horde (Orgrimmar, Undercity, Darkspear, Thunder Bluff, Silvermoon City, Bilgewater Cartel) and Alliance (Stormwind, Ironforge, Gnomeregan, Darnassus, Exodar, Gilneas) reputations up to 5999/6000 Friendly. This is indeed intended, as many of you have guessed, but we absolutely appreciate the feedback provided in this thread -- both in relation to the Lunar Festival and the reputation cap itself.

For clarity, there was a separate issue that was preventing eligible Horde characters, regardless of their faction standing, from earning Bilgewater Cartel reputation when completing the Lunar Festival coin quests. Even if they were Neutral with Bilgewater, for example, they were not receiving the 75 reputation as intended. This has since been resolved with a hotfix and should be live on all realms.
blizz -> wysłany:
01/25/2011 6:21 PMPosted by Braille
They should. But they don't.
Today I got reputation with Thunderbluff at 7626/12000.
See my post #75 (page 4)...



We're actually already looking into Thunder Bluff and the point at which it caps (thanks in large part to your previous report), and I believe we'll be applying a hotfix shortly.