Ok I took the time to measure what I am going to call the zone line that is hard coded into the client for vexthal.
This zone-line begins at:
x = -1639.5
y = 372.8
z = -40.4
It ends at:
x = -1419.1
y = 343.0
z = -40.4
Based on this data, the best solution I came up with is to take the advice to move the zone-in point further into the zone, past this hard coded zone-line. I propose doing so with the following queries, which are based upon the PEQ Luclin Release database.
Code:
update zone set safe_x = -1400, safe_y = 343, safe_z = -40.4 where short_name = 'vexthal';
update zone_points set target_y = 343, target_x = -1400, target_z = -40.4, target_heading = 64.4 where id = 785;
update doors set dest_x = -1400, dest_y = 343, dest_z = -40.4, dest_heading = 64.4 where id = 8917;
insert into zone_points (zone, number, target_x, target_y, target_z, target_heading, target_zone_id) VALUES ('vexthal', 1, -741, -1451, 12, 253, 176);
Your mileage may vary on other world databases...
Thank you to all of you who responded to this thread and shared your knowledge with me. I couldn't have solved this problem as nicely as I did without your input.
Threaded Mode
