As a protective measure we have now throttled the NPC. At one time we had someone abuse this NPC to create thousands of items at once, causing the Blackrock worldserver to run out of item GUIDs. Once, on Blackrock we have a вЂpick a specвЂ™ NPC which will instantly set you up with the gear you need to play PvP at level 80, thus creating many items at once. Has this ever happened outside of this Frostmourne launch? Prior to those changes when a new character was created the starting items were also created instantly, because of this the item guid usage was much more spread out thus causing us to not exceed the available pool of item GUIDs. We will temporarily allocate a significantly larger item GUID pool that is reserved by the worldservers.ДЄfter Frostmourne S1 launched we moved all character list functionality to our realmserver as it is much better suited for that data. What will we do next year to prevent this from happening? We did not expect the number of items to be created within a few server ticks to exceed the available item guid pool size. This means thousands of items were being created at the same point in time causing the worldserver to run out of available item GUIDs and thus deliberately crashing itself in order to ensure data integrity. Every fresh character starts with about 5-6 items, depending on the class/race. All the starting items are being created at the first log-in. Due to character creation being handled on our realmserver, when a new character is created there are no items yet. The second factor was the obvious MASSIVE influx of fresh character logins. However, during the first minute of Frostmourne, the CPU and bandwidth of the servers were very saturated, causing the request of a new item GUID pool to be delayed, this is the first factor leading to the crash. Normally this is a very fast process, within milliseconds. When the pool is almost depleted a new GUID pool is requested. When a worldservers first starts up, it requests a pool of unused item GUIDs from the realmserver, new items will be assigned a GUID from this pool. Items are created on the worldserver, but since players are able to connect to multiple worldservers the generation of new GUIDs has to come from the realmserver, which is the central point all relevant worldservers connect to. These numbers have to be globally unique, having two items with the same GUID would be a large problem. This number is used to save, load and manipulate this item, both on the server and on the client.

When an item is created, a new GUID (unique number) is assigned to that item. To explain what happened we first have to dive into how items are created and what happens internally. The real issue was the main worldserver crashing after about 60 seconds into the launch. This quickly went down however as soon as players spread out a little bit. There was a huge bandwidth spike initially, similar to what we experienced last year, causing noticeable lag in the first 3-4 minutes. The realm launched at April 15th at 16:00: In this devlog I will explain what went wrong in the first few minutes of Frostmourne S2 release and why. As a result, this year was much, much better but it still did not go as well as we wouldвЂ™ve liked. Yes, this is the appropriate forum, since this may be a wowhead issue.After last year's somewhat laggy initial hour of Frostmourne (As described in the devlog from June 1st 2020), we learned a lot and made various changes to help address those issues. I'm keeping a running list, as I'm going through Outland, and most are dailies, but some are not. Is this the appropriate thread to post these in? I know on the alliance side, i have the Loremaster of Eastern Kingdom and i still have tuns of quests to do that count. I'm sure you will find a quest that counts to replace this one. When it comes to the Loremaster, there are many quests possible to complete. Only option would be to Exclude the quest in the wowhead log and forget about it. You may be out of luck if you can not get it. Otherwise if the number '431' is not in that information, then you either have not done the quest or Blizzard does not have a record of it being completed for your character. If the number '431' is in the data, then it might be a Wowhead issue. Copy the information to Notepad or some word processor and search for the exact number '431'. It will display a box with a bunch of numbers in it. Have you verified that you can not do the quest again? Go take a look and find out. I have not done any Horde quests, so i do not know if it is repeatable. Is this a repeatable quest? If so, then it will not be marked as completed.

Completed quest tracker wow