Daniel Gibbs
5 years ago
committed by
GitHub
GitHub
187 changed files with 1289 additions and 669 deletions
@ -5,32 +5,34 @@ |
|||
The following is a set of guidelines for contributing to LinuxGSM, which are hosted in the [GameServerManagers Organization](https://github.com/gameservermanagers) on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request. |
|||
|
|||
## Table of Contents |
|||
* [Contributing to LinuxGSM](#contributing-to-linuxgsm) |
|||
* [Table of Contents](#table-of-contents) |
|||
|
|||
[Contributing to LinuxGSM](#contributing-to-linuxgsm) |
|||
* [Table of Contents](#table-of-contents) |
|||
* [Code of Conduct](#code-of-conduct) |
|||
* [Bug/Enhancement Contributions](#---bug-enhancement-contributions---) |
|||
* [Reporting Bugs](#--reporting-bugs) |
|||
* [Before Submitting A Bug Report](#before-submitting-a-bug-report) |
|||
* [How Do I Submit A (Good) Bug Report?](#how-do-i-submit-a--good--bug-report-) |
|||
* [Suggesting Features](#--suggesting-features) |
|||
* [Before Submitting An Feature Suggestion](#before-submitting-an-feature-suggestion) |
|||
* [How Do I Submit A (Good) Feature Suggestion?](#how-do-i-submit-a--good--feature-suggestion-) |
|||
* [Game Server Requests](#---game-server-requests) |
|||
* [Before Submitting a Game Server Request](#before-submitting-a-game-server-request) |
|||
* [How Do I Submit A (Good) Game Server Suggestion?](#how-do-i-submit-a--good--feature-suggestion--1) |
|||
* [Game Server Specific Issues](#---game-server-specific-issues) |
|||
* [Code Contributions](#---code-contributions) |
|||
* [Pull Requests](#pull-requests) |
|||
* [Pull Request naming convention](#pull-request-naming-convention) |
|||
* [Testing](#testing) |
|||
* [Pull Request Status Checks](#pull-request-status-checks) |
|||
* [Test Environment](#test-environment) |
|||
* [Styleguides](#-wine-glass--styleguides) |
|||
* [Git Commit Messages](#git-commit-messages) |
|||
* [BASH Styleguide](#bash-styleguide) |
|||
* [Document Contributions](#-blue-book--document-contributions) |
|||
* [Documentation Styleguide](#documentation-styleguide) |
|||
* [🎉 Bug/Enhancement Contributions 🐛](#bug-enhancement-contributions) |
|||
+ [🐛Reporting Bugs](#reporting-bugs) |
|||
- [Before Submitting A Bug Report](#before-submitting-a-bug-report) |
|||
- [How Do I Submit A (Good) Bug Report?](#how-do-i-submit-a--good--bug-report-) |
|||
+ [🎉Suggesting Features](#suggesting-features) |
|||
- [Before Submitting An Feature Suggestion](#before-submitting-an-feature-suggestion) |
|||
- [How Do I Submit A (Good) Feature Suggestion?](#how-do-i-submit-a--good--feature-suggestion-) |
|||
+ [🎮 Game Server Requests](#game-server-requests) |
|||
- [Before Submitting a Game Server Request](#before-submitting-a-game-server-request) |
|||
- [How Do I Submit A (Good) Game Server Request?](#how-do-i-submit-a--good--game-server-request-) |
|||
+ [🎮 Game Server Specific Issues](#game-server-specific-issues) |
|||
* [💻 Code Contributions](#code-contributions) |
|||
+ [Pull Requests](#pull-requests) |
|||
- [Pull Request naming convention](#pull-request-naming-convention) |
|||
+ [Testing](#testing) |
|||
- [Pull Request Status Checks](#pull-request-status-checks) |
|||
- [Test Environment](#test-environment) |
|||
+ [:wine_glass: Styleguides](#-wine-glass--styleguides) |
|||
- [Git Commit Messages](#git-commit-messages) |
|||
- [BASH Styleguide](#bash-styleguide) |
|||
* [:blue_book: Document Contributions](#-blue-book--document-contributions) |
|||
+ [Documentation Styleguide](#documentation-styleguide) |
|||
* [Issue and Pull Request Labels](#issue-and-pull-request-labels) |
|||
|
|||
## Code of Conduct |
|||
|
|||
This project and everyone participating in it are governed by the [LinuxGSM Code of Conduct](https://github.com/GameServerManagers/linuxgsm/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behaviour to [[email protected]](mailto:[email protected]). |
|||
@ -41,11 +43,11 @@ This project and everyone participating in it are governed by the [LinuxGSM Code |
|||
|
|||
This section guides you through submitting a bug report for LinuxGSM. Following these guidelines help maintainers and the community understand your report 📝, reproduce the behaviour💻, and find any related reports 🔎. |
|||
|
|||
Before creating bug reports, please check [this list](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#before-submitting-a-bug-report) as you might find out that you don’t need to create one. When you are creating a bug report, please [include as many details as possible](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-bug-report). Fill out [the required template](https://github.com/atom/.github/blob/master/.github/ISSUE_TEMPLATE/bug_report.md), the information it asks for helps us resolve issues faster. |
|||
Before creating bug reports, please check [this list](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#before-submitting-a-bug-report) as you might find out that you don’t need to create one. When you are creating a bug report, please [include as many details as possible](https://github.com/GameServerManagers/linuxgsm/blob/master/CONTRIBUTING.md#how-do-i-submit-a-good-bug-report). Fill out [the required template]([https://github.com/GameServerManagers/LinuxGSM/issues/new/choose](https://github.com/GameServerManagers/LinuxGSM/issues/new/choose)), the information it asks for helps us resolve issues faster. |
|||
|
|||
#### Before Submitting A Bug Report |
|||
|
|||
* **Check the** [**documentation**](https://docs.linuxgsm.com/%5D(https://docs.linuxgsm.com/))**.** You might be able to find the cause of the problem and fix things yourself. |
|||
* **Check the [documentation](https://docs.linuxgsm.com).** You might be able to find the cause of the problem and fix things yourself. |
|||
* **Check that the problem is not related to** [**support page**](https://linuxgsm/com/support) for links to other support options. |
|||
* **Check the** [**support page**](https://linuxgsm/com/support) for links to other support options. |
|||
* **Perform a** [**cursory search**](https://github.com/search?q=org:GameServerManagers%20type:issues&type=Issues) to see if the problem has already been reported. If it has **and the issue is still open**, add a comment to the existing issue and give it a thumbs up instead of opening a new one. |
|||
@ -83,19 +85,23 @@ Features are tracked as [GitHub issues](https://guides.github.com/features/issue |
|||
|
|||
### 🎮 Game Server Requests |
|||
|
|||
This section guides you through submitting a game server request for LinuxGSM, Following these guidelines help maintainers and the community understand your game server request 📝 |
|||
|
|||
This section guides you through submitting a game server request for LinuxGSM, Following these guidelines help maintainers and the community understand your game server request 📝. |
|||
#### Before Submitting a Game Server Request |
|||
|
|||
* **Check for existing** [**game server requests**](https://github.com/GameServerManagers/LinuxGSM/labels/type%3A%20game%20server%20request) to see if the new game server has already been suggested. If it has **and if the new game server is still open**, give it a thumbs up instead of opening a new one. |
|||
* **Check for existing** [**game server requests**](https://github.com/GameServerManagers/LinuxGSM/labels/type%3A%20game%20server%20request) to see if the new game server has already been suggested. If it has **and if the new game server is still open**, give it a thumbs. |
|||
* **Check the game server is supported on Linux**, this does not include Wine servers which we do not support. |
|||
#### How Do I Submit A (Good) Game Server Request? |
|||
* The title should be as follows: **[Server Request] Game Name** |
|||
* **Provide Steam App ID** if applicable |
|||
* **Supply any documentation/how-to guides** for the game server. |
|||
|
|||
### 🎮 Game Server Specific Issues |
|||
|
|||
LinuxGSM is a management script that acts as a wrapper around game servers. These game servers are developed by different game developers such as Valve, Epic and Facepunch to name a few. |
|||
|
|||
LinuxGSM has no control over the development and limited knowledge issues directly relating to the game servers themselves. The same also applies for any mods, add-ons, maps etc. |
|||
LinuxGSM has no control over the development and limited knowledge of issues directly relating to the game servers themselves. The same also applies for any mods, add-ons, maps etc. |
|||
|
|||
If there is an issue with a specific game server or mod the best action may be to contact the game/mod developers on there support forums. If it is unclear some community members might be able to help. |
|||
If there is an issue with a specific game server or mod the best action may be to contact the game/mod developers on there support forums. If it is unclear some community members should be able to help. |
|||
|
|||
A [list](https://docs.linuxgsm.com/support/game-server) of known game developer forums is available on the [LinuxGSM docs](https://docs.linuxgsm.com/support/game-server). |
|||
|
|||
@ -112,7 +118,7 @@ The process described here has several goals: |
|||
|
|||
Please follow these steps to have your contribution considered by the maintainers: |
|||
|
|||
1. Follow all instructions in [the template](https://github.com/GameServerManagers/LinuxGSM/blob/master/.github/pull_request_template.md) |
|||
1. Follow all check-list in [the template](https://github.com/GameServerManagers/LinuxGSM/blob/master/.github/pull_request_template.md) |
|||
2. Follow the [style guides](#styleguides) |
|||
3. After you submit your pull request, verify that all [status checks](https://help.github.com/articles/about-status-checks/) are passing |
|||
|
|||
@ -130,24 +136,24 @@ If applied, this commit will _your subject line here_ |
|||
|
|||
For example: |
|||
|
|||
* If applied, this commit will _refactor subsystem X for readability_ |
|||
* If applied, this commit will _update getting started documentation_ |
|||
* If applied, this commit will _remove deprecated methods_ |
|||
* If applied, this commit will _release version 1.0.0_ |
|||
* If applied, this commit will _merge pull request #123 from user/branch_ |
|||
* If applied, this commit will **refactor subsystem X for readability** |
|||
* If applied, this commit will **update getting started documentation** |
|||
* If applied, this commit will **remove deprecated methods** |
|||
* If applied, this commit will **release version 1.0.0** |
|||
* If applied, this commit will **merge pull request #123 from user/branch** |
|||
|
|||
Notice how this doesn’t work for the other non-imperative forms: |
|||
|
|||
* If applied, this commit will _fixed bug with Y_ |
|||
* If applied, this commit will _change the behaviour of X_ |
|||
* If applied, this commit will _more fixes for broken stuff_ |
|||
* If applied, this commit will _sweet new API methods_ |
|||
* If applied, this commit will **fixed bug with Y** |
|||
* If applied, this commit will **change the behaviour of X** |
|||
* If applied, this commit will **more fixes for broken stuff** |
|||
* If applied, this commit will **sweet new API methods** |
|||
|
|||
Below is an example of the subject line for a pull request. |
|||
Below is an example of the subject line for a pull request: |
|||
|
|||
feat(alerts): add slack support to alerts |
|||
**feat(alerts): add slack support to alerts** |
|||
|
|||
fix(csgoserver): remove SteamCMD auth requirement 32-bit workaround |
|||
**fix(csgoserver): remove SteamCMD auth requirement 32-bit workaround** |
|||
|
|||
### Testing |
|||
|
|||
@ -155,7 +161,7 @@ fix(csgoserver): remove SteamCMD auth requirement 32-bit workaround |
|||
When a Pull Request is submitted, a series of status check tests are conducted. These tests will asses the code quality, complete CI tests etc. To get your PR merged these status checks must pass. |
|||
|
|||
#### Test Environment |
|||
It is recommended that you have a testing environment available to test your code during development. To test your own cod you must change some variables within the `linuxgsm.sh` file. This will force the use of your own code branch. |
|||
It is recommended that you have a testing environment available to test your code during development. To test your own code you must change some variables within the `linuxgsm.sh` file. This will force the use of your own code branch. |
|||
```bash |
|||
## GitHub Branch Select |
|||
# Allows for the use of different function files |
|||
@ -183,7 +189,7 @@ As well as code contributions it is possible to contribute by writing and improv |
|||
|
|||
### Documentation Styleguide |
|||
|
|||
LinuxGSM has various documentation available to assist users and developers. LinuxGSM primarily uses [GitBook](http://gitbook.com/) which uses the [Markdown](https://www.markdownguide.org/) document standard. LinuxGSM uses [Codacy](https://app.codacy.com/manual/GameServerManagers/LinuxGSM/dashboard) to analyse any Pull Requests to give you feedback on markup standards. |
|||
LinuxGSM has various documentation available to assist [users](https://docs.linuxgsm.com) and [developers](dev-docs.linuxgsm.com). LinuxGSM primarily uses [GitBook](http://gitbook.com/) which uses the [Markdown](https://www.markdownguide.org/) document standard. LinuxGSM uses [Codacy](https://app.codacy.com/manual/GameServerManagers/LinuxGSM/dashboard) to analyse any Pull Requests to give you feedback on markup standards. |
|||
|
|||
## Issue and Pull Request Labels |
|||
|
|||
|
|||
File diff suppressed because one or more lines are too long
@ -0,0 +1,158 @@ |
|||
################################## |
|||
######## Default Settings ######## |
|||
################################## |
|||
# DO NOT EDIT, ANY CHANGES WILL BE OVERWRITTEN! |
|||
# Copy settings from here and use them in either: |
|||
# common.cfg - applies settings to every instance. |
|||
# [instance].cfg - applies settings to a specific instance. |
|||
|
|||
#### Game Server Settings #### |
|||
|
|||
## Server Start Command | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters |
|||
fn_parms(){ |
|||
parms="+statusMonitor 1" |
|||
} |
|||
|
|||
#### LinuxGSM Settings #### |
|||
|
|||
## LinuxGSM Stats |
|||
# Send useful stats to LinuxGSM developers. |
|||
# https://docs.linuxgsm.com/configuration/linuxgsm-stats |
|||
# (on|off) |
|||
stats="off" |
|||
|
|||
## Notification Alerts |
|||
# (on|off) |
|||
|
|||
# Display IP | https://docs.linuxgsm.com/alerts#display-ip |
|||
displayip="" |
|||
|
|||
# More info | https://docs.linuxgsm.com/alerts#more-info |
|||
postalert="off" |
|||
postdays="7" |
|||
posttarget="https://termbin.com" |
|||
|
|||
# Discord Alerts | https://docs.linuxgsm.com/alerts/discord |
|||
discordalert="off" |
|||
discordwebhook="webhook" |
|||
|
|||
# Email Alerts | https://docs.linuxgsm.com/alerts/email |
|||
emailalert="off" |
|||
email="[email protected]" |
|||
emailfrom="" |
|||
|
|||
# IFTTT Alerts | https://docs.linuxgsm.com/alerts/ifttt |
|||
iftttalert="off" |
|||
ifttttoken="accesstoken" |
|||
iftttevent="linuxgsm_alert" |
|||
|
|||
# Mailgun Email Alerts | https://docs.linuxgsm.com/alerts/mailgun |
|||
mailgunalert="off" |
|||
mailguntoken="accesstoken" |
|||
mailgundomain="example.com" |
|||
mailgunemailfrom="[email protected]" |
|||
mailgunemail="[email protected]" |
|||
|
|||
# Pushbullet Alerts | https://docs.linuxgsm.com/alerts/pushbullet |
|||
pushbulletalert="off" |
|||
pushbullettoken="accesstoken" |
|||
channeltag="" |
|||
|
|||
# Pushover Alerts | https://docs.linuxgsm.com/alerts/pushover |
|||
pushoveralert="off" |
|||
pushovertoken="accesstoken" |
|||
|
|||
# Slack Alerts | https://docs.linuxgsm.com/alerts/slack |
|||
slackalert="off" |
|||
slackwebhook="webhook" |
|||
|
|||
# Telegram Alerts | https://docs.linuxgsm.com/alerts/telegram |
|||
# You can add a custom cURL string eg proxy (useful in Russia) or else in "curlcustomstring". |
|||
# like a "--socks5 ipaddr:port" for socks5 proxy see more in "curl --help", if you not need |
|||
# any custom string in curl - simple ignore this parameter. |
|||
telegramalert="off" |
|||
telegramtoken="accesstoken" |
|||
telegramchatid="" |
|||
curlcustomstring="" |
|||
|
|||
## Updating | https://docs.linuxgsm.com/commands/update |
|||
updateonstart="off" |
|||
|
|||
## Backup | https://docs.linuxgsm.com/commands/backup |
|||
maxbackups="4" |
|||
maxbackupdays="30" |
|||
stoponbackup="on" |
|||
|
|||
## Logging | https://docs.linuxgsm.com/features/logging |
|||
consolelogging="on" |
|||
logdays="7" |
|||
|
|||
## Monitor | https://docs.linuxgsm.com/commands/monitor |
|||
# Query delay time |
|||
querydelay="1" |
|||
|
|||
## ANSI Colors | https://docs.linuxgsm.com/features/ansi-colors |
|||
ansi="on" |
|||
|
|||
#### Advanced Settings #### |
|||
|
|||
## Message Display Time | https://docs.linuxgsm.com/features/message-display-time |
|||
sleeptime="0.5" |
|||
|
|||
## Stop Mode | https://docs.linuxgsm.com/features/stop-mode |
|||
# 1: tmux kill |
|||
# 2: CTRL+c |
|||
# 3: quit |
|||
# 4: quit 120s |
|||
# 5: stop |
|||
# 6: q |
|||
# 7: exit |
|||
# 8: 7 Days to Die |
|||
# 9: GoldSrc |
|||
# 10: Avorion |
|||
# 11: end |
|||
stopmode="3" |
|||
|
|||
## Query mode |
|||
# 1: session only |
|||
# 2: gamedig + gsquery |
|||
# 3: gamedig |
|||
# 4: gsquery |
|||
# 5: tcp |
|||
querymode="1" |
|||
querytype="" |
|||
|
|||
## Game Server Details |
|||
# Do not edit |
|||
gamename="Battlefield: Vietnam" |
|||
engine="refractor" |
|||
glibc="2.2.4" |
|||
|
|||
#### Directories #### |
|||
# Edit with care |
|||
|
|||
## Game Server Directories |
|||
systemdir="${serverfiles}" |
|||
executabledir="${systemdir}" |
|||
executable="./start.sh" |
|||
servercfgdir="${systemdir}/mods/bfvietnam/settings" |
|||
servercfg="serversettings.con" |
|||
servercfgdefault="serversettings.con" |
|||
servercfgfullpath="${servercfgdir}/${servercfg}" |
|||
|
|||
## Backup Directory |
|||
backupdir="${lgsmdir}/backup" |
|||
|
|||
## Logging Directories |
|||
logdir="${rootdir}/log" |
|||
gamelogdir="${serverfiles}/mods/bfvietnam/logs" |
|||
lgsmlogdir="${logdir}/script" |
|||
consolelogdir="${logdir}/console" |
|||
lgsmlog="${lgsmlogdir}/${selfname}-script.log" |
|||
consolelog="${consolelogdir}/${selfname}-console.log" |
|||
alertlog="${lgsmlogdir}/${selfname}-alert.log" |
|||
postdetailslog="${lgsmlogdir}/${selfname}-postdetails.log" |
|||
|
|||
## Logs Naming |
|||
lgsmlogdate="${lgsmlogdir}/${selfname}-script-$(date '+%Y-%m-%d-%H:%M:%S').log" |
|||
consolelogdate="${consolelogdir}/${selfname}-console-$(date '+%Y-%m-%d-%H:%M:%S').log" |
|||
@ -0,0 +1,173 @@ |
|||
################################## |
|||
######## Default Settings ######## |
|||
################################## |
|||
# DO NOT EDIT, ANY CHANGES WILL BE OVERWRITTEN! |
|||
# Copy settings from here and use them in either: |
|||
# common.cfg - applies settings to every instance. |
|||
# [instance].cfg - applies settings to a specific instance. |
|||
|
|||
#### Game Server Settings #### |
|||
|
|||
## Server Start Settings | https://docs.linuxgsm.com/configuration/start-parameters |
|||
ip="0.0.0.0" |
|||
port="7777" |
|||
beaconport="15000" |
|||
maxplayers="32" |
|||
|
|||
## Server Start Command | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters |
|||
fn_parms(){ |
|||
parms="-port="${port}" -beaconport="${beaconport}" -MULTIHOME="${ip}" -maxplayers=${maxplayers}" |
|||
} |
|||
|
|||
#### LinuxGSM Settings #### |
|||
|
|||
## LinuxGSM Stats |
|||
# Send useful stats to LinuxGSM developers. |
|||
# https://docs.linuxgsm.com/configuration/linuxgsm-stats |
|||
# (on|off) |
|||
stats="off" |
|||
|
|||
## Notification Alerts |
|||
# (on|off) |
|||
|
|||
# Display IP | https://docs.linuxgsm.com/alerts#display-ip |
|||
displayip="" |
|||
|
|||
# More info | https://docs.linuxgsm.com/alerts#more-info |
|||
postalert="off" |
|||
postdays="7" |
|||
posttarget="https://termbin.com" |
|||
|
|||
# Discord Alerts | https://docs.linuxgsm.com/alerts/discord |
|||
discordalert="off" |
|||
discordwebhook="webhook" |
|||
|
|||
# Email Alerts | https://docs.linuxgsm.com/alerts/email |
|||
emailalert="off" |
|||
email="[email protected]" |
|||
emailfrom="" |
|||
|
|||
# IFTTT Alerts | https://docs.linuxgsm.com/alerts/ifttt |
|||
iftttalert="off" |
|||
ifttttoken="accesstoken" |
|||
iftttevent="linuxgsm_alert" |
|||
|
|||
# Mailgun Email Alerts | https://docs.linuxgsm.com/alerts/mailgun |
|||
mailgunalert="off" |
|||
mailguntoken="accesstoken" |
|||
mailgundomain="example.com" |
|||
mailgunemailfrom="[email protected]" |
|||
mailgunemail="[email protected]" |
|||
|
|||
# Pushbullet Alerts | https://docs.linuxgsm.com/alerts/pushbullet |
|||
pushbulletalert="off" |
|||
pushbullettoken="accesstoken" |
|||
channeltag="" |
|||
|
|||
# Pushover Alerts | https://docs.linuxgsm.com/alerts/pushover |
|||
pushoveralert="off" |
|||
pushovertoken="accesstoken" |
|||
|
|||
# Slack Alerts | https://docs.linuxgsm.com/alerts/slack |
|||
slackalert="off" |
|||
slackwebhook="webhook" |
|||
|
|||
# Telegram Alerts | https://docs.linuxgsm.com/alerts/telegram |
|||
# You can add a custom cURL string eg proxy (useful in Russia) or else in "curlcustomstring". |
|||
# like a "--socks5 ipaddr:port" for socks5 proxy see more in "curl --help", if you not need |
|||
# any custom string in curl - simple ignore this parameter. |
|||
telegramalert="off" |
|||
telegramtoken="accesstoken" |
|||
telegramchatid="" |
|||
curlcustomstring="" |
|||
|
|||
## Updating | https://docs.linuxgsm.com/commands/update |
|||
updateonstart="off" |
|||
|
|||
## Backup | https://docs.linuxgsm.com/commands/backup |
|||
maxbackups="4" |
|||
maxbackupdays="30" |
|||
stoponbackup="on" |
|||
|
|||
## Logging | https://docs.linuxgsm.com/features/logging |
|||
consolelogging="on" |
|||
logdays="7" |
|||
|
|||
## Monitor | https://docs.linuxgsm.com/commands/monitor |
|||
# Query delay time |
|||
querydelay="1" |
|||
|
|||
## ANSI Colors | https://docs.linuxgsm.com/features/ansi-colors |
|||
ansi="on" |
|||
|
|||
#### Advanced Settings #### |
|||
|
|||
## Message Display Time | https://docs.linuxgsm.com/features/message-display-time |
|||
sleeptime="0.5" |
|||
|
|||
## SteamCMD Settings | https://docs.linuxgsm.com/steamcmd |
|||
# Server appid |
|||
appid="897590" |
|||
# SteamCMD Branch | https://docs.linuxgsm.com/steamcmd/branch |
|||
branch="" |
|||
betapassword="" |
|||
# Master Server | https://docs.linuxgsm.com/steamcmd/steam-master-server |
|||
steammaster="false" |
|||
|
|||
## Stop Mode | https://docs.linuxgsm.com/features/stop-mode |
|||
# 1: tmux kill |
|||
# 2: CTRL+c |
|||
# 3: quit |
|||
# 4: quit 120s |
|||
# 5: stop |
|||
# 6: q |
|||
# 7: exit |
|||
# 8: 7 Days to Die |
|||
# 9: GoldSrc |
|||
# 10: Avorion |
|||
# 11: end |
|||
stopmode="2" |
|||
|
|||
## Query mode |
|||
# 1: session only |
|||
# 2: gamedig + gsquery |
|||
# 3: gamedig |
|||
# 4: gsquery |
|||
# 5: tcp |
|||
querymode="1" |
|||
querytype="" |
|||
|
|||
## Game Server Details |
|||
# Do not edit |
|||
gamename="Memories of Mars" |
|||
engine="unreal4" |
|||
glibc="2.17" |
|||
|
|||
#### Directories #### |
|||
# Edit with care |
|||
|
|||
## Game Server Directories |
|||
systemdir="${serverfiles}/Game" |
|||
executabledir="${systemdir}/Binaries/Linux" |
|||
executable="./MemoriesOfMarsServer" |
|||
servercfgdir="${serverfiles}" |
|||
servercfg="DedicatedServerConfig.cfg" |
|||
servercfgdefault="DedicatedServerConfig.cfg" |
|||
servercfgfullpath="${servercfgdir}/${servercfg}" |
|||
|
|||
## Backup Directory |
|||
backupdir="${lgsmdir}/backup" |
|||
|
|||
## Logging Directories |
|||
logdir="${rootdir}/log" |
|||
gamelogdir="${serverfiles}/Game/Saved/Logs" |
|||
lgsmlogdir="${logdir}/script" |
|||
consolelogdir="${logdir}/console" |
|||
lgsmlog="${lgsmlogdir}/${selfname}-script.log" |
|||
consolelog="${consolelogdir}/${selfname}-console.log" |
|||
alertlog="${lgsmlogdir}/${selfname}-alert.log" |
|||
postdetailslog="${lgsmlogdir}/${selfname}-postdetails.log" |
|||
|
|||
## Logs Naming |
|||
lgsmlogdate="${lgsmlogdir}/${selfname}-script-$(date '+%Y-%m-%d-%H:%M:%S').log" |
|||
consolelogdate="${consolelogdir}/${selfname}-console-$(date '+%Y-%m-%d-%H:%M:%S').log" |
|||
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue