I'm trying to set the server up so that multiple sets of config files can be used (for mulltiple servers).
This was easy in windows ... I just copied the arma folder and modified the configs in the new folder ... but I can't do it in linux. The install seems to use the same config directory no matter what (except for armagetron vs. armagetronad)
So I've tried running the server and setting flags like this:
[egg ]$ /usr/local/games/armagetronad-dedicated
with the following flags entered in command line as well
--datadir /usr/local/games/armagetronad-dedicated
--configdir /home/egg/tron/boc/config/
--userdatadir /home/egg/tron/boc/
--vardir /home/egg/tron/boc/
Shouldn't it read the configs from /home/egg/tron/boc/config/ ... it's not.
at this point, I can't even find the config files that are being used to run the server. I check by checking the server name that was used .. so I have all server names currenly set to the path so I know if I have the right ones ... still can't find em.
Any suggestions?
config files ...linux .. what path is used?
Yeah. 
I actually copied the armagetronad-dedicated script to several different names and modified them directly to reflect the real paths to things.
I'm on my laptop right now and those files are inaccessible, but here's the explanation.
/usr/local/bin/armagetronad-dedicated is just a bash wrapper that does some settings migration. The real binary is stored elsewhere. You want your settings to persist, presumably, across upgrades. The best way to do that is to put them in non-standard locations and modify the actual bash wrapper accordingly. Copy it to a different name, of course.
So I have:
/usr/local/bin/armagetronad-dedicated
/usr/local/bin/armagetronad-champions
/usr/local/bin/armagetronad-teams
/usr/local/bin/armagetronad-nuclear
Each one starting a different server, of course.
What you're doing *should* work, so the reason I suggest doing it this way is so you can see right inside the wrapper what paths are getting used where and when and why and so forth.
I actually copied the armagetronad-dedicated script to several different names and modified them directly to reflect the real paths to things.
I'm on my laptop right now and those files are inaccessible, but here's the explanation.
/usr/local/bin/armagetronad-dedicated is just a bash wrapper that does some settings migration. The real binary is stored elsewhere. You want your settings to persist, presumably, across upgrades. The best way to do that is to put them in non-standard locations and modify the actual bash wrapper accordingly. Copy it to a different name, of course.
So I have:
/usr/local/bin/armagetronad-dedicated
/usr/local/bin/armagetronad-champions
/usr/local/bin/armagetronad-teams
/usr/local/bin/armagetronad-nuclear
Each one starting a different server, of course.
What you're doing *should* work, so the reason I suggest doing it this way is so you can see right inside the wrapper what paths are getting used where and when and why and so forth.
Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN
Be the devil's own, Lucifer's my name.
- Iron Maiden
Be the devil's own, Lucifer's my name.
- Iron Maiden