You're right, but I'm talking about the *client* end. The client will only load zones it knows about, so if you want to create a totally new zone you have to export it as something the client knows about, like "tutorial". You could call it's .S3D file name anything you wish, like deadgulch.s3d, but internally the filenames are all the same as those in tutorial.s3d. It would be this way for all newly created zones. Then, the little zone proxy that the *user* is running would intercept the zone packet from the server, copy the appropriate .S3D file over tutorial.s3d in the EQ folder, and tell the client to zone to "tutorial".
The question arises when you go from one new zone to another. As far as the client is concerned, you're in zone "tutorial", and I don't know if it will perform a full zone reload if it is told to zone to "tutorial" again. If not, then you have to have two sets of all new zones--one coded for "tutorial" and one for another, like "cshome". Then the zone proxy program simply has to remember which one you're using and switch to the other one.
|