Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::Windows Servers

Support::Windows Servers Support forum for Windows EQEMu users.

Reply
 
Thread Tools Display Modes
  #1  
Old 12-21-2008, 07:56 PM
ChaosSlayer
Demi-God
 
Join Date: May 2007
Posts: 1,032
Default

i want to point out that "zoning out" points or "Exits" - where you "zone out" from any given zone are HARD CODED into Client. - they cannot be changed.

the "zone to" points (where you appear wafter you zone) are writen in DB and can be altered at will

another thing you have to watch for are overlapign "zone in" and zone outs. For exmaple your problem with Kitihor could be that you zoning in rigth in front the zone out point, you char steps on in and gets zoned back where you came from, and from that zone he gets zoned back in Kitihor and so on. This problem also existed in Vex Thale where zone in and zone out overlapped each other
Reply With Quote
  #2  
Old 12-21-2008, 11:11 PM
Neiv
Hill Giant
 
Join Date: May 2008
Location: Colorado
Posts: 238
Default

Thanks; good to know. So in this case it appears I need to create a zone line that falls before the hard-coded zoneline?
Reply With Quote
  #3  
Old 12-22-2008, 12:52 AM
chrsschb's Avatar
chrsschb
Dragon
 
Join Date: Nov 2008
Location: GA
Posts: 907
Default

There are three areas you need to edit.

In zone_points.sql find Target_Y, Target_X, Target_Z, and Target_Heading and edit them for both the destination and the origin zones.

In zones.sql make sure Safe_X, Safe_Y, and Safe_Z are good spots (generally near a zone line).
Reply With Quote
  #4  
Old 12-22-2008, 01:32 AM
Neiv
Hill Giant
 
Join Date: May 2008
Location: Colorado
Posts: 238
Default

Quote:
There are three areas you need to edit. In zone_points.sql find Target_Y, Target_X, Target_Z, and Target_Heading and edit them for both the destination and the origin zones. In zones.sql make sure Safe_X, Safe_Y, and Safe_Z are good spots (generally near a zone line).
All of these are set correctly. The latest thing I have done is attempt to set a zoneline before the hard-coded zoneline. The zoneline I have set is simply ignored. Here is the entry in the zone_points table:

40,commons,1,910,4114,-47.7,0,41,27,2.6,166,0,12,0

where:
40 = zone_point ID
commons = current zone
1 = zone_point number for that zone (out of 4)
910 = Y
4114 = X
-47.7 = Z
0 = heading
41 = target Y
27 = target X
2.6 = target Z
166 = target heading
0 = zone instance
12 = target zone ID (qey2hh1 = west karana)
0 = buffer

If you zone into commons and #goto the coords above, you'll be placed in the corridor leading to kithicor, but not quite at the hard-coded zoneline. Having this set the way I have it in the db should, by all rights, zone me into the corridor of west karana. Except it doesn't. Instead, the zoneline is simply ignored, and I can walk right through it. It makes no sense to me.
Reply With Quote
  #5  
Old 12-22-2008, 01:59 AM
ChaosSlayer
Demi-God
 
Join Date: May 2007
Posts: 1,032
Default

"
40 = zone_point ID
commons = current zone
1 = zone_point number for that zone (out of 4)
910 = Y
4114 = X
-47.7 = Z
"

this is the hard coded part - you should NEVER change these value sin Db cuase they correspand to hard coded values in the client. don't even touch them (if you ever did- get back the original values)

ONLY alter the "target" coordinates.

So if you want to zone from WC to Kithihor- you walking over the "zone out" points. That points is hard coded, if Db entriy for that point is missing - your zonnign will be screwed up - the client will STILL try to zone you SOMEWHERE - but if you messed with those values (as i showed above) - the values in Db will not match with with client hard coding and you will enter into endless zone-loop


now for "target" values- you can put anything you want - so it is posible to have WC zone line zone you to qeynos, as long as you do NOT touch the zone line itself
Reply With Quote
  #6  
Old 12-22-2008, 10:46 PM
Neiv
Hill Giant
 
Join Date: May 2008
Location: Colorado
Posts: 238
Default

Hmm . . .doh!

Would someone be so kind as to sort their zone_points table by zone name and copy and paste the "commons" entries here (there should be three or four of them)? And while you're at is, I would probably benefit from the entries of eastkarana, qey2hh1, southkarana, and northkarana. Sorry for the trouble.
Reply With Quote
  #7  
Old 12-26-2008, 05:20 AM
Neiv
Hill Giant
 
Join Date: May 2008
Location: Colorado
Posts: 238
Default

Quote:
ONLY alter the "target" coordinates.

So if you want to zone from WC to Kithihor- you walking over the "zone out" points. That points is hard coded, if Db entriy for that point is missing - your zonnign will be screwed up - the client will STILL try to zone you SOMEWHERE - but if you messed with those values (as i showed above) - the values in Db will not match with with client hard coding and you will enter into endless zone-loop

now for "target" values- you can put anything you want - so it is posible to have WC zone line zone you to qeynos, as long as you do NOT touch the zone line itself
Okay, I'm still having no luck with this. I tried using this method to zone from the eastern zoneline of qey2hh1 (number 1 zone for qey2hh1 in the zone_points table) to commons (target_zone_id 21), and entering that zoneline stills takes me to North Karana. This is VERY frustrating because it disallows me from piecing my map together. Any suggestions?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 02:05 PM.


 

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.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3