Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

a little tips may be

Initiate Mage
Joined
May 10, 2006
Messages
11
Reaction score
0
Here is my problems : My server is running smooth on everything except the death bug on resurrect. This is weird part, when my char die, i can resurrect him on my desktop; however on my wireless desktop i cant resurrect my char. After that everyone on the server disconnected. Was this something i need to modify or just a core or db problems. I have try many new core and db still the bug still there.
 
Initiate Mage
Joined
Jan 7, 2007
Messages
75
Reaction score
0
I read till now quite a lot of post about death bug. Also i read a lot of post about this pretending that such bug cannot exist, but in reality it exist. :(
Tryed till now different cores some mayde by me some made by others[albatron, biglad, and others] and still appeared.
Also tr i've tryed many times to drop the DB and star all over again but thsi bug remains.
So i can assured any1 that this bug exist. Of course could be people that never meet with him but still exist.
 
Initiate Mage
Joined
May 10, 2006
Messages
11
Reaction score
0
well i dont know why most devs stated this bug isnt real whereas it was real. I even reinstalled my windows and such trying to fix this bug, but i have no success. The strange thing is that some player on my server has this bug and some dont. I even have it myself but only on my wireless laptop. Whenever i use my regular pc i can log in the deathbug char and easily resurrect with no problem. So i just dont know what is wrong hopefully some expert kindly devs will show me the light :)
 
Initiate Mage
Joined
Feb 18, 2007
Messages
10
Reaction score
0
If it doesn't happen to everyone, then it might be a client version problem. Remeber that mangos runs on wow version 1.12.1 AND 1.12.2. Maybe one of these has the problem, and the other one doesn't.
 
Back
Top