Help to get all Zones Working Perfect

[radcode]

Hi everyone.
Like many of you I've been playing around with different versions of EQEmu and different databases. You run this patch and that fix and they all seem to fix one thing and break the other. So many times I already deleted my database and started from scratch. Lately I've been on a mission to get all the zones to work properly so I made new database only with the zone related tables.

zone, zone_points and zonepoints_raw

My hope is to get all zone lines, coordinates and direction facing at zoning squared away. All other things like items, spawns and other crap can be customized based on specific preference. But as a base to having good server you need to have working zone points so that when your friend plays, he/she doesn't get warped under world or drops from sky and dies at the zone. After all the experimenting I think this is the way tables should be working.

1) table 'zone' defines short/long names safe coordinates which are x,y,z and probably would be nicer if they would be y,x,z to avoid confusion, since in-game they should coordinates as y,x,z

(often I've seen that after zoning I would end up at safe coords rather then one in zone_points table.)

2) table 'zone_points' I believe should be working as (zonename warping from), (zone line y,x,z ), (zonename warping to),(y,x,z,(face direction y,x)

3) table 'zonepoints_raw' I believe actual data that defines zone lines, borders e.t.c I am still not sure how to mess around with that since the data seems to be encrypted.

So I am hoping (with some help) to get these things straightened out and perhapse with couple people (who are willing ) to test all zones/ zonepoings and get all dafenitions for zoning put into a clean good database. Then we can do test and post it here and work on next part.

I am also hoping to get boats to work, though I realize that we'll probably need at least port zones running in real-time. Or so I think for the boats to work they way they do on real EQ server since they're running on schedule. If that can't be done without real-time each zone emulation then maybe get translocators working at the docks where the boats supposed to be so that each zone can be traveled to without the need to use #zone.

Thanks ahead of time for all the assistance.

[how can i post]

im pretty noob but can you tell me how am i supposed to make it work plz ? =)

[deeque]

sounds like a good idea

i find that it is very easy to find all that info while in game use the #loc ( not /loc) but #loc it tells exactly everything you need xyz and heading (direction facing) just have admin tool running and pluck in the info or open the zone files and change there


:lol:

[Trumpcard]

Good safe points for all zones would be a start..

I know several are messed up at the moment, Befallen is one..

Anyone know any zones that have bad safe points? If you get them too me, and good loc's , I'll update the db.sql that comes with the releases so they are correct out of the box.


A bad safe point usually demonstrates itself by crashing to desktop everytime logging into a zone. It can be other things also, but a few of the cases Ive seen have required a change to the safe point.
If you can compile a list of bad zones, I'll see about fixing them.

Thanks!

Great idea btw, I'll do whatever I can to help. I'd love to see zoning perfected. It's the basis of creating a good stable legit server if you ask me...

[radcode]

I guess I am still waiting for the question to be answered. Is the zone_points table the one where you put in coordinates of :
(zonename warping from), y,x,z,(zonename warping to),y,x,y,(direction facing y,x) If this is the format then I must have been doing something wrong. Because I was messing around with it and no matter how i put them it didn't seem to work. Whis is why I came here for clarification.
An example would be.
INSERT INTO zone_points VALUES (1,'qeynos',464,-440,351,'qeynos2',-155,-7,351,0,0);

Where is stands for; zone from 'qeynos' at (y,x,z)='464,-440,3.51' to 'qeynos2' at (y,x,z,keep y,keep x)= '-155,-7,3.51,0,0) where keep y and keep x would be face direction. In this case 0,0 Is this is the right format? If so, I am stumbled why it wouldn't make work. I especialy hate cases where you zone and you're facing to the zone line and by accident zone back into zone you just came from. Also I am assuming that you can put in coordinates for z as decimal value like '3.51' ? I am also presuming that zone in coordinates can be altered a bit, say to be right on the middle of the path rather then on a side like in case of zoning into North Qeynos from Q. Hills

[deeque]

ive been thinking about those tables as well and here is would i have been messing around with .. by altering the zone_points table a little bit by adding another colum called heading before the keepx and keep y not sure what they do either ..doesnt seem to be much of anything all the records for them all have been 0 in all the entries.


CREATE TABLE zone_points (
id int(11) NOT NULL auto_increment,
zone char(16) NOT NULL default '',
y float NOT NULL default '0',
x float NOT NULL default '0',
z float NOT NULL default '0',
target_zone char(16) NOT NULL default '',
target_y float NOT NULL default '0',
target_x float NOT NULL default '0',
target_z float NOT NULL default '0',
heading float NOT NULL default '0',
keep_x tinyint(1) NOT NULL default '0',
keep_y tinyint(1) NOT NULL default '0',
PRIMARY KEY (id)
) TYPE=MyISAM;

---

and also adding an extra number in into a new version of the zone_points data dump file where the heading of 45 would make the toon zone into those coords and facing the heading of 45 like this :


REPLACE INTO zone_points VALUES (1,'qeynos',464,-440,351,'qeynos2',-155,-7,351,45,0,0);

but they only thing is the admin tool doesnt load this extra colum and i tryed to use the #goto Y X Z H (H meaning Heading) Command along with the extra heading # to tell what direction to face. .but i guess the Emulator would need some extra coding or adding something to the goto command to recgognize that 4th variable.

by doing the #loc command it gives the x= ,y= ,z= , Heading=


this is just my idea of how to fix the facing the wrong way thing
also to update the file easily by using the REPLACE INTO command
until there is that perfect zone_points.sql file

[radcode]

I don't think adding extra columns will do anything, since the emulator won't know what to do with them. Most likely it will interpret new field as the one it was looking for and skip last field. So I guess we need this answered by the coder of the emulator, weather or not we can control which direction you're facing when you zone? Also weather or not you can alter the zone in points and if not can this be added in the next update?