Support::General SupportPost all topics here having to do with errors while trying to connect to an EQEMu server but not about the setup/running of the Server itself.
I used the above fix and it solved the melee out of range but spells still say I cannot see my target. I used #summon on a mob and tried casting and still get the error.
I used the above fix and it solved the melee out of range but spells still say I cannot see my target. I used #summon on a mob and tried casting and still get the error.
make sure you have download the map files with out them in your eqemu folder you will not have line of sight. Therefor causeing the you can not see the target.
Aargh!! I think I need this fix. Everything seems to work now. Except my position(Server)remains at zonepoint. I also need to make the correct DB as mine is missing the correct Items table.
Well..On to the fixing DB problems. I hope I can get the rest soon.
I did compile a new zoneperl.exe last night, but it has another problem and I haven't had time to look into it, yet. It kicks out a run-time error from the perl quests and crashes the zoneperl.exe that generated it.
I was just doing a little reading of ActiveState perl's README and I see in there a blurb about Perl 5.8 not being compatible with earlier releases of Perl and "You have to recompile your XS modules." I believe the quest subsystem uses these XS modules, right? So either I need to recompile those or I need to back down to a previous release of ActiveState Perl? Like 5.6? I wonder if thats not what was tossing that runtime exception in my updated zoneperl.exe last night... My server does have ActiveState Perl 5.8 installed and I think thats a relatively recent release of ActiveState Perl. Anyone else running ActiveState Perl 5.8? Anyone have this working ok with ActiveState Perl 5.6?
for my 6.0 and 6.1 i used ActiveState Perl 5.8 and had no issues. for 6.2 i dunno i don't have a working zoneperl for 6.2 nor do i have perl installed yet from having to do a reformat.
Thanks..That worked. At first world.exe was crashing when I try to zone. So I put the original world.exe back in and now it seems to work a treat!
I also am using a new database so now the only errors I get are the opcode thingies.
Well i have been playing around and well i found another issue. The world.exe in the EQEMUfix zip that mikeusc did has an issue with it (for me at least). If you try to use the command #zone you get a loving M$ error window. when i am in BB and type #zone firiona the zone will bootup all looks normal till the error window pops up saying world.exe has encounterd an error and needs to be closed. Fix for was i went back to the original world.exe from the ninaries and i can sit here and bounce from BB to firiona via the #zone command.
not sure anyone else encountered this or not seems some files work better on other pc's and some pc's the files hate them heh. so if you encounter this you can replace the fixed world.exe with the original one or worlddebug.exe from binaries.
/me runs and hides from the mob for finding another bug
Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.