Forum > Resources and Tools

[RELEASE] Darker Nights 4.3.4 (+3.3.5) v1.3

<< < (13/24) > >>

Milly:

--- Quote from: "TheRealDavidTwo" ---
--- Quote from: "Milly" ---That error message pops up for a lot of reasons, but for me the only reason it ever seems to show up is when you used a custom patch and exe on the Windows version of World of Warcraft. It means your client is fucked, basically.

If you're going to be using mods on Cata then you're gonna want to get a mac version. It works exactly the same and doesn't get corrupted when patched. Though I'm not sure how or if that applies to you because you're not on 4.3.4.

Try removing the custom launcher and patch and seeing if you can get back into the game. If you can't, your client is broken, and I don't think you can fix it. Sorry if that's the case but it always happens with the windows version.
--- End quote ---

As I was the one with the error there as well; I can get into the game just fine with the retail .exe. But as soon as I try logging in with a custom patch enabled w/the patched EXE (as, again, seen here: https://i.imgur.com/6ogaojE.png), then yeah, all shit breaks loose.

The client is definitely not "broken", because if it was, I wouldn't be able to get into the game at all, especially with the retail .exe/unpatched exe.

EDIT --- And what do you mean by "Mac" version? Do you have a place where I can find such, if that ends up actually being the case? Because that's not making too much sense.
--- End quote ---
This is strange. Whenever the situation happens to me, the client entirely breaks. Even if I remove the patch, clear all caches, and use the retail wow.exe, it still gets the same error. I ran into this issue a lot before I got my Mac client. And you can find the download link here: http://www.mediafire.com/download/wlbpg ... PB.torrent

TheBuG:
Doesn't that have to do with the WoW.Mfil file?

I'm not sure, haven't done anything related to it for a while, but try creating an empty text file and rename it to WoW.Mfil and see if it works.

schlumpf:

--- Quote from: "TheBuG" ---I'm not sure, haven't done anything related to it for a while, but try creating an empty text file and rename it to WoW.Mfil and see if it works.
--- End quote ---

.mfil normally contains build key. not sure what it does without. likely just retrieve current build key. does so on wod.

TheBuG:

--- Quote from: "schlumpf" ---
--- Quote from: "TheBuG" ---I'm not sure, haven't done anything related to it for a while, but try creating an empty text file and rename it to WoW.Mfil and see if it works.
--- End quote ---

.mfil normally contains build key. not sure what it does without. likely just retrieve current build key. does so on wod.
--- End quote ---

I remember some private servers replacing the WoW.mfil with their own because this error would show up for some players (or so they claimed). I'm not sure if it works though.

Karis:
thank you for release.

Navigation

[0] Message Index

[#] Next page

[*] Previous page