⚠ This is WIP
Why?
bsm works because files/directories have a specific structure. This should be documented and finalized.
Structure
/ refers to the directory where all related files are stored, such as /home/bzfs/myserver.
server refers to a bzfs instance.
map refers to the configuration used to run a server (bzw+config).
world refers to the bzw file.
- Paths ending in
/ refer to a directory.
| Path |
Description |
/log.sh |
Bash script that takes in the output from bzfs - this should be part of bsm and not it's own script |
/configs/master.conf |
Configuration file loaded for every server |
/configs/publickey |
Contains the public key to be used (optional) |
/configs/groups.txt |
Group permissions file (optional) |
/configs/badwords.txt |
Badwords file (optional) |
/maps/ |
Stores one map per subdirectory, with the subdirectory name being the ID |
/maps/name/config.conf |
Map-specific configuration file |
/maps/name/map.bzw |
Map world file |
/maps/name/pid |
PID of the running server (auto generated) |
/maps/name/reports.txt |
Reports for the map (auto generated) |
/maps/name/logs/ |
Log files by date (auto generated) |
Why?
bsmworks because files/directories have a specific structure. This should be documented and finalized.Structure
/refers to the directory where all related files are stored, such as/home/bzfs/myserver.serverrefers to abzfsinstance.maprefers to the configuration used to run aserver(bzw+config).worldrefers to the bzw file./refer to a directory./log.shbzfs- this should be part ofbsmand not it's own script/configs/master.conf/configs/publickey/configs/groups.txt/configs/badwords.txt/maps//maps/name/config.conf/maps/name/map.bzw/maps/name/pid/maps/name/reports.txt/maps/name/logs/