Tredegar - Adding the 'run in background' did the trick! That's exactly what I was after - useful technique to know and a nice simple answer
I've now created a single script that does everything.
Interestingly it does dump the 'initial' text output of each instance to the console, but this time all at once. There is no 'prompt' visible afterwards on the console, but as soon as I start typing it accepts it as a new command and the server instances disapear into the background. Just a quirk though, doesn't interfere with anything.
Bigearsbilly - The fearserver by default runs on port 27888. To change any of the settings (including the port) you have to specify an optionsfile when executing the file. I didn't mention this previously as it wasn't really relevant.
So my 'combined' startup script looks like this:
./fearserver.bin -optionsfile /home/fear/FEAR/ServerOptions/ServerOptions-SMTDM $
./fearserver.bin -optionsfile /home/fear/FEAR/ServerOptions/ServerOptions-SMDM $
./fearserver.bin -optionsfile /home/fear/FEAR/ServerOptions/ServerOptions-SMCTF $
Having 3 instances lets me have the option of 3 different game modes. I could make the script run at startup but would prefer to start the servers manually...
I can confirm the 3 instances laucnhed from the single script are all running smoothly and are being thoroughly tested
Thanks for all your help guys!