View Single Post
  #3  
Old 03-14-2005, 10:25 AM
Magick
Sarnak
 
Join Date: Feb 2003
Posts: 73
Default

Ok.. I'm a little rusty so feel free to correct me. And also I can only potentially help on the first issue (Zoning).

It would help if you pasted copies of what your zone.exe(s) say when you try to zone. The reason being is it sounds like one of two things:

1. No zone points are in the database for that area --OR--
2. Your zones are autobooting and that's why you aren't zoning. (Typically you'd get a "this zone is unavailable" and then it sends you back to the safepoint of where you were.)


Ways to check, again off the top of my head:

1. Open your db and look at the zone_points table and scan the zone field in that table for the zone your character is in. Does it list zone points? Where is the target_zone for each? (just looked in my stock/default db and you apparently can't zone from EC to WC so there is quite a bit missing).

If everything looks ok there, I'd test out zone.exe by force booting the zone you're in and the adjacent zone and attempting to zone. The messages in the command window (if it doesn't work) should give you a hint as to what the problem might be.

To force load change your boot5zones.bat to something like:

Quote:
REM: ****Read this first!!!****

REM: This file requires your real IP in the place of "EXTERNAL_IP_HERE" when you are connecting
REM: To the EQEmu Loginserver.

REM: When you are using minilogin, Replace all IP Addresses to say 127.0.0.1

REM: If you still get errors try using localhost instead of 127.0.0.1

REM:--------------Start-----------------------
@echo off

if NOT exist spells_us.txt goto NOSPELL

start zone ecommons 127.0.0.1 8780 127.0.0.1
start zone commons 127.0.0.1 8781 127.0.0.1
exit
cls

:NOSPELL
echo You did not copy the spells_en.txt from your everquest directory to this one. Please do so or zones will crash on startup.
PAUSE

REM:---------------END------------------------
..and save it as zonetest.bat

Move your char to one of those zone via the database, start the server, log in, and try to zone. Both zones ARE up and running so if you have a problem then it might help narrow down a fix. NOTE: I would not use those two examples since my db did not have a zone point there. Just change the zone shortname to whatever zones you want to boot.
Reply With Quote