zone line fixing

[erfg12]

The zone lines all need to be fixed. zone_points holds the zone line data. Here are the issues that need to be fixed.

1. If you see any that say X:0, Y:0, Z:0 that needs to be fixed.
2. Some of the zone lines to/from match up which means when you zone in you will be zoned right back out.
3. Z axis are very far off which means the zone line will be above/below where it's supposed to be.

[erfg12]

We can try the Velious PEQ database, it has some different zone lines in it - https://sourceforge.net/projects/projecteq/files/ProjectEQ%20Databases/PEQ%20Velious/

Otherwise there is a much older EQEmu 3.6 database with zone points - http://prdownloads.sourceforge.net/eqemu/EQEMu-3.6-DB-Addon.zip?download

and a EQEmu 4.1 database with zone points - http://prdownloads.sourceforge.net/eqemu/EQEmu-0.4.1-DB-Addon.zip?download

[jimm0thy]

I had tried a few different database's originally, including various ones from PEQ, but zoning never seemed to work right (always getting stuck in a zoning loop). The problem seemed to be the range around the zoning coordinates and is why I started working on setting up "new" zone lines. The ones I setup are pretty close but obviously not exact, also I wasn't sure how that was going to work on the larger zone's zonelines so I added the additional code for those (which would work for small zone lines as well). Attached is what I have done atm, Faydwer should be set as well as most of Antonica. We still need Odus, Kunark, and Velious - and multiple dungeon zonelines

eqclassic_zonelines.xlsx

[jimm0thy]

Forgot to mention, I also compiled a version of Zone.exe that removes the zoning code all together to make it easier to figure out where the zone lines should be without trigger a zone. Though it seems a lot of zones in Antonica have no invisible / physical wall and you can just fall off the side of the world

https://drive.google.com/open?id=1xfxE3CzI2QOfMcPSXnvbR6dDeTry5E2Q

[erfg12]

I added a .gitignore to the repo, and merged some of your code (if not all). I would recommend re-forking the source to prevent Visual Studio garbage files from going into the repo. Also, use something like Google Drive or One Drive for your .xlsx documents. If you update zone lines, go ahead and make new small update .SQL file(s) that update just the zone lines you fixed from the base database.

I highly recommend keeping big data files out of the repo to prevent long pull/push times and lots of bandwidth data usages.

Also, join our Discord if you can so we can collaborate on this project.