[PARTLY-SOLVED] Client tries to patch despite account name

[Ascathos]

So, I've got an analysis concerning trying to log onto a 3.3.5a server and he suddenly wanting to patch. Somehow, he tries to patch if you enter an email. That is fine and reasonable. However, some clients try to patch when entering a account name. After some  tests, I found out that he somehow always refers to the email whenever the WTF-folder is deleted, indicating that it is saving that function somewhere. Setting the patchlist to something local, set realmlist differently, etc. doesn't work - we found that out already.

So, to narrowing it down;

• Set patchlist, realmlist and the "saved" accountname in the config.wtf to an actual accountname, but it still wants to patch
• Found out that it sets the email on default, somehow saving it somewhere
• Checked the registry for some kind of reference, like an update entry or similar.

Anyone any pointers I might be able to follow ?

[stoneharry]

So, I've got an analysis concerning trying to log onto a 3.3.5a server and he suddenly wanting to patch. Somehow, he tries to patch if you enter an email. That is fine and reasonable. However, some clients try to patch when entering a account name. After some  tests, I found out that he somehow always refers to the email whenever the WTF-folder is deleted, indicating that it is saving that function somewhere. Setting the patchlist to something local, set realmlist differently, etc. doesn't work - we found that out already.

So, to narrowing it down;

• Set patchlist, realmlist and the "saved" accountname in the config.wtf to an actual accountname, but it still wants to patch
• Found out that it sets the email on default, somehow saving it somewhere
• Checked the registry for some kind of reference, like an update entry or similar.

Anyone any pointers I might be able to follow ?

Try moving the 'Battle.net.dll' out of your WoW folder, and delete 'Passwords.dll' if it exists in there.

The battle net DLL contains information used when connecting using the Battle Net 2 protocol (emails). Information such as realmlistbn (hardcoded into the DLL).

The other DLL is one of many modules that are streamed to clients through the new protocol, and will also contain information that could be forcing you to connect to retail.

Also try starting WoW.exe with the -console argument. This allows you to open the console with the tidal key ( ` ). When you login, it will put helpful information in there, such as the realmlist it is connecting to and any errors causing it to default to that.

[Ascathos]

Thanks for the pointers. Headsup, you require an American Keyboard setting (google it.) and press ^. May or may not work with different keys for different keyboards anyway.