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.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.
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.
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.
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..mfil normally contains build key. not sure what it does without. likely just retrieve current build key. does so on wod.
Holy cow those settings are dark!! and Milly..... what's your avatar from?
Wow you really put some time into that. I thank you. ^_^ Hm, however... I didn't change any of the original atmospheres, or the times at which certain places become night/day (best time for testing is 12am). I scaled everything on a gradient, to remain consistent. For a while the mod was meant to be like a custom day/night cycle, which would synchonrize all the sunrises and sunsets and probably would have taken care of most of your concerns, but I found it was too messy and I went OCD and deleted it. Also, I might add that some of the things you talked about may be because you're on 3.3.5. So as much as I'd like to follow up on all of your critique, it's really against the very foundation I built the mod on Which was to not modify any of the original settings by Blizzard, and just scale them all to the same hex color (121212).Now I'm looking into MoP. And unfortunately, LightIntBand.dbc doesn't exist anymore so I will have to redo the entire mod on there. (Although the new dbc setup makes it a lot simpler). But anyway I will have to consider putting a little more customization into the day/night cycles on there.
