LinuxGSM_ Dev
  • Home
  • Getting Started
    • Getting Started
    • Programming Language
    • Development Software
    • Test Environment
    • Developer Commands
    • Adding a new Game Server
  • Workflow
    • Semantic Versioning
    • Workflow
    • Agile
    • Pull Requests
    • Gitflow
    • Conventional Commits
    • Unit Tests
  • Technical
    • Main Executable
    • Commands
    • Exit Codes
    • Functions
    • Modules
      • Fixes
      • Core
    • Game Server Querying
    • Messages & Logs
    • Checks
    • Exit
    • Install
    • Debuggins
  • Code Standards
    • Style Guide
    • Shellcheck Linter
    • Text Editor Settings
Powered by GitBook
On this page

Was this helpful?

  1. Technical

Commands

Commands

Within LinuxGSM there are many commands that a user will run to complete tasks such as start, stop, monitor, and details. Command scripts are stored will all other modules and are always named something like command_install.sh. See the commands page for more info.

Within LinuxGSM there are many commands that a user will run to complete tasks such as start, stop, monitor, and details. Command scripts are stored with all other modules and are always named something like command_install.sh.

Some game servers may require bespoke commands to complete tasks. Examples of this include Teamspeak 3 and Unreal Tournament 2004. Take a look at the core_getopts.sh module for examples of how to add commands.

PreviousMain ExecutableNextExit Codes

Last updated 1 year ago

Was this helpful?