Custom cfg, blacklist from URL
#3
There are several ways to do that.
1) host the stuff on an NFS/SMB/... drive and load the config file from there.
2) use something rsync/scp/... to actively push the file to the hosts
3) download the file every time a client is started, by adding something like
curl http://path.to/config.cfg > config/saved.cfg
to the beginning of assaultcube.sh/assaultcube.bat. That's probably the most convenient option, and it doesn't need root.

Of course, there are additional ways, but they're probably more work than doing the stuff manually. How many instances are we talking about anyway?
Thanks given by:


Messages In This Thread
Custom cfg, blacklist from URL - by FleshyPod - 08 Oct 12, 04:08PM
RE: Custom cfg, blacklist from URL - by Link - 08 Oct 12, 05:46PM
RE: Custom cfg, blacklist from URL - by tempest - 08 Oct 12, 06:19PM