Lalolyen
10-09-2007, 06:21 PM
I just thought I would post an update on our server. So far we can get zone instancing to work with 2 zone instances (the 3rd one crashes the zone server atm).
So far this is what we have done:
New column in zones called instance that is a number from 0 to 100. This specifies how many instances can be open on the zone. The zone server reads it the same. 0 means its not an instanced zone, 100 means you can have 100 instances running at the same time before giving the message when trying to access the zone "This zone is too dangerous for you to enter!"
If a zone is still loading/booting as each time an instance is requested it will load in in your zone server automatically and remove it under 10 minutes of inactivity you will get: "This zone is not yet ready for adventurers!".
The concept of this is simple actually. You duplicate a zone in your database, and have the same zone name, but place one as a 0 and the other as a 1 and the zone server will then interpret the 0 as the zone you normally enter (like stillmoon temple.
So far this is working with the flagging system that is already programmed in EMU's code, however I am having some problems preventing the zone crashes (as it seems that the zone server MUST have a unique identifier on the zone somehow so I'm thinking of just making a table called instanced zones and have the world server pull the zone from that table OR create a zone in that table if requested from the zone table and it reads 1 in the instance column.)
So far this is what we have done:
New column in zones called instance that is a number from 0 to 100. This specifies how many instances can be open on the zone. The zone server reads it the same. 0 means its not an instanced zone, 100 means you can have 100 instances running at the same time before giving the message when trying to access the zone "This zone is too dangerous for you to enter!"
If a zone is still loading/booting as each time an instance is requested it will load in in your zone server automatically and remove it under 10 minutes of inactivity you will get: "This zone is not yet ready for adventurers!".
The concept of this is simple actually. You duplicate a zone in your database, and have the same zone name, but place one as a 0 and the other as a 1 and the zone server will then interpret the 0 as the zone you normally enter (like stillmoon temple.
So far this is working with the flagging system that is already programmed in EMU's code, however I am having some problems preventing the zone crashes (as it seems that the zone server MUST have a unique identifier on the zone somehow so I'm thinking of just making a table called instanced zones and have the world server pull the zone from that table OR create a zone in that table if requested from the zone table and it reads 1 in the instance column.)