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

12-15-2008, 02:06 AM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
Issues with setting zone points
Is there some limitation for setting new zone points--or adjusting existing ones--in certain zones? I am trying to set a new zone point in West Commons (using the zone_points table) and it is not recognizing it no matter what I do. I have set a zone point from a custom zone into West Commons, and it works fine; but I can't get the converse to work (WC to the custom zone). Just for some background, I have successfully worked this same plan between West Karana (qey2hh1) and the same custom zone (though at a different zin and zout in that zone). But for some reason, it's not working in West Commons. Any thoughts?
|

12-21-2008, 07:35 PM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
I'm bumping this because this is really baffling me. Specifically, I'm trying to change the target zone when zoning from commons (west commons) to kithicor forest. I have been unsuccessful in each attempt to change the target zone ID from the commons zone (using zone_points table). So, I renamed all "commons" zone entries in the zone points table to "x-commons." In theory, this should remove all the zones points in commons. Yet, after closing everything down and restarting, I zoned into commons and ran to the kithicor zone line, and it still tried to zone into kithicor (it ended up being an endless loop since it could not find it).
My question is, if the zone points table does not govern this zone point, what exactly does?
|

12-21-2008, 07:56 PM
|
Demi-God
|
|
Join Date: May 2007
Posts: 1,032
|
|
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
|

12-21-2008, 11:11 PM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
Thanks; good to know. So in this case it appears I need to create a zone line that falls before the hard-coded zoneline?
|

12-22-2008, 12:52 AM
|
 |
Dragon
|
|
Join Date: Nov 2008
Location: GA
Posts: 904
|
|
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).
|
 |
|
 |

12-22-2008, 01:32 AM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
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.
|
 |
|
 |

12-22-2008, 01:59 AM
|
Demi-God
|
|
Join Date: May 2007
Posts: 1,032
|
|
"
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
|

12-22-2008, 10:46 PM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
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.
|
 |
|
 |

12-26-2008, 05:20 AM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
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?
|
 |
|
 |
 |
|
 |

01-04-2009, 04:54 PM
|
Demi-God
|
|
Join Date: May 2007
Posts: 1,032
|
|
there are few zone lines which use VERY BROAD zoning line.
for exmaple zoning from West to east COmmons- you prabobly noticed that there are prety mcuh unlimited number of places you can zone from and to betwin these 2 zones.
You can zone by the orc camp, or by the road or by the south wall- etc BUT you arive in the other commosn EXCATLY where you zoned out in the other commons. - in other words the client somehow KNOWS your coordinates where you zoned out and puts them over to naother zone where you zonign in.
SAME thing happenigng betwen West and North Karana - the client need to keep some sort of a special track to see that if zoned by the road or nexr the river - and then put you by the road or by the river or any other of million points - real coordinates transisition i call it.
Same thing when zoning from North Qeynos to Qeynos Hills
I am prety sure those specific zone lines cannot be altered neither or at least won't be a trivial thing to do. I decided myself NOT to mess with them.
HOWEVER I have succesefuly made it than for exmaple you can zone from Unrest to Felwithe B, on StromHeaven server you can also see how you can zone from CrushBone to nexus - that is done as I mentioend with altering TARGET zone/coordinates
so try to alter zoning with something what naturaly has NARROW passage.
For starters connect Crushbone to Unrest for exmaple =)
|
 |
|
 |

01-04-2009, 09:27 PM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
Yeah, I figured out the broad zone lines are going to be near impossible to change. And I have since my last post successfully changed quite a few narrow zonelines. I have also learned to leave the origin zone points alone and just change the target zone points in any given row. However, there are some target zone points that still do not respond no matter what (e.g., the zoneline from Eastkarana to Beholder, narrow zone points both, will not let me change the target from Beholder to something else without getting caught in an endless loop to Beholder). For those cases I have set up an invisible NPC that catches players entering the proximity and zones them to the right target zone via quest::movepc(zoneid,x,y,z) just before they reach the zoneline.
|

01-04-2009, 11:37 PM
|
Demi-God
|
|
Join Date: May 2007
Posts: 1,032
|
|
dang I had plans for that zone point myself
thanks for posting this
|

01-05-2009, 12:29 AM
|
Hill Giant
|
|
Join Date: May 2008
Location: Colorado
Posts: 238
|
|
The zoneline from West Commons to Kithicor gives me similar grief when I try to change the target to qey2hh1 (the zone point is the tunnel between qeynos hills and West Karana--both zonelines are "tunnel" zonepoints, so it shouldn't be an issue, but it is). It's not a pervasive problem (I've only encountered two or three examples of it), but it there. You may get a different result when you try it.
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -4. The time now is 05:28 AM.
|
|
 |
|
 |
|
|
|
 |
|
 |
|
 |