[BUG] broken YOM on DC

[snarez]

On DragonCat messages in Ye Olde Mail generated by system display a php warning that call to sprintf() has too few arguments, and call stack. It is shown twice.

Messages from other players are OK.

[blarg]

Thanks for the note, we'll take a look. If you haven't already, please petition it with the Report-to-Admin button from the YOM.

We've been working on a bunch of little updates/fixes over the last few weeks, so it might be a side effect of something we've changed.

[snarez]

Already petitioned it and it works now; that was some quick reacting to problems... I played a certain paid MMORPG where it took days for things to be sorted out

[RichPlaystation]

Originally Posted by snarez

Already petitioned it and it works now; that was some quick reacting to problems... I played a certain paid MMORPG where it took days for things to be sorted out

Which probably had 1000's or 100's of 1000's of active players, which is why it probably took days, correct? If it was something HUGE like World of Warcraft anyway.

[snarez]

I was talking about WoW, actually... Don't get me wrong, I understand it's a huge game with massive number of players (it is a MMO after all :P ), and I respect Blizzard more than any other game making company, but I still fail to understand how they could allow themselves to implement one buggy patch after another... The Ahn'Qiraj patch (1.9?) made the game absolutely unplayable for me for a week, and then in order to make it work I had to install OLDER drivers. It's all very funny now, considering that the theme of patch was invasion of huge bugs, but it wasn't that funny when I was paying for game.

Anyway, what I wanted to say is not that WoW is bad, but that LotGD and the whole team are absolutely great !

[Valancy]

buggy patches happen to the best of us. the software company that i work for ends up installing them sometimes too. the thing is, you beta test the patch on 6-8 servers, and things work fine for most of them, and problems are resolved and everything seems to be working fine, and then you do a general release and suddenly 15 unexpected things blow up at other servers.