Ah, hehe. For *server operators*, there is an additional step you need to take:
1. Add another column to the zone table. The modified server code will look for a column called "thirdparty", where it should contain 0 for all normal zones and 1 for all third party zones. You can make the change by doing something like this:
Code:
C:
cd\mysql\bin
mysql
use eq
alter table zone add thirdparty int(2) unsigned default '0';
quit
Then you need to add zone entries for all of the new zones (like "windszone") and set thirdparty to 1 for them.
There is a sticky in the 3rd party section that explains this in greater detail, but this is the crux of it. Of course, it's a good idea to set things like zone points, safe points etc. if you want other people to play in the zones...I wouldn't mind dumping the pertinent parts of my db and posting them, but I don't know how to do that...
In addition to this, if you have your server on a LAN and you want to access ZP zones from inside the same LAN, you either need to use a dynamic DNS service like dyndns or you might have to make a change to world/client.cpp. This is because world.exe might/will see the address of your router on incoming connections and it won't then be able to make an outgoing connection to ZP. My server code differs from what I uploaded in that I have a statement that substitutes my actual WAN IP address when it sees the router's internal address so the outgoing connection will work. If you're using minilogin this may or may not be a problem, I'm not sure. Of course, this whole issue could simply be because of a bug in my Linksys router's firmware and not affect anyone else...