ArcEMU-World Error?

[Neth'zul]

Hey guys i get this shitty error, +rep for anyone who helps me!

[Sounddead]

Don't use ArcEmu? :P

Hearthstone is mucho better

[Neth'zul]

lol thanks for the tip

[Vindicated]

@ Sounddead - So true.

@ Neth :O I could just tell you dis over MSN but 'tis the new patch

[Neth'zul]

New patch?! RAGE! lol thanks Vinidicted and Soundded!

[jamb92]

So wait, I don't understand what you folks mean by "new patch."

I am having this exact same problem with a 3.0.3 ArcEmu core rev 2003, this is 3.0.3, not a "new patch." Am I just confused or what do you guys mean?

This issue started happening for me earlier today without any changes or manipulation of my server and ArcEmu files. Yes, I know Blizzard released 3.0.8 today, but I do not understand how 3.0.8 coming out has anything to do with already-downloaded 3.0.3 cores not working anymore.

[jamb92]

Ahh, I figured it out. I guess what Vindicated meant by his brief explanation is that if you have a 3.0.3 build and someone connects who has upgraded to the new 3.0.8, this error will occur and the server will crash.

UNLESS you change your logon server config file to only allow max client build of 9183 (3.0.3).

I changed my config and the problem immediately stopped. ArcEmu by default has the max client build in the config to be 9999. So while it was set like that, any dumbass who upgraded to 3.0.8 already and tried to connect to the 3.0.3 realm caused the entire realm to crash with that endless loop of compile errors that Neth posted above.

[gangstagreen]

Ahh, I figured it out. I guess what Vindicated meant by his brief explanation is that if you have a 3.0.3 build and someone connects who has upgraded to the new 3.0.8, this error will occur and the server will crash.

UNLESS you change your logon server config file to only allow max client build of 9183 (3.0.3).

I changed my config and the problem immediately stopped. ArcEmu by default has the max client build in the config to be 9999. So while it was set like that, any dumbass who upgraded to 3.0.8 already and tried to connect to the 3.0.3 realm caused the entire realm to crash with that endless loop of compile errors that Neth posted above.

Very well explained. Someone should sticky that in a new thread. Rep is deserved

[cello1993]

I have the same problem but,
Sorry I didn't understand... or at least how to fix .
Is it because the new 3.0.8 patch? I have in logonserver.conf Client min=1 and Client max=9999 but still doesn't works. Isn't ArcEmu compatible with the new patch yet?

[jamb92]

Yes, to fix it, go into your ArcEmu-Logonserver config file and find the part where it lets you set the min and max client build version. I'm at a place where I can't remote to my server to copy/paste the config, but it looks something like this:

Min = 1
Max = 9999

Change that 9999 to 9183 until you have a core with 3.0.8 support. If you don't, anyone who connects to your realm who has updated their WoW to 3.0.8 will crash your 3.0.3 server.

My server has been public for a while so despite our news post people were trying to connect with 3.0.8 all day until we changed our config. This resulted in the server crashing every 5 minutes or so xD

[jamb92]

Isn't ArcEmu compatible with the new patch yet?

And no, it isn't until you have a 3.0.8 core. 3.0.8 changed quite a few things so it might even require some DB updates.

Seemed to be mostly talent and mechanic changes though. We'll see. Point is just because someone updated their WoW to 3.0.8 it doesn't mean your server is now running 3.0.8 until you update it. When you do update it, change the build max # again in the config to the newest #.

Hope that makes sense

[cello1993]

Yea jamb92 thx ^^ Very well explained =]
Hum I'm checking the ArcEmu changelog every minute xD
Seems to be that revision 2029 haves a possible fix for the 3.0.8 and I hope when they update the Keazain repacks it be "really" fixed ^^
Cuz my problem is that "I" upgraded to 3.0.8 version xD
Hehe ... but thx very much for the help

See you!