03 Jan 12, 05:47PM
Do as you did the first one but use other names for the files and different ports of course.
Make a copy of server.sh
Rename the copy to new-server.sh (or what ever)
Edit new-server.sh:
Under "CUBE_OPTIONFILE" you add the new servercmdline.txt the server gonna use.
Example: CUBE_OPTIONFILE=-Cconfig/2-servercmdline.txt
This means you need to make a new servercmdline.txt or copy the one you have and rename it to 2-servercmdline.txt.
In 2-servercmdline.txt you need to add the new maprot file, blacklist etc.
Remember you must use the -f switch (ports) in the new server if they are on the same IP as the old one.
For example, use -f28765 for a second server (if servers are on same IP).
Open the new ports on your router.
Hope that helps a bit.
My English sucks so feel free to complain if you dont understand. :P
Make a copy of server.sh
Rename the copy to new-server.sh (or what ever)
Edit new-server.sh:
Under "CUBE_OPTIONFILE" you add the new servercmdline.txt the server gonna use.
Example: CUBE_OPTIONFILE=-Cconfig/2-servercmdline.txt
This means you need to make a new servercmdline.txt or copy the one you have and rename it to 2-servercmdline.txt.
In 2-servercmdline.txt you need to add the new maprot file, blacklist etc.
Remember you must use the -f switch (ports) in the new server if they are on the same IP as the old one.
For example, use -f28765 for a second server (if servers are on same IP).
Open the new ports on your router.
Hope that helps a bit.
My English sucks so feel free to complain if you dont understand. :P