Oh, this is just too much.
Our script currently collects all the quests returned by the list displayed in the Completed tab of the Quest book, or rather by the underlying server request. All of them, I verified it works well. I am now affected by this bug too, so I took the courtesy of counting the amount of quests returned by the game server. It was 1000. Whoa, what a nice number, right? Then I counted the amount of quests imported by two players affected by the issue (one of them you, Abydos). 1000 in both cases. Quite a coincidence now. So then I actually counted the imported quests for every character imported today and took the courtesy of creating a scatter plot:
[SPOIL]
[/SPOIL]
Notice the
tiny bump of the character count near 1000 completed quests? That's more than 50% of imported characters. 50% of characters have exactly 1000 completed quests? Yeah, right.
So apparently, instead of actually fixing the bug that caused a server error for players with huge amounts of completed quests, InnoGames programmers simply limited the amount of displayed quests to 1000 to sweep the actual bug under the carpet. I know laziness is the driving force of every good programmer (including myself, I dare to say), but
this lazy? Common, InnoGames, you can buy better programmers than that.
There are also some players who have more than 1000 quests displayed in the quest book. This could either be because this
"fix" may not yet be deployed everywhere, or maybe it doesn't apply to all players for some reason. In case this is just a quick fix to make the quest book partially work while fixing the underlying issue, I still think it is a very poor decision (as this limit made the feature useless for even more players than affected by the original issue).
Fun fact... or guess, rather: Due to another careless bug recently introduced to public beta, I found their coders really like the number 1000. Apparently, you can only do a repeatable quest a thousand times, then it just disappears. Yes, I actually did a repeatable quest 1000 times to find out.
// Just to be clear, this game bug is the sole reason why TW-DB currently displays some of your quests as not completed.