I would think the client is already sending the necessary packet...the zoneline information is in the .S3D files, and so the client would know when it's time to zone. I just finished getting OpenZone adding zonelines to zones and exporting them in the .S3D files, but so far there's no response in the client. I'm 100% certain I'm putting it in right, because I loaded the .WLD in DZoneConverter and the zoneline is there. It's possible that the client doesn't use this information anymore or EQEmu ignores the packets, but I figure the information's there for a reason. I'm going to do some more digging..
.
.
.
Well this is interesting. Some zones have the mechanism I described above, whereas other zones only specify a zone point ID, starting with 1 (no destination information at all). I'll switch my code to use the ID method and see if I can coax EQEmu to get the zone points working by putting corresponding entries in the DB...
WC
|
Threaded Mode
