Handling more than one mission in a server
by TigerHeros · in Torque 3D Professional · 05/31/2010 (12:17 am) · 4 replies
Hi,
I use two mission files. I need to run it on the server simultaneously.
Still now i use only one mission, so i normally run the dedicated server with a mission and connect from the client machine by giving only the IP-address of the server machine. When application is being run, it loads the mission file from server.
But now I have two mission files and I run both mission on the dedicated server. In the client side. I have two buttons for loading each mission. Can you help in this process.
I use two mission files. I need to run it on the server simultaneously.
Still now i use only one mission, so i normally run the dedicated server with a mission and connect from the client machine by giving only the IP-address of the server machine. When application is being run, it loads the mission file from server.
But now I have two mission files and I run both mission on the dedicated server. In the client side. I have two buttons for loading each mission. Can you help in this process.
About the author
#2
05/31/2010 (2:22 am)
yes... but how to run application in different ports on the server. 
#4
If you want multiple persistent missions (as in different players can be in different missions at any time), the easiest approach is use a dedicated server for each mission, and have each one listen to a different port.
You can use NetConnection objects to make the dedicated servers talk to each other, so you can "move" a player from a server to another. Basically, you'll need to tell the new server about all player properties that matter to your game - health, experience, inventory, etc. You can also have a single central "persistence" server specifically to handle such shared player information.
05/31/2010 (6:24 am)
You cannot run two completely independent missions in the same process, at least not without doing many well-planned source changes.If you want multiple persistent missions (as in different players can be in different missions at any time), the easiest approach is use a dedicated server for each mission, and have each one listen to a different port.
You can use NetConnection objects to make the dedicated servers talk to each other, so you can "move" a player from a server to another. Basically, you'll need to tell the new server about all player properties that matter to your game - health, experience, inventory, etc. You can also have a single central "persistence" server specifically to handle such shared player information.
Torque 3D Owner Chris