Ok, I'm willing to learn something new... Instead of boasting about what you can do, or there is a proper way (chain loading)... Why not share or explain... Because every where I look, it's pretty much the same way of starting the maps by new instances... No pun intended...
Fair enough
It's actually quite easy
for instance, lets say we want to start a server with the following 4 maps:
The worldmap, the starting map, heaven and hell. this nets us: gs01, is21, is22 and is61
Most, if not all guides, and also iweb do it as follow (correct me if im wrong)
Code:
./gs gs01
./gs is21
./gs is22
./gs is61
(if you feel fancy, you can add the > gs01.log, etc behind to write the output to a log file, or /dev/null if you simply dont want to see any of it)
Now, whilst that works, it starts a new instance every time. consuming your memory.
So how do you chainload it?
Instead of the above lines you put them in 1 line
Code:
./gs gs01 gs.conf gmserver.conf gsalias_wallow.conf is21 is22 is61
* Note: add in the configs as well, wont work without it
This will chainload them and thus decrease memory usage
Full server config
Code:
./gs gs01 gs.conf gmserver.conf gsalias_wallow.conf is01 is02 is05 is06 is07 is08 is09 is10 is11 is12 is13 is14 is15 is16 is17 is18 is19 is20 is22 is21 is23 is24 is25 is26 is27 is28 is29 is31 is32 is33 is34 is35 is37 is38 is39 is40 is41 is42 is43 is44 is45 is46 is47 is48 is49 is61 is62 is63 is66 is67 is68 is69 is70 is71 is72 is73 is74 is75
* Note 1: Disk usage will spike slightly due to it loading all the data for the maps
* Note 2: Adding a '> output.log' behind the command results all the logs from all the maps getting written to 1 file
Give it a whirl i suppose, this trick has worked for me for years. no reason it shouldn't work with anyone else's setup but you never know. (Oh for your information, I am running Ubuntu 16.04 with the 4.12 kernel)
