SoggyShorts
Well-Known Member
@Enevhar Aldarion you should have taken me up on that 5 KP bet...
-
Dear forum reader,
To actively participate on the forum by joining discussions or starting your own threads or topics, you need a game account and to REGISTER HERE!
Fixed [35311] Fellowship adventure marker is incorrect
- Thread starter maxiqbert
- Start date
maxiqbert
Well-Known Member
I'm not sure yet that the bug will be corrected. After all they won't have beta to test it.
Lelanya
Well-Known Member
So
The penny hasn't dropped? If live isn't getting the buggy check and it hasn't been fixed before this one winds up that means...
We get another FA!
filiander
Active Member
I am really confused.
It is the same FA as the last one. Nothing has changed, only the bug. Why did they implement a bug in a part of the game, that had been played before?
And more confusing is, that they cant fix that bug. They had 2 updates.
The first made things worse, because the obly thing that happened was the killing of the most important part of the FA, the chat.
The second, what did the second?
It is the same FA as the last one. Nothing has changed, only the bug. Why did they implement a bug in a part of the game, that had been played before?
And more confusing is, that they cant fix that bug. They had 2 updates.
The first made things worse, because the obly thing that happened was the killing of the most important part of the FA, the chat.
The second, what did the second?
Quercus
Member
The problem was... the marker was not working correctly! Yes, there is always a problem with this marker in the browser version of the game. The fact is that there were two markers: one of them (gray "!") indicated that the badge was partially assembled, the second (green) indicated that the badge could be collected. And if at the same time one badge was collected completely, and the second - partially, we can see only "!" and it is not clear that something is already ready.
It looks like the developers have removed this gray "!" and that was a good idea. But at the same time something was messed up in the code and the marker began to behave inappropriately.
Well, why with each fix there is no fix, and new bugs are added - we can only guess
