Infinite Zoning Loop

[WildcardX]

I ran the following queries against my world database and I got mixed, but promising results.

update zone set safe_x = -1589.6, safe_y = 371.3, safe_z = -40.4, canbind = 0 where short_name = 'vexthal';
update zone_points set target_y = 371.3, target_x = -1589.6, target_z = -40.4, target_heading = 64.9 where id = 785;

After a quick reboot of the server, I found I can #zone vexthal and zone in to the updated coordinates and everything is great.. no problems.

But now here is where it gets.. odd. I zoned out to umbral plains and then zoned back into vexthal like a player would, except I didn't zone to the coordinates specified in the query above. Instead it lands me at the original zone in coordinates that were in the database before I updated it. And, of course, then I run into that same infinite zone loop.

I'll test this more tomorrow.

[bufferofnewbies]

check doors table
field id:
# 8917

someone might have set the zone as a door also, and it could be triggering before the zoneline does.

[WildcardX]

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.

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.

[bufferofnewbies]

Good show. I'm glad you got it to working.
Now to steal your code cause I'm really lazy...

mwhaha

[WildcardX]

I moved this thread because it's clear to me now that this bug isn't a bug in the EQEmu server code, but rather just a mechanism behavior of the EQ client.

[Angelox]

Just as a "quick solution" here's what i've done to solve this tell someone can figure it out -
I had this problem at one of the oow zonelines, I think it was bloodfields to draniksscar. I placed a "zoner" npc before this happens.
Just a tiny, invisible (race: invisible man), untargetable, and hidden npc, that uses quest::movepc automaticaly as you approach the zone line.
Probably sounds very "assenine", but works very well, and you'd never know it was there unless you were the one that put it there.

[John Adams]

Silly me. I thought that *was* the solution for adding zone lines.