Nostalrius Begins - Quality wow vanilla realm (1.12)

Your client locally stores data about quests, game objects, items, NPCs and more. So when something is called by the client it will use your local copy of data first before getting new data from the server. If you have custom data or broken things it might be because you brought it with you from another server so it sent broken/improper data instead of using clean fresh data from the server.

It is important on Nostalrius as the items are currently in a pre-nerf state that you regularly clear your cache to ensure all data used by your client is current data from the server.

Here is a BAT file for you to use to clear your cache and launch the game every time you play. To create a BAT file, simply create a new text document in Notepad or TextEdit and save the file with a '.bat' extension, and change the filetype from “.txt” to “all files”. I saved mine as 'Game_Launch.bat'. Just place the file in your root WoW Folder:

Code: Select all

@echo off
rd /s /Q "WDB"
start WoW.exe
exit

Thank you, working nice

In case someone else has problems with wow client freezing when entering world (after cleaning WDB), disable addons that make heavy use of WDB cache (and thus will generate many API requests if cache is empty).

Typical examples are quest tracking addons, like Enhanced Quest Log or Questie, that will try to pull quest objectives and might hang your client.
If you want to use them, disable them when logging in (and enable them using addon panel like MCP + /reload) or don't add too many quests to quest tracker. In theory it's not needed to clean WDB cache all the time, only when there are server-side changes to quest objectives / items / objects.

zerf wrote:In case someone else has problems with wow client freezing when entering world (after cleaning WDB), disable addons that make heavy use of WDB cache (and thus will generate many API requests if cache is empty).

Typical examples are quest tracking addons, like Enhanced Quest Log or Questie, that will try to pull quest objectives and might hang your client.
If you want to use them, disable them when logging in (and enable them using addon panel like MCP + /reload) or don't add too many quests to quest tracker. In theory it's not needed to clean WDB cache all the time, only when there are server-side changes to quest objectives / items / objects.

Speaking of this, we're actually working on something in questie right now to combat the first-login lag after deleting WDB.

Is this in your real WoW folder or the one associated with the private server version?

Bonjourno,

I have a slight problem, namely that after deleting my WDB and WTF folders in my WoW classic folder (downloaded the game via the nostalrius client), they both don't reappear after logging in.
Still, my items haven't updated yet, where I still see the old versions all others already see the newer stats.

Thanks in advance

merijnvdb wrote:Bonjourno,

I have a slight problem, namely that after deleting my WDB and WTF folders in my WoW classic folder (downloaded the game via the nostalrius client), they both don't reappear after logging in.
Still, my items haven't updated yet, where I still see the old versions all others already see the newer stats.

Thanks in advance

I"m actually experiencing the same exact thing, I deleted both the WDB and WTF folders and followed the advice the OP said but still my gear won't update with the stats. I even deleted atlas loot just incase, still no dice. Anyone have any advice that can help with this?

I"m actually experiencing the same exact thing, I deleted both the WDB and WTF folders and followed the advice the OP said but still my gear won't update with the stats. I even deleted atlas loot just incase, still no dice. Anyone have any advice that can help with this?

I too have problems with this. Any help on the issue?

Bumpiewumpie, seem to be enough peeps with this problem

If deleting your WDB folder isn't working and you're using Windows 8 (or Windows 7 without admin status) try moving your entire wow folder to your desktop first. It's likely not being removed because of admin rights issues in Windows.