Aliens vs Predator is available for hosting on our platform. This guide covers the basics of setting up and managing your Aliens vs Predator server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Aliens vs Predator server:
-After your server is created, you can configure it through the control panel:
+Aliens vs Predator is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Aliens vs Predator server for your community.
+ +Check server configurationdefault.cfg - Server ConfigurationsThe Aliens vs Predator server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Aliens vs Predator Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Aliens vs Predator Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Aliens vs Predator server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+default.cfg - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Aliens vs Predator Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Aliens vs Predator server hosting +
diff --git a/modules/billing/docs/aliensvspredator/metadata.json b/modules/billing/docs/aliensvspredator/metadata.json index fa894e71..5881484a 100644 --- a/modules/billing/docs/aliensvspredator/metadata.json +++ b/modules/billing/docs/aliensvspredator/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Aliens vs Predator game servers", - "name": "Aliens vs Predator", - "order": 5, - "category": "todo" +{ + "description": "Setup and configuration guide for Aliens vs Predator game servers", + "name": "Aliens vs Predator", + "order": 5, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/aoc/index.php b/modules/billing/docs/aoc/index.php index 4ac8d80f..5c71feb1 100644 --- a/modules/billing/docs/aoc/index.php +++ b/modules/billing/docs/aoc/index.php @@ -1,66 +1,372 @@ -Age of Chivalry is available for hosting on our platform. This guide covers the basics of setting up and managing your Age of Chivalry server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Age of Chivalry server:
-After your server is created, you can configure it through the control panel:
+Age of Chivalry is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Age of Chivalry server for your community.
+ +Check server configurationThe Age of Chivalry server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Age of Chivalry Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Age of Chivalry Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Age of Chivalry server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Age of Chivalry Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Age of Chivalry server hosting +
diff --git a/modules/billing/docs/aoc/metadata.json b/modules/billing/docs/aoc/metadata.json index 3489a38a..47e1d8c8 100644 --- a/modules/billing/docs/aoc/metadata.json +++ b/modules/billing/docs/aoc/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Age of Chivalry game servers", - "name": "Age of Chivalry", - "order": 6, - "category": "todo" +{ + "description": "Setup and configuration guide for Age of Chivalry game servers", + "name": "Age of Chivalry", + "order": 6, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/arma-reforger/index.php b/modules/billing/docs/arma-reforger/index.php index 6f357656..72f92acb 100644 --- a/modules/billing/docs/arma-reforger/index.php +++ b/modules/billing/docs/arma-reforger/index.php @@ -1,68 +1,372 @@ -Arma Reforger is available for hosting on our platform. This guide covers the basics of setting up and managing your Arma Reforger server.
-2001- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Arma Reforger server:
-After your server is created, you can configure it through the control panel:
+Arma Reforger is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Arma Reforger server for your community.
+ +Check server configurationThe Arma Reforger server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Arma Reforger Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Arma Reforger Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Arma Reforger server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Arma Reforger Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Arma Reforger server hosting +
diff --git a/modules/billing/docs/arma-reforger/metadata.json b/modules/billing/docs/arma-reforger/metadata.json index 9fb95e5c..6ae4f2de 100644 --- a/modules/billing/docs/arma-reforger/metadata.json +++ b/modules/billing/docs/arma-reforger/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Arma Reforger game servers", - "name": "Arma Reforger", - "order": 9, - "category": "todo" +{ + "description": "Setup and configuration guide for Arma Reforger game servers", + "name": "Arma Reforger", + "order": 9, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/assettocorsa/index.php b/modules/billing/docs/assettocorsa/index.php index 5ed91d5d..29871b9a 100644 --- a/modules/billing/docs/assettocorsa/index.php +++ b/modules/billing/docs/assettocorsa/index.php @@ -1,68 +1,383 @@ -Assetto Corsa is available for hosting on our platform. This guide covers the basics of setting up and managing your Assetto Corsa server.
-9600- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Assetto Corsa server:
-After your server is created, you can configure it through the control panel:
+Assetto Corsa is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Assetto Corsa server for your community.
+ +Check server configuration/cfg/server_cfg.ini - Server Configurations/cfg/entry_list.ini - More Server ConfigurationsThe Assetto Corsa server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Assetto Corsa Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Assetto Corsa Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Assetto Corsa server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+/cfg/server_cfg.ini - Server Configurations/cfg/entry_list.ini - More Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Assetto Corsa Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Assetto Corsa server hosting +
diff --git a/modules/billing/docs/assettocorsa/metadata.json b/modules/billing/docs/assettocorsa/metadata.json index 59835757..2979b4ad 100644 --- a/modules/billing/docs/assettocorsa/metadata.json +++ b/modules/billing/docs/assettocorsa/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Assetto Corsa game servers", - "name": "Assetto Corsa", - "order": 15, - "category": "todo" +{ + "description": "Setup and configuration guide for Assetto Corsa game servers", + "name": "Assetto Corsa", + "order": 15, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/atlas/index.php b/modules/billing/docs/atlas/index.php index 3132c70d..909e31dd 100644 --- a/modules/billing/docs/atlas/index.php +++ b/modules/billing/docs/atlas/index.php @@ -1,68 +1,372 @@ -Atlas is available for hosting on our platform. This guide covers the basics of setting up and managing your Atlas server.
-5761- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Atlas server:
-After your server is created, you can configure it through the control panel:
+Atlas is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Atlas server for your community.
+ +Check server configurationThe Atlas server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Atlas Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Atlas Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Atlas server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Atlas Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Atlas server hosting +
diff --git a/modules/billing/docs/atlas/metadata.json b/modules/billing/docs/atlas/metadata.json index f523beee..465c9baf 100644 --- a/modules/billing/docs/atlas/metadata.json +++ b/modules/billing/docs/atlas/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Atlas game servers", - "name": "Atlas", - "order": 17, - "category": "todo" +{ + "description": "Setup and configuration guide for Atlas game servers", + "name": "Atlas", + "order": 17, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/avorion/index.php b/modules/billing/docs/avorion/index.php index 1ef9d6d5..934e8e98 100644 --- a/modules/billing/docs/avorion/index.php +++ b/modules/billing/docs/avorion/index.php @@ -1,68 +1,372 @@ -Avorion is available for hosting on our platform. This guide covers the basics of setting up and managing your Avorion server.
-27000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Avorion server:
-After your server is created, you can configure it through the control panel:
+Avorion is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Avorion server for your community.
+ +Check server configurationThe Avorion server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Avorion Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Avorion Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Avorion server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Avorion Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Avorion server hosting +
diff --git a/modules/billing/docs/avorion/metadata.json b/modules/billing/docs/avorion/metadata.json index 61ccb60c..e9cd862c 100644 --- a/modules/billing/docs/avorion/metadata.json +++ b/modules/billing/docs/avorion/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Avorion game servers", - "name": "Avorion", - "order": 19, - "category": "todo" +{ + "description": "Setup and configuration guide for Avorion game servers", + "name": "Avorion", + "order": 19, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/bf2/index.php b/modules/billing/docs/bf2/index.php index f9132256..7c8886d9 100644 --- a/modules/billing/docs/bf2/index.php +++ b/modules/billing/docs/bf2/index.php @@ -1,74 +1,372 @@ -Battlefield 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Battlefield 2 server.
-16567- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Battlefield 2 server:
+Battlefield 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Battlefield 2 server for your community.
+ +Check server configurationThe Battlefield 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Battlefield 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Battlefield 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Battlefield 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]After your server is created, you can configure it through the control panel:
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+htop or topiotopUse your server's IP address and port to connect from the game client.
+# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+Popular server modifications compatible with Battlefield 2:
+If you need assistance with your Battlefield 2 server:
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Battlefield 2 server hosting +
diff --git a/modules/billing/docs/bf2/metadata.json b/modules/billing/docs/bf2/metadata.json index 5a241eaf..c3f95dae 100644 --- a/modules/billing/docs/bf2/metadata.json +++ b/modules/billing/docs/bf2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Battlefield 2 game servers", - "name": "Battlefield 2", - "order": 21, - "category": "todo" +{ + "description": "Setup and configuration guide for Battlefield 2 game servers", + "name": "Battlefield 2", + "order": 21, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/bfbc2/index.php b/modules/billing/docs/bfbc2/index.php index 36404c9e..c37686e7 100644 --- a/modules/billing/docs/bfbc2/index.php +++ b/modules/billing/docs/bfbc2/index.php @@ -1,74 +1,372 @@ -Battlefield Bad Company 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Battlefield Bad Company 2 server.
-19567- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Battlefield Bad Company 2 server:
+Battlefield Bad Company 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Battlefield Bad Company 2 server for your community.
+ +Check server configurationThe Battlefield Bad Company 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Battlefield Bad Company 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Battlefield Bad Company 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Battlefield Bad Company 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]After your server is created, you can configure it through the control panel:
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+htop or topiotopUse your server's IP address and port to connect from the game client.
+# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+Popular server modifications compatible with Battlefield Bad Company 2:
+If you need assistance with your Battlefield Bad Company 2 server:
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Battlefield Bad Company 2 server hosting +
diff --git a/modules/billing/docs/bfbc2/metadata.json b/modules/billing/docs/bfbc2/metadata.json index c1cc81a7..12bad1de 100644 --- a/modules/billing/docs/bfbc2/metadata.json +++ b/modules/billing/docs/bfbc2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Battlefield Bad Company 2 game servers", - "name": "Battlefield Bad Company 2", - "order": 23, - "category": "todo" +{ + "description": "Setup and configuration guide for Battlefield Bad Company 2 game servers", + "name": "Battlefield Bad Company 2", + "order": 23, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/bloodfrontier/index.php b/modules/billing/docs/bloodfrontier/index.php index 955231ca..2cee75c1 100644 --- a/modules/billing/docs/bloodfrontier/index.php +++ b/modules/billing/docs/bloodfrontier/index.php @@ -1,66 +1,372 @@ -Blood Frontier is available for hosting on our platform. This guide covers the basics of setting up and managing your Blood Frontier server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Blood Frontier server:
-After your server is created, you can configure it through the control panel:
+Blood Frontier is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Blood Frontier server for your community.
+ +Check server configurationThe Blood Frontier server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Blood Frontier Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Blood Frontier Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Blood Frontier server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Blood Frontier Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Blood Frontier server hosting +
diff --git a/modules/billing/docs/bloodfrontier/metadata.json b/modules/billing/docs/bloodfrontier/metadata.json index e25f0f49..0759d32b 100644 --- a/modules/billing/docs/bloodfrontier/metadata.json +++ b/modules/billing/docs/bloodfrontier/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Blood Frontier game servers", - "name": "Blood Frontier", - "order": 26, - "category": "todo" +{ + "description": "Setup and configuration guide for Blood Frontier game servers", + "name": "Blood Frontier", + "order": 26, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/brainbread2/index.php b/modules/billing/docs/brainbread2/index.php index ab269090..f65d462e 100644 --- a/modules/billing/docs/brainbread2/index.php +++ b/modules/billing/docs/brainbread2/index.php @@ -1,68 +1,381 @@ -BrainBread 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your BrainBread 2 server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a BrainBread 2 server:
-After your server is created, you can configure it through the control panel:
+BrainBread 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a BrainBread 2 server for your community.
+ +Check server configurationbrainbread2/cfg/server.cfg - Main Configuration FileThe BrainBread 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="BrainBread 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="BrainBread 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your BrainBread 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+brainbread2/cfg/server.cfg - Main Configuration FileCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=BrainBread 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For BrainBread 2 server hosting +
diff --git a/modules/billing/docs/brainbread2/metadata.json b/modules/billing/docs/brainbread2/metadata.json index 1a346c20..89fabf47 100644 --- a/modules/billing/docs/brainbread2/metadata.json +++ b/modules/billing/docs/brainbread2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for BrainBread 2 game servers", - "name": "BrainBread 2", - "order": 27, - "category": "todo" +{ + "description": "Setup and configuration guide for BrainBread 2 game servers", + "name": "BrainBread 2", + "order": 27, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/citadelfwf/index.php b/modules/billing/docs/citadelfwf/index.php index b701409a..ea93c841 100644 --- a/modules/billing/docs/citadelfwf/index.php +++ b/modules/billing/docs/citadelfwf/index.php @@ -1,66 +1,381 @@ -Citadel: Forged with Fire is available for hosting on our platform. This guide covers the basics of setting up and managing your Citadel: Forged with Fire server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Citadel: Forged with Fire server:
-After your server is created, you can configure it through the control panel:
+Citadel: Forged with Fire is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Citadel: Forged with Fire server for your community.
+ +Check server configurationCitadel/Saved/Config/WindowsServer/Game.ini - Server ConfigurationsThe Citadel: Forged with Fire server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Citadel: Forged with Fire Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Citadel: Forged with Fire Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Citadel: Forged with Fire server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+Citadel/Saved/Config/WindowsServer/Game.ini - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Citadel: Forged with Fire Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Citadel: Forged with Fire server hosting +
diff --git a/modules/billing/docs/citadelfwf/metadata.json b/modules/billing/docs/citadelfwf/metadata.json index 90786db1..14d3db63 100644 --- a/modules/billing/docs/citadelfwf/metadata.json +++ b/modules/billing/docs/citadelfwf/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Citadel: Forged with Fire game servers", - "name": "Citadel: Forged with Fire", - "order": 41, - "category": "todo" +{ + "description": "Setup and configuration guide for Citadel: Forged with Fire game servers", + "name": "Citadel: Forged with Fire", + "order": 41, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/colonysurvival/index.php b/modules/billing/docs/colonysurvival/index.php index e0a5c503..b28c7f68 100644 --- a/modules/billing/docs/colonysurvival/index.php +++ b/modules/billing/docs/colonysurvival/index.php @@ -1,68 +1,372 @@ -Colony Survival is available for hosting on our platform. This guide covers the basics of setting up and managing your Colony Survival server.
-27016- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Colony Survival server:
-After your server is created, you can configure it through the control panel:
+Colony Survival is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Colony Survival server for your community.
+ +Check server configurationThe Colony Survival server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Colony Survival Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Colony Survival Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Colony Survival server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Colony Survival Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Colony Survival server hosting +
diff --git a/modules/billing/docs/colonysurvival/metadata.json b/modules/billing/docs/colonysurvival/metadata.json index cdd192e0..24e6f067 100644 --- a/modules/billing/docs/colonysurvival/metadata.json +++ b/modules/billing/docs/colonysurvival/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Colony Survival game servers", - "name": "Colony Survival", - "order": 44, - "category": "todo" +{ + "description": "Setup and configuration guide for Colony Survival game servers", + "name": "Colony Survival", + "order": 44, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/common-issues/index.php b/modules/billing/docs/common-issues/index.php index 5dd48ea3..9aa96523 100644 --- a/modules/billing/docs/common-issues/index.php +++ b/modules/billing/docs/common-issues/index.php @@ -1,128 +1,372 @@ -Common Issues & Solutions is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Common Issues & Solutions server for your community.
+ +Check server configurationThe Common Issues & Solutions server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="{game_name} Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="{game_name} Server" dir=in action=allow protocol=UDP localport=[PORT]
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description={game_name} Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
-Symptoms
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
-File Upload Issues
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
-Mods/Plugins Not Working
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
-Symptoms
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
+If these solutions don't resolve your issue:
++ Last updated: {datetime.now().strftime("%B %Y")} | For {game_name} server hosting +
diff --git a/modules/billing/docs/common-issues/metadata.json b/modules/billing/docs/common-issues/metadata.json index 01bfab4e..40fa2d7a 100644 --- a/modules/billing/docs/common-issues/metadata.json +++ b/modules/billing/docs/common-issues/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Troubleshooting guide for common server problems", - "name": "Common Issues \u0026 Solutions", - "order": 1, - "category": "todo" +{ + "description": "Troubleshooting guide for common server problems", + "name": "Common Issues & Solutions", + "order": 1, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/cs2d/index.php b/modules/billing/docs/cs2d/index.php index 1b6c793e..4fc60886 100644 --- a/modules/billing/docs/cs2d/index.php +++ b/modules/billing/docs/cs2d/index.php @@ -1,66 +1,372 @@ -CS2D is available for hosting on our platform. This guide covers the basics of setting up and managing your CS2D server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a CS2D server:
-After your server is created, you can configure it through the control panel:
+CS2D is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a CS2D server for your community.
+ +Check server configurationThe CS2D server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="CS2D Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="CS2D Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your CS2D server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=CS2D Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For CS2D server hosting +
diff --git a/modules/billing/docs/cs2d/metadata.json b/modules/billing/docs/cs2d/metadata.json index 4fc1b12a..73f9d859 100644 --- a/modules/billing/docs/cs2d/metadata.json +++ b/modules/billing/docs/cs2d/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for CS2D game servers", - "name": "CS2D", - "order": 48, - "category": "todo" +{ + "description": "Setup and configuration guide for CS2D game servers", + "name": "CS2D", + "order": 48, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/cspromod/index.php b/modules/billing/docs/cspromod/index.php index 05e7d82b..deab8dba 100644 --- a/modules/billing/docs/cspromod/index.php +++ b/modules/billing/docs/cspromod/index.php @@ -1,68 +1,372 @@ -CSPromod is available for hosting on our platform. This guide covers the basics of setting up and managing your CSPromod server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a CSPromod server:
-After your server is created, you can configure it through the control panel:
+CSPromod is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a CSPromod server for your community.
+ +Check server configurationThe CSPromod server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="CSPromod Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="CSPromod Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your CSPromod server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=CSPromod Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For CSPromod server hosting +
diff --git a/modules/billing/docs/cspromod/metadata.json b/modules/billing/docs/cspromod/metadata.json index 7493a092..cf000115 100644 --- a/modules/billing/docs/cspromod/metadata.json +++ b/modules/billing/docs/cspromod/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for CSPromod game servers", - "name": "CSPromod", - "order": 52, - "category": "todo" +{ + "description": "Setup and configuration guide for CSPromod game servers", + "name": "CSPromod", + "order": 52, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/czero/index.php b/modules/billing/docs/czero/index.php index 07b0f717..4aafb774 100644 --- a/modules/billing/docs/czero/index.php +++ b/modules/billing/docs/czero/index.php @@ -1,68 +1,372 @@ -Counter-Strike Condition Zero is available for hosting on our platform. This guide covers the basics of setting up and managing your Counter-Strike Condition Zero server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Counter-Strike Condition Zero server:
-After your server is created, you can configure it through the control panel:
+Counter-Strike Condition Zero is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Counter-Strike Condition Zero server for your community.
+ +Check server configurationThe Counter-Strike Condition Zero server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Counter-Strike Condition Zero Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Counter-Strike Condition Zero Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Counter-Strike Condition Zero server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Counter-Strike Condition Zero Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Counter-Strike Condition Zero server hosting +
diff --git a/modules/billing/docs/czero/metadata.json b/modules/billing/docs/czero/metadata.json index a418f742..698baafb 100644 --- a/modules/billing/docs/czero/metadata.json +++ b/modules/billing/docs/czero/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Counter-Strike Condition Zero game servers", - "name": "Counter-Strike Condition Zero", - "order": 56, - "category": "todo" +{ + "description": "Setup and configuration guide for Counter-Strike Condition Zero game servers", + "name": "Counter-Strike Condition Zero", + "order": 56, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/dmc/index.php b/modules/billing/docs/dmc/index.php index 3d9d8027..e13bd3f2 100644 --- a/modules/billing/docs/dmc/index.php +++ b/modules/billing/docs/dmc/index.php @@ -1,66 +1,372 @@ -Death Match Classic is available for hosting on our platform. This guide covers the basics of setting up and managing your Death Match Classic server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Death Match Classic server:
-After your server is created, you can configure it through the control panel:
+Death Match Classic is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Death Match Classic server for your community.
+ +Check server configurationThe Death Match Classic server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Death Match Classic Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Death Match Classic Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Death Match Classic server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Death Match Classic Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Death Match Classic server hosting +
diff --git a/modules/billing/docs/dmc/metadata.json b/modules/billing/docs/dmc/metadata.json index 06916fe2..24cc382c 100644 --- a/modules/billing/docs/dmc/metadata.json +++ b/modules/billing/docs/dmc/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Death Match Classic game servers", - "name": "Death Match Classic", - "order": 64, - "category": "todo" +{ + "description": "Setup and configuration guide for Death Match Classic game servers", + "name": "Death Match Classic", + "order": 64, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/dystopia/index.php b/modules/billing/docs/dystopia/index.php index 0004626a..97460120 100644 --- a/modules/billing/docs/dystopia/index.php +++ b/modules/billing/docs/dystopia/index.php @@ -1,68 +1,419 @@ -Dystopia is available for hosting on our platform. This guide covers the basics of setting up and managing your Dystopia server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Dystopia server:
-After your server is created, you can configure it through the control panel:
+Dystopia is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Dystopia server for your community.
+ +27015| Port | +Protocol | +Purpose | +
|---|---|---|
27015 |
+ UDP | +Game/Query (can change with -port) | +
27015 |
+ TCP | +RCON | +
27020 |
+ UDP | +SourceTV (tv_port) | +
27005 |
+ UDP | +Client port (outbound/varies) | +
26900 |
+ UDP | +Steam (outbound, -sport) (Optional) | +
27031-27036 |
+ UDP | +Steam Remote Play / P2P (outbound) (Optional) | +
27036-27037 |
+ TCP | +Steam Remote Play (inbound where applicable) (Optional) | +
Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Dystopia Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Dystopia Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
- -Use your server's IP address and port to connect from the game client.
- -Access your server files via FTP using the credentials provided in your control panel.
- -If you need assistance with your Dystopia server:
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+./srcds_run -console -game dystopia -ip 0.0.0.0 -port 27015 +map dys_broadcast +maxplayers 24 +exec server.cfg
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+./srcds_run -console -game dystopia -ip 0.0.0.0 -port 27015 +map dys_broadcast +maxplayers 24 +exec server.cfg
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Dystopia Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+Open 27015/udp and 27015/tcp; check -ip/-port; ensure sv_lan 0; verify external firewall/NAT.
+ +Ensure -authkey is present; server has internet access; use +host_workshop_collection and +workshop_start_map or fall back to FastDL.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Dystopia server hosting +
diff --git a/modules/billing/docs/dystopia/metadata.json b/modules/billing/docs/dystopia/metadata.json index ede42f39..7e902960 100644 --- a/modules/billing/docs/dystopia/metadata.json +++ b/modules/billing/docs/dystopia/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Dystopia game servers", - "name": "Dystopia", - "order": 73, - "category": "todo" +{ + "description": "Setup and configuration guide for Dystopia game servers", + "name": "Dystopia", + "order": 73, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/eco/index.php b/modules/billing/docs/eco/index.php index 6f48cc1f..22719c91 100644 --- a/modules/billing/docs/eco/index.php +++ b/modules/billing/docs/eco/index.php @@ -1,68 +1,372 @@ -Eco is available for hosting on our platform. This guide covers the basics of setting up and managing your Eco server.
-3000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Eco server:
-After your server is created, you can configure it through the control panel:
+Eco is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Eco server for your community.
+ +Check server configurationThe Eco server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Eco Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Eco Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Eco server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Eco Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Eco server hosting +
diff --git a/modules/billing/docs/eco/metadata.json b/modules/billing/docs/eco/metadata.json index 9f77e096..2c1fa805 100644 --- a/modules/billing/docs/eco/metadata.json +++ b/modules/billing/docs/eco/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Eco game servers", - "name": "Eco", - "order": 74, - "category": "todo" +{ + "description": "Setup and configuration guide for Eco game servers", + "name": "Eco", + "order": 74, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/empyriongs/index.php b/modules/billing/docs/empyriongs/index.php index 3a8c0ab2..cd559d64 100644 --- a/modules/billing/docs/empyriongs/index.php +++ b/modules/billing/docs/empyriongs/index.php @@ -1,68 +1,383 @@ -Empyrion is available for hosting on our platform. This guide covers the basics of setting up and managing your Empyrion server.
-30000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Empyrion server:
-After your server is created, you can configure it through the control panel:
+Empyrion is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Empyrion server for your community.
+ +Check server configurationdedicated.yaml - Server ConfigurationsSaves/adminconfig.example.yaml - Admin ConfigurationsThe Empyrion server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Empyrion Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Empyrion Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Empyrion server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+dedicated.yaml - Server ConfigurationsSaves/adminconfig.example.yaml - Admin ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Empyrion Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Empyrion server hosting +
diff --git a/modules/billing/docs/empyriongs/metadata.json b/modules/billing/docs/empyriongs/metadata.json index c52507ba..8dd24049 100644 --- a/modules/billing/docs/empyriongs/metadata.json +++ b/modules/billing/docs/empyriongs/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Empyrion game servers", - "name": "Empyrion", - "order": 75, - "category": "todo" +{ + "description": "Setup and configuration guide for Empyrion game servers", + "name": "Empyrion", + "order": 75, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/enemyterritory/index.php b/modules/billing/docs/enemyterritory/index.php index 1fd13cca..a26edf0c 100644 --- a/modules/billing/docs/enemyterritory/index.php +++ b/modules/billing/docs/enemyterritory/index.php @@ -1,68 +1,385 @@ -Wolfenstein: Enemy Territory is available for hosting on our platform. This guide covers the basics of setting up and managing your Wolfenstein: Enemy Territory server.
-27960- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Wolfenstein: Enemy Territory server:
-After your server is created, you can configure it through the control panel:
+Wolfenstein: Enemy Territory is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Wolfenstein: Enemy Territory server for your community.
+ +27960| Port | +Protocol | +Purpose | +
|---|---|---|
27960 |
+ UDP | +Game/Query (set with +set net_port) | +
Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Wolfenstein: Enemy Territory Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Wolfenstein: Enemy Territory Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
- -Use your server's IP address and port to connect from the game client.
- -Access your server files via FTP using the credentials provided in your control panel.
- -If you need assistance with your Wolfenstein: Enemy Territory server:
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+./etlded +set dedicated 2 +set net_port 27960 +set fs_game legacy +exec server.cfg
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+./etlded +set dedicated 2 +set net_port 27960 +set fs_game legacy +exec server.cfg
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Wolfenstein: Enemy Territory Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+Forward UDP 27960; set dedicated 2; verify master server reachability; avoid NAT loopback issues.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Wolfenstein: Enemy Territory server hosting +
diff --git a/modules/billing/docs/enemyterritory/metadata.json b/modules/billing/docs/enemyterritory/metadata.json index acdce4c9..94f74749 100644 --- a/modules/billing/docs/enemyterritory/metadata.json +++ b/modules/billing/docs/enemyterritory/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Wolfenstein: Enemy Territory game servers", - "name": "Wolfenstein: Enemy Territory", - "order": 142, - "category": "todo" +{ + "description": "Setup and configuration guide for Wolfenstein: Enemy Territory game servers", + "name": "Wolfenstein: Enemy Territory", + "order": 142, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/esmod/index.php b/modules/billing/docs/esmod/index.php index 4f2bb32d..6d3a5164 100644 --- a/modules/billing/docs/esmod/index.php +++ b/modules/billing/docs/esmod/index.php @@ -1,66 +1,372 @@ -Eternal-Silence is available for hosting on our platform. This guide covers the basics of setting up and managing your Eternal-Silence server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Eternal-Silence server:
-After your server is created, you can configure it through the control panel:
+Eternal-Silence is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Eternal-Silence server for your community.
+ +Check server configurationThe Eternal-Silence server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Eternal-Silence Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Eternal-Silence Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Eternal-Silence server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Eternal-Silence Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Eternal-Silence server hosting +
diff --git a/modules/billing/docs/esmod/metadata.json b/modules/billing/docs/esmod/metadata.json index d203c612..9e1700d2 100644 --- a/modules/billing/docs/esmod/metadata.json +++ b/modules/billing/docs/esmod/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Eternal-Silence game servers", - "name": "Eternal-Silence", - "order": 76, - "category": "todo" +{ + "description": "Setup and configuration guide for Eternal-Silence game servers", + "name": "Eternal-Silence", + "order": 76, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ets2/index.php b/modules/billing/docs/ets2/index.php index e3cc1610..6e6d839f 100644 --- a/modules/billing/docs/ets2/index.php +++ b/modules/billing/docs/ets2/index.php @@ -1,68 +1,383 @@ -Euro Truck Simulator 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Euro Truck Simulator 2 server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Euro Truck Simulator 2 server:
-After your server is created, you can configure it through the control panel:
+Euro Truck Simulator 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Euro Truck Simulator 2 server for your community.
+ +Check server configurationEuro Truck Simulator 2/server_config.sii - configure serverEuro Truck Simulator 2/server_packages.sii - Advanced ModificationsThe Euro Truck Simulator 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Euro Truck Simulator 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Euro Truck Simulator 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Euro Truck Simulator 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+Euro Truck Simulator 2/server_config.sii - configure serverEuro Truck Simulator 2/server_packages.sii - Advanced ModificationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Euro Truck Simulator 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Euro Truck Simulator 2 server hosting +
diff --git a/modules/billing/docs/ets2/metadata.json b/modules/billing/docs/ets2/metadata.json index b52b4824..37c4a434 100644 --- a/modules/billing/docs/ets2/metadata.json +++ b/modules/billing/docs/ets2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Euro Truck Simulator 2 game servers", - "name": "Euro Truck Simulator 2", - "order": 77, - "category": "todo" +{ + "description": "Setup and configuration guide for Euro Truck Simulator 2 game servers", + "name": "Euro Truck Simulator 2", + "order": 77, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/feedthebeast/index.php b/modules/billing/docs/feedthebeast/index.php index f01b2951..97d08bed 100644 --- a/modules/billing/docs/feedthebeast/index.php +++ b/modules/billing/docs/feedthebeast/index.php @@ -1,68 +1,372 @@ -Feed The Beast Server is available for hosting on our platform. This guide covers the basics of setting up and managing your Feed The Beast Server server.
-25565- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Feed The Beast Server server:
-After your server is created, you can configure it through the control panel:
+Feed The Beast Server is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Feed The Beast Server server for your community.
+ +Check server configurationThe Feed The Beast Server server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Feed The Beast Server Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Feed The Beast Server Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Feed The Beast Server server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Feed The Beast Server Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Feed The Beast Server server hosting +
diff --git a/modules/billing/docs/feedthebeast/metadata.json b/modules/billing/docs/feedthebeast/metadata.json index 7377e57f..4b19732c 100644 --- a/modules/billing/docs/feedthebeast/metadata.json +++ b/modules/billing/docs/feedthebeast/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Feed The Beast Server game servers", - "name": "Feed The Beast Server", - "order": 79, - "category": "todo" +{ + "description": "Setup and configuration guide for Feed The Beast Server game servers", + "name": "Feed The Beast Server", + "order": 79, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/fgms/index.php b/modules/billing/docs/fgms/index.php index 3608ebb8..603ce192 100644 --- a/modules/billing/docs/fgms/index.php +++ b/modules/billing/docs/fgms/index.php @@ -1,66 +1,372 @@ -FlightGear Multiplayer Server is available for hosting on our platform. This guide covers the basics of setting up and managing your FlightGear Multiplayer Server server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a FlightGear Multiplayer Server server:
-After your server is created, you can configure it through the control panel:
+FlightGear Multiplayer Server is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a FlightGear Multiplayer Server server for your community.
+ +Check server configurationThe FlightGear Multiplayer Server server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="FlightGear Multiplayer Server Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="FlightGear Multiplayer Server Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your FlightGear Multiplayer Server server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=FlightGear Multiplayer Server Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For FlightGear Multiplayer Server server hosting +
diff --git a/modules/billing/docs/fgms/metadata.json b/modules/billing/docs/fgms/metadata.json index f9075cf7..84d1b0ad 100644 --- a/modules/billing/docs/fgms/metadata.json +++ b/modules/billing/docs/fgms/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for FlightGear Multiplayer Server game servers", - "name": "FlightGear Multiplayer Server", - "order": 81, - "category": "todo" +{ + "description": "Setup and configuration guide for FlightGear Multiplayer Server game servers", + "name": "FlightGear Multiplayer Server", + "order": 81, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/fivem/index.php b/modules/billing/docs/fivem/index.php index a83df1ec..ae82237e 100644 --- a/modules/billing/docs/fivem/index.php +++ b/modules/billing/docs/fivem/index.php @@ -1,68 +1,381 @@ -FiveM is available for hosting on our platform. This guide covers the basics of setting up and managing your FiveM server.
-30120- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a FiveM server:
-After your server is created, you can configure it through the control panel:
+FiveM is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a FiveM server for your community.
+ +Check server configurationserver.cfg - Main Config FileThe FiveM server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="FiveM Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="FiveM Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your FiveM server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+server.cfg - Main Config FileCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=FiveM Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For FiveM server hosting +
diff --git a/modules/billing/docs/fivem/metadata.json b/modules/billing/docs/fivem/metadata.json index 6d1f3fba..8012b00f 100644 --- a/modules/billing/docs/fivem/metadata.json +++ b/modules/billing/docs/fivem/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for FiveM game servers", - "name": "FiveM", - "order": 84, - "category": "todo" +{ + "description": "Setup and configuration guide for FiveM game servers", + "name": "FiveM", + "order": 84, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/freecol/index.php b/modules/billing/docs/freecol/index.php index 8f0e9cf8..78a252e5 100644 --- a/modules/billing/docs/freecol/index.php +++ b/modules/billing/docs/freecol/index.php @@ -1,66 +1,372 @@ -FreeCol is available for hosting on our platform. This guide covers the basics of setting up and managing your FreeCol server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a FreeCol server:
-After your server is created, you can configure it through the control panel:
+FreeCol is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a FreeCol server for your community.
+ +Check server configurationThe FreeCol server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="FreeCol Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="FreeCol Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your FreeCol server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=FreeCol Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For FreeCol server hosting +
diff --git a/modules/billing/docs/freecol/metadata.json b/modules/billing/docs/freecol/metadata.json index 2f4d62ed..acc75d6e 100644 --- a/modules/billing/docs/freecol/metadata.json +++ b/modules/billing/docs/freecol/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for FreeCol game servers", - "name": "FreeCol", - "order": 86, - "category": "todo" +{ + "description": "Setup and configuration guide for FreeCol game servers", + "name": "FreeCol", + "order": 86, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/gearbox/index.php b/modules/billing/docs/gearbox/index.php index 21b370d4..561596c6 100644 --- a/modules/billing/docs/gearbox/index.php +++ b/modules/billing/docs/gearbox/index.php @@ -1,66 +1,372 @@ -Gearbox is available for hosting on our platform. This guide covers the basics of setting up and managing your Gearbox server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Gearbox server:
-After your server is created, you can configure it through the control panel:
+Gearbox is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Gearbox server for your community.
+ +Check server configurationThe Gearbox server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Gearbox Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Gearbox Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Gearbox server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Gearbox Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Gearbox server hosting +
diff --git a/modules/billing/docs/gearbox/metadata.json b/modules/billing/docs/gearbox/metadata.json index e558bcb1..a78c2d0e 100644 --- a/modules/billing/docs/gearbox/metadata.json +++ b/modules/billing/docs/gearbox/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Gearbox game servers", - "name": "Gearbox", - "order": 0, - "category": "todo" +{ + "description": "Setup and configuration guide for Gearbox game servers", + "name": "Gearbox", + "order": 0, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/halo_ce/index.php b/modules/billing/docs/halo_ce/index.php index b2950467..c92a8405 100644 --- a/modules/billing/docs/halo_ce/index.php +++ b/modules/billing/docs/halo_ce/index.php @@ -1,66 +1,372 @@ -Halo CE is available for hosting on our platform. This guide covers the basics of setting up and managing your Halo CE server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Halo CE server:
-After your server is created, you can configure it through the control panel:
+Halo CE is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Halo CE server for your community.
+ +Check server configurationThe Halo CE server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Halo CE Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Halo CE Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Halo CE server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Halo CE Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Halo CE server hosting +
diff --git a/modules/billing/docs/halo_ce/metadata.json b/modules/billing/docs/halo_ce/metadata.json index 7a8ad5d2..907477e1 100644 --- a/modules/billing/docs/halo_ce/metadata.json +++ b/modules/billing/docs/halo_ce/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Halo CE game servers", - "name": "Halo CE", - "order": 1, - "category": "todo" +{ + "description": "Setup and configuration guide for Halo CE game servers", + "name": "Halo CE", + "order": 1, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/harsh/index.php b/modules/billing/docs/harsh/index.php index 285e79cf..4fb335eb 100644 --- a/modules/billing/docs/harsh/index.php +++ b/modules/billing/docs/harsh/index.php @@ -1,66 +1,387 @@ -Operation Harsh Doorstop is available for hosting on our platform. This guide covers the basics of setting up and managing your Operation Harsh Doorstop server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Operation Harsh Doorstop server:
-After your server is created, you can configure it through the control panel:
+Operation Harsh Doorstop is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Operation Harsh Doorstop server for your community.
+ +Check server configuration\HarshDoorstop\Saved\Config\WindowsServer\game.ini - Game.ini\HarshDoorstop\Saved\Config\WindowsServer\engine.ini - Engine.ini\HarshDoorstop\Saved\Config\WindowsServer\mapcycle.cfg - Mapcycle.cfg\HarshDoorstop\Saved\Config\WindowsServer\admins.cfg - Admins.cfgThe Operation Harsh Doorstop server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Operation Harsh Doorstop Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Operation Harsh Doorstop Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Operation Harsh Doorstop server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+\HarshDoorstop\Saved\Config\WindowsServer\game.ini - Game.ini\HarshDoorstop\Saved\Config\WindowsServer\engine.ini - Engine.ini\HarshDoorstop\Saved\Config\WindowsServer\mapcycle.cfg - Mapcycle.cfg\HarshDoorstop\Saved\Config\WindowsServer\admins.cfg - Admins.cfgCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Operation Harsh Doorstop Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Operation Harsh Doorstop server hosting +
diff --git a/modules/billing/docs/harsh/metadata.json b/modules/billing/docs/harsh/metadata.json index 76fc104f..3768984b 100644 --- a/modules/billing/docs/harsh/metadata.json +++ b/modules/billing/docs/harsh/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Operation Harsh Doorstop game servers", - "name": "Operation Harsh Doorstop", - "order": 2, - "category": "todo" +{ + "description": "Setup and configuration guide for Operation Harsh Doorstop game servers", + "name": "Operation Harsh Doorstop", + "order": 2, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/hidden_source/index.php b/modules/billing/docs/hidden_source/index.php index 6d6588df..d7bc1ff1 100644 --- a/modules/billing/docs/hidden_source/index.php +++ b/modules/billing/docs/hidden_source/index.php @@ -1,68 +1,372 @@ -Hidden: Source is available for hosting on our platform. This guide covers the basics of setting up and managing your Hidden: Source server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Hidden: Source server:
-After your server is created, you can configure it through the control panel:
+Hidden: Source is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Hidden: Source server for your community.
+ +Check server configurationThe Hidden: Source server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Hidden: Source Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Hidden: Source Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Hidden: Source server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Hidden: Source Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Hidden: Source server hosting +
diff --git a/modules/billing/docs/hidden_source/metadata.json b/modules/billing/docs/hidden_source/metadata.json index a256e3d0..7a0ba23a 100644 --- a/modules/billing/docs/hidden_source/metadata.json +++ b/modules/billing/docs/hidden_source/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Hidden: Source game servers", - "name": "Hidden: Source", - "order": 4, - "category": "todo" +{ + "description": "Setup and configuration guide for Hidden: Source game servers", + "name": "Hidden: Source", + "order": 4, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/hl2d/index.php b/modules/billing/docs/hl2d/index.php index 039f2113..6d7f66fb 100644 --- a/modules/billing/docs/hl2d/index.php +++ b/modules/billing/docs/hl2d/index.php @@ -1,68 +1,419 @@ -Half-Life 2: Deathmatch is available for hosting on our platform. This guide covers the basics of setting up and managing your Half-Life 2: Deathmatch server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Half-Life 2: Deathmatch server:
-After your server is created, you can configure it through the control panel:
+Half-Life 2: Deathmatch is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Half-Life 2: Deathmatch server for your community.
+ +27015| Port | +Protocol | +Purpose | +
|---|---|---|
27015 |
+ UDP | +Game/Query (can change with -port) | +
27015 |
+ TCP | +RCON | +
27020 |
+ UDP | +SourceTV (tv_port) | +
27005 |
+ UDP | +Client port (outbound/varies) | +
26900 |
+ UDP | +Steam (outbound, -sport) (Optional) | +
27031-27036 |
+ UDP | +Steam Remote Play / P2P (outbound) (Optional) | +
27036-27037 |
+ TCP | +Steam Remote Play (inbound where applicable) (Optional) | +
Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Half-Life 2: Deathmatch Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Half-Life 2: Deathmatch Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
- -Use your server's IP address and port to connect from the game client.
- -Access your server files via FTP using the credentials provided in your control panel.
- -If you need assistance with your Half-Life 2: Deathmatch server:
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+./srcds_run -console -game hl2mp -ip 0.0.0.0 -port 27015 +map dm_lockdown +maxplayers 24 +exec server.cfg
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+./srcds_run -console -game hl2mp -ip 0.0.0.0 -port 27015 +map dm_lockdown +maxplayers 24 +exec server.cfg
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Half-Life 2: Deathmatch Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+Open 27015/udp and 27015/tcp; check -ip/-port; ensure sv_lan 0; verify external firewall/NAT.
+ +Ensure -authkey is present; server has internet access; use +host_workshop_collection and +workshop_start_map or fall back to FastDL.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Half-Life 2: Deathmatch server hosting +
diff --git a/modules/billing/docs/hl2d/metadata.json b/modules/billing/docs/hl2d/metadata.json index f7c585df..abed0701 100644 --- a/modules/billing/docs/hl2d/metadata.json +++ b/modules/billing/docs/hl2d/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Half-Life 2: Deathmatch game servers", - "name": "Half-Life 2: Deathmatch", - "order": 5, - "category": "todo" +{ + "description": "Setup and configuration guide for Half-Life 2: Deathmatch game servers", + "name": "Half-Life 2: Deathmatch", + "order": 5, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/hldm/index.php b/modules/billing/docs/hldm/index.php index e96f54cf..dcc6bffc 100644 --- a/modules/billing/docs/hldm/index.php +++ b/modules/billing/docs/hldm/index.php @@ -1,68 +1,372 @@ -Half Life: Death Match is available for hosting on our platform. This guide covers the basics of setting up and managing your Half Life: Death Match server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Half Life: Death Match server:
-After your server is created, you can configure it through the control panel:
+Half Life: Death Match is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Half Life: Death Match server for your community.
+ +Check server configurationThe Half Life: Death Match server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Half Life: Death Match Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Half Life: Death Match Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Half Life: Death Match server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Half Life: Death Match Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Half Life: Death Match server hosting +
diff --git a/modules/billing/docs/hldm/metadata.json b/modules/billing/docs/hldm/metadata.json index 9adcc7d3..ed79e5f0 100644 --- a/modules/billing/docs/hldm/metadata.json +++ b/modules/billing/docs/hldm/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Half Life: Death Match game servers", - "name": "Half Life: Death Match", - "order": 7, - "category": "todo" +{ + "description": "Setup and configuration guide for Half Life: Death Match game servers", + "name": "Half Life: Death Match", + "order": 7, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/hltv/index.php b/modules/billing/docs/hltv/index.php index f57a5a89..7339eb96 100644 --- a/modules/billing/docs/hltv/index.php +++ b/modules/billing/docs/hltv/index.php @@ -1,66 +1,372 @@ -HLTV is available for hosting on our platform. This guide covers the basics of setting up and managing your HLTV server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a HLTV server:
-After your server is created, you can configure it through the control panel:
+HLTV is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a HLTV server for your community.
+ +Check server configurationThe HLTV server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="HLTV Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="HLTV Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your HLTV server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=HLTV Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For HLTV server hosting +
diff --git a/modules/billing/docs/hltv/metadata.json b/modules/billing/docs/hltv/metadata.json index 4c0ff749..d6e82c4f 100644 --- a/modules/billing/docs/hltv/metadata.json +++ b/modules/billing/docs/hltv/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for HLTV game servers", - "name": "HLTV", - "order": 9, - "category": "todo" +{ + "description": "Setup and configuration guide for HLTV game servers", + "name": "HLTV", + "order": 9, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/homefront/index.php b/modules/billing/docs/homefront/index.php index 467cfc93..0544d9b3 100644 --- a/modules/billing/docs/homefront/index.php +++ b/modules/billing/docs/homefront/index.php @@ -1,66 +1,381 @@ -Homefront is available for hosting on our platform. This guide covers the basics of setting up and managing your Homefront server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Homefront server:
-After your server is created, you can configure it through the control panel:
+Homefront is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Homefront server for your community.
+ +Check server configurationGCGame/Config/DedicatedProfile_DefaultProfile/DedicatedPlaylist - Server ConfigurationsThe Homefront server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Homefront Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Homefront Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Homefront server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+GCGame/Config/DedicatedProfile_DefaultProfile/DedicatedPlaylist - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Homefront Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Homefront server hosting +
diff --git a/modules/billing/docs/homefront/metadata.json b/modules/billing/docs/homefront/metadata.json index b09acedc..6bdc8397 100644 --- a/modules/billing/docs/homefront/metadata.json +++ b/modules/billing/docs/homefront/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Homefront game servers", - "name": "Homefront", - "order": 10, - "category": "todo" +{ + "description": "Setup and configuration guide for Homefront game servers", + "name": "Homefront", + "order": 10, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/hurtworld/index.php b/modules/billing/docs/hurtworld/index.php index 948a5809..87414dc6 100644 --- a/modules/billing/docs/hurtworld/index.php +++ b/modules/billing/docs/hurtworld/index.php @@ -1,68 +1,381 @@ -Hurtworld is available for hosting on our platform. This guide covers the basics of setting up and managing your Hurtworld server.
-12871- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Hurtworld server:
-After your server is created, you can configure it through the control panel:
+Hurtworld is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Hurtworld server for your community.
+ +Check server configurationautoexec.cfg - Server ConfigurationsThe Hurtworld server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Hurtworld Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Hurtworld Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Hurtworld server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+autoexec.cfg - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Hurtworld Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Hurtworld server hosting +
diff --git a/modules/billing/docs/hurtworld/metadata.json b/modules/billing/docs/hurtworld/metadata.json index 29fe3a8e..293e56f1 100644 --- a/modules/billing/docs/hurtworld/metadata.json +++ b/modules/billing/docs/hurtworld/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Hurtworld game servers", - "name": "Hurtworld", - "order": 11, - "category": "todo" +{ + "description": "Setup and configuration guide for Hurtworld game servers", + "name": "Hurtworld", + "order": 11, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/il2/index.php b/modules/billing/docs/il2/index.php index e30c057e..bd1cc4bf 100644 --- a/modules/billing/docs/il2/index.php +++ b/modules/billing/docs/il2/index.php @@ -1,66 +1,372 @@ -IL-2 Sturmovik is available for hosting on our platform. This guide covers the basics of setting up and managing your IL-2 Sturmovik server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a IL-2 Sturmovik server:
-After your server is created, you can configure it through the control panel:
+IL-2 Sturmovik is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a IL-2 Sturmovik server for your community.
+ +Check server configurationThe IL-2 Sturmovik server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="IL-2 Sturmovik Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="IL-2 Sturmovik Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your IL-2 Sturmovik server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=IL-2 Sturmovik Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For IL-2 Sturmovik server hosting +
diff --git a/modules/billing/docs/il2/metadata.json b/modules/billing/docs/il2/metadata.json index f351be2f..36f7901b 100644 --- a/modules/billing/docs/il2/metadata.json +++ b/modules/billing/docs/il2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for IL-2 Sturmovik game servers", - "name": "IL-2 Sturmovik", - "order": 14, - "category": "todo" +{ + "description": "Setup and configuration guide for IL-2 Sturmovik game servers", + "name": "IL-2 Sturmovik", + "order": 14, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ins/index.php b/modules/billing/docs/ins/index.php index 5635472d..20d0ca12 100644 --- a/modules/billing/docs/ins/index.php +++ b/modules/billing/docs/ins/index.php @@ -1,68 +1,419 @@ -Insurgency is available for hosting on our platform. This guide covers the basics of setting up and managing your Insurgency server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Insurgency server:
-After your server is created, you can configure it through the control panel:
+Insurgency is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Insurgency server for your community.
+ +27015| Port | +Protocol | +Purpose | +
|---|---|---|
27015 |
+ UDP | +Game/Query (can change with -port) | +
27015 |
+ TCP | +RCON | +
27020 |
+ UDP | +SourceTV (tv_port) | +
27005 |
+ UDP | +Client port (outbound/varies) | +
26900 |
+ UDP | +Steam (outbound, -sport) (Optional) | +
27031-27036 |
+ UDP | +Steam Remote Play / P2P (outbound) (Optional) | +
27036-27037 |
+ TCP | +Steam Remote Play (inbound where applicable) (Optional) | +
Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Insurgency Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Insurgency Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
- -Use your server's IP address and port to connect from the game client.
- -Access your server files via FTP using the credentials provided in your control panel.
- -If you need assistance with your Insurgency server:
+# Update system packages
+sudo apt update && sudo apt upgrade -y
+
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
+
+# Download server files (method varies by game)
+# Check official documentation for download links
+./srcds_run -console -game insurgency -ip 0.0.0.0 -port 27015 +map sinjar +maxplayers 24 +exec server.cfg
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+./srcds_run -console -game insurgency -ip 0.0.0.0 -port 27015 +map sinjar +maxplayers 24 +exec server.cfg
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Insurgency Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+Open 27015/udp and 27015/tcp; check -ip/-port; ensure sv_lan 0; verify external firewall/NAT.
+ +Ensure -authkey is present; server has internet access; use +host_workshop_collection and +workshop_start_map or fall back to FastDL.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Insurgency server hosting +
diff --git a/modules/billing/docs/ins/metadata.json b/modules/billing/docs/ins/metadata.json index f28af164..04630098 100644 --- a/modules/billing/docs/ins/metadata.json +++ b/modules/billing/docs/ins/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Insurgency game servers", - "name": "Insurgency", - "order": 15, - "category": "todo" +{ + "description": "Setup and configuration guide for Insurgency game servers", + "name": "Insurgency", + "order": 15, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ivmp/index.php b/modules/billing/docs/ivmp/index.php index 16410495..bad3d1df 100644 --- a/modules/billing/docs/ivmp/index.php +++ b/modules/billing/docs/ivmp/index.php @@ -1,66 +1,372 @@ -IV Multiplayer is available for hosting on our platform. This guide covers the basics of setting up and managing your IV Multiplayer server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a IV Multiplayer server:
-After your server is created, you can configure it through the control panel:
+IV Multiplayer is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a IV Multiplayer server for your community.
+ +Check server configurationThe IV Multiplayer server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="IV Multiplayer Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="IV Multiplayer Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your IV Multiplayer server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=IV Multiplayer Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For IV Multiplayer server hosting +
diff --git a/modules/billing/docs/ivmp/metadata.json b/modules/billing/docs/ivmp/metadata.json index 690b816c..6a087962 100644 --- a/modules/billing/docs/ivmp/metadata.json +++ b/modules/billing/docs/ivmp/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for IV Multiplayer game servers", - "name": "IV Multiplayer", - "order": 19, - "category": "todo" +{ + "description": "Setup and configuration guide for IV Multiplayer game servers", + "name": "IV Multiplayer", + "order": 19, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/jcmp/index.php b/modules/billing/docs/jcmp/index.php index 269bd350..73b628a6 100644 --- a/modules/billing/docs/jcmp/index.php +++ b/modules/billing/docs/jcmp/index.php @@ -1,68 +1,372 @@ -Just Cause 2 Multiplayer is available for hosting on our platform. This guide covers the basics of setting up and managing your Just Cause 2 Multiplayer server.
-7777- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Just Cause 2 Multiplayer server:
-After your server is created, you can configure it through the control panel:
+Just Cause 2 Multiplayer is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Just Cause 2 Multiplayer server for your community.
+ +Check server configurationThe Just Cause 2 Multiplayer server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Just Cause 2 Multiplayer Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Just Cause 2 Multiplayer Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Just Cause 2 Multiplayer server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Just Cause 2 Multiplayer Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Just Cause 2 Multiplayer server hosting +
diff --git a/modules/billing/docs/jcmp/metadata.json b/modules/billing/docs/jcmp/metadata.json index 985efc97..aa6a006d 100644 --- a/modules/billing/docs/jcmp/metadata.json +++ b/modules/billing/docs/jcmp/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Just Cause 2 Multiplayer game servers", - "name": "Just Cause 2 Multiplayer", - "order": 21, - "category": "todo" +{ + "description": "Setup and configuration guide for Just Cause 2 Multiplayer game servers", + "name": "Just Cause 2 Multiplayer", + "order": 21, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/jediknight2/index.php b/modules/billing/docs/jediknight2/index.php index bc88fab1..080c7a2c 100644 --- a/modules/billing/docs/jediknight2/index.php +++ b/modules/billing/docs/jediknight2/index.php @@ -1,66 +1,372 @@ -Jedi Knight 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Jedi Knight 2 server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Jedi Knight 2 server:
-After your server is created, you can configure it through the control panel:
+Jedi Knight 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Jedi Knight 2 server for your community.
+ +Check server configurationThe Jedi Knight 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Jedi Knight 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Jedi Knight 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Jedi Knight 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Jedi Knight 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Jedi Knight 2 server hosting +
diff --git a/modules/billing/docs/jediknight2/metadata.json b/modules/billing/docs/jediknight2/metadata.json index 84b143b9..a12d40f4 100644 --- a/modules/billing/docs/jediknight2/metadata.json +++ b/modules/billing/docs/jediknight2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Jedi Knight 2 game servers", - "name": "Jedi Knight 2", - "order": 23, - "category": "todo" +{ + "description": "Setup and configuration guide for Jedi Knight 2 game servers", + "name": "Jedi Knight 2", + "order": 23, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/jediknightja/index.php b/modules/billing/docs/jediknightja/index.php index 580c77fc..84a5abee 100644 --- a/modules/billing/docs/jediknightja/index.php +++ b/modules/billing/docs/jediknightja/index.php @@ -1,66 +1,372 @@ -Jedi Knight: Jedi Academy is available for hosting on our platform. This guide covers the basics of setting up and managing your Jedi Knight: Jedi Academy server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Jedi Knight: Jedi Academy server:
-After your server is created, you can configure it through the control panel:
+Jedi Knight: Jedi Academy is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Jedi Knight: Jedi Academy server for your community.
+ +Check server configurationThe Jedi Knight: Jedi Academy server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Jedi Knight: Jedi Academy Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Jedi Knight: Jedi Academy Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Jedi Knight: Jedi Academy server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Jedi Knight: Jedi Academy Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Jedi Knight: Jedi Academy server hosting +
diff --git a/modules/billing/docs/jediknightja/metadata.json b/modules/billing/docs/jediknightja/metadata.json index 7847a7dc..37cbb61b 100644 --- a/modules/billing/docs/jediknightja/metadata.json +++ b/modules/billing/docs/jediknightja/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Jedi Knight: Jedi Academy game servers", - "name": "Jedi Knight: Jedi Academy", - "order": 24, - "category": "todo" +{ + "description": "Setup and configuration guide for Jedi Knight: Jedi Academy game servers", + "name": "Jedi Knight: Jedi Academy", + "order": 24, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/lifeisfeudal/index.php b/modules/billing/docs/lifeisfeudal/index.php index c32522de..5a71217c 100644 --- a/modules/billing/docs/lifeisfeudal/index.php +++ b/modules/billing/docs/lifeisfeudal/index.php @@ -1,68 +1,372 @@ -Life is Feudal is available for hosting on our platform. This guide covers the basics of setting up and managing your Life is Feudal server.
-28000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Life is Feudal server:
-After your server is created, you can configure it through the control panel:
+Life is Feudal is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Life is Feudal server for your community.
+ +Check server configurationThe Life is Feudal server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Life is Feudal Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Life is Feudal Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Life is Feudal server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Life is Feudal Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Life is Feudal server hosting +
diff --git a/modules/billing/docs/lifeisfeudal/metadata.json b/modules/billing/docs/lifeisfeudal/metadata.json index 9d2805f0..efaf531f 100644 --- a/modules/billing/docs/lifeisfeudal/metadata.json +++ b/modules/billing/docs/lifeisfeudal/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Life is Feudal game servers", - "name": "Life is Feudal", - "order": 32, - "category": "todo" +{ + "description": "Setup and configuration guide for Life is Feudal game servers", + "name": "Life is Feudal", + "order": 32, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mab_warband/index.php b/modules/billing/docs/mab_warband/index.php index 1e08d6e3..70b524c6 100644 --- a/modules/billing/docs/mab_warband/index.php +++ b/modules/billing/docs/mab_warband/index.php @@ -1,68 +1,372 @@ -Mount and Blade Warband is available for hosting on our platform. This guide covers the basics of setting up and managing your Mount and Blade Warband server.
-7240- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Mount and Blade Warband server:
-After your server is created, you can configure it through the control panel:
+Mount and Blade Warband is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Mount and Blade Warband server for your community.
+ +Check server configurationThe Mount and Blade Warband server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Mount and Blade Warband Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Mount and Blade Warband Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Mount and Blade Warband server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Mount and Blade Warband Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Mount and Blade Warband server hosting +
diff --git a/modules/billing/docs/mab_warband/metadata.json b/modules/billing/docs/mab_warband/metadata.json index ebb70f46..84f4f551 100644 --- a/modules/billing/docs/mab_warband/metadata.json +++ b/modules/billing/docs/mab_warband/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Mount and Blade Warband game servers", - "name": "Mount and Blade Warband", - "order": 47, - "category": "todo" +{ + "description": "Setup and configuration guide for Mount and Blade Warband game servers", + "name": "Mount and Blade Warband", + "order": 47, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mafia2online/index.php b/modules/billing/docs/mafia2online/index.php index a48c1dbf..8a7926a6 100644 --- a/modules/billing/docs/mafia2online/index.php +++ b/modules/billing/docs/mafia2online/index.php @@ -1,66 +1,381 @@ -Mafia 2 Online is available for hosting on our platform. This guide covers the basics of setting up and managing your Mafia 2 Online server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Mafia 2 Online server:
-After your server is created, you can configure it through the control panel:
+Mafia 2 Online is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Mafia 2 Online server for your community.
+ +Check server configurationconfig.xml - Server ConfigurationsThe Mafia 2 Online server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Mafia 2 Online Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Mafia 2 Online Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Mafia 2 Online server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+config.xml - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Mafia 2 Online Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Mafia 2 Online server hosting +
diff --git a/modules/billing/docs/mafia2online/metadata.json b/modules/billing/docs/mafia2online/metadata.json index 00633b36..7c9cb94f 100644 --- a/modules/billing/docs/mafia2online/metadata.json +++ b/modules/billing/docs/mafia2online/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Mafia 2 Online game servers", - "name": "Mafia 2 Online", - "order": 33, - "category": "todo" +{ + "description": "Setup and configuration guide for Mafia 2 Online game servers", + "name": "Mafia 2 Online", + "order": 33, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/miscreated/index.php b/modules/billing/docs/miscreated/index.php index 8b4d8ef2..3b271b06 100644 --- a/modules/billing/docs/miscreated/index.php +++ b/modules/billing/docs/miscreated/index.php @@ -1,68 +1,381 @@ -Miscreated is available for hosting on our platform. This guide covers the basics of setting up and managing your Miscreated server.
-64090- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Miscreated server:
-After your server is created, you can configure it through the control panel:
+Miscreated is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Miscreated server for your community.
+ +Check server configurationhosting.cfg - Server ConfigurationThe Miscreated server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Miscreated Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Miscreated Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Miscreated server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+hosting.cfg - Server ConfigurationCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Miscreated Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Miscreated server hosting +
diff --git a/modules/billing/docs/miscreated/metadata.json b/modules/billing/docs/miscreated/metadata.json index 3c5fb021..28144cd1 100644 --- a/modules/billing/docs/miscreated/metadata.json +++ b/modules/billing/docs/miscreated/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Miscreated game servers", - "name": "Miscreated", - "order": 39, - "category": "todo" +{ + "description": "Setup and configuration guide for Miscreated game servers", + "name": "Miscreated", + "order": 39, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mohaa/index.php b/modules/billing/docs/mohaa/index.php index 748b1b40..09748d23 100644 --- a/modules/billing/docs/mohaa/index.php +++ b/modules/billing/docs/mohaa/index.php @@ -1,66 +1,372 @@ -Medal Of Honor: Allied Assault is available for hosting on our platform. This guide covers the basics of setting up and managing your Medal Of Honor: Allied Assault server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Medal Of Honor: Allied Assault server:
-After your server is created, you can configure it through the control panel:
+Medal Of Honor: Allied Assault is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Medal Of Honor: Allied Assault server for your community.
+ +Check server configurationThe Medal Of Honor: Allied Assault server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Medal Of Honor: Allied Assault Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Medal Of Honor: Allied Assault Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Medal Of Honor: Allied Assault server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Medal Of Honor: Allied Assault Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Medal Of Honor: Allied Assault server hosting +
diff --git a/modules/billing/docs/mohaa/metadata.json b/modules/billing/docs/mohaa/metadata.json index db411a0e..52df6b7b 100644 --- a/modules/billing/docs/mohaa/metadata.json +++ b/modules/billing/docs/mohaa/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Medal Of Honor: Allied Assault game servers", - "name": "Medal Of Honor: Allied Assault", - "order": 40, - "category": "todo" +{ + "description": "Setup and configuration guide for Medal Of Honor: Allied Assault game servers", + "name": "Medal Of Honor: Allied Assault", + "order": 40, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mohbr/index.php b/modules/billing/docs/mohbr/index.php index 8eaf8d3b..7fdee557 100644 --- a/modules/billing/docs/mohbr/index.php +++ b/modules/billing/docs/mohbr/index.php @@ -1,66 +1,372 @@ -Medal Of Honor: Breakthrough (Windows) is available for hosting on our platform. This guide covers the basics of setting up and managing your Medal Of Honor: Breakthrough (Windows) server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Medal Of Honor: Breakthrough (Windows) server:
-After your server is created, you can configure it through the control panel:
+Medal Of Honor: Breakthrough (Windows) is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Medal Of Honor: Breakthrough (Windows) server for your community.
+ +Check server configurationThe Medal Of Honor: Breakthrough (Windows) server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Medal Of Honor: Breakthrough (Windows) Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Medal Of Honor: Breakthrough (Windows) Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Medal Of Honor: Breakthrough (Windows) server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Medal Of Honor: Breakthrough (Windows) Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Medal Of Honor: Breakthrough (Windows) server hosting +
diff --git a/modules/billing/docs/mohbr/metadata.json b/modules/billing/docs/mohbr/metadata.json index 7e856710..4fb35a44 100644 --- a/modules/billing/docs/mohbr/metadata.json +++ b/modules/billing/docs/mohbr/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Medal Of Honor: Breakthrough (Windows) game servers", - "name": "Medal Of Honor: Breakthrough (Windows)", - "order": 42, - "category": "todo" +{ + "description": "Setup and configuration guide for Medal Of Honor: Breakthrough (Windows) game servers", + "name": "Medal Of Honor: Breakthrough (Windows)", + "order": 42, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mohsp/index.php b/modules/billing/docs/mohsp/index.php index 5d84f74e..2a5186b5 100644 --- a/modules/billing/docs/mohsp/index.php +++ b/modules/billing/docs/mohsp/index.php @@ -1,66 +1,372 @@ -Medal Of Honor: Spearhead is available for hosting on our platform. This guide covers the basics of setting up and managing your Medal Of Honor: Spearhead server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Medal Of Honor: Spearhead server:
-After your server is created, you can configure it through the control panel:
+Medal Of Honor: Spearhead is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Medal Of Honor: Spearhead server for your community.
+ +Check server configurationThe Medal Of Honor: Spearhead server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Medal Of Honor: Spearhead Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Medal Of Honor: Spearhead Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Medal Of Honor: Spearhead server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Medal Of Honor: Spearhead Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Medal Of Honor: Spearhead server hosting +
diff --git a/modules/billing/docs/mohsp/metadata.json b/modules/billing/docs/mohsp/metadata.json index fdd49d4c..19c6de08 100644 --- a/modules/billing/docs/mohsp/metadata.json +++ b/modules/billing/docs/mohsp/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Medal Of Honor: Spearhead game servers", - "name": "Medal Of Honor: Spearhead", - "order": 43, - "category": "todo" +{ + "description": "Setup and configuration guide for Medal Of Honor: Spearhead game servers", + "name": "Medal Of Honor: Spearhead", + "order": 43, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mohspdemo/index.php b/modules/billing/docs/mohspdemo/index.php index 3d5cfb9a..e3520bcc 100644 --- a/modules/billing/docs/mohspdemo/index.php +++ b/modules/billing/docs/mohspdemo/index.php @@ -1,66 +1,372 @@ -Medal Of Honor: Spearhead Demo Server (Windows) is available for hosting on our platform. This guide covers the basics of setting up and managing your Medal Of Honor: Spearhead Demo Server (Windows) server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Medal Of Honor: Spearhead Demo Server (Windows) server:
-After your server is created, you can configure it through the control panel:
+Medal Of Honor: Spearhead Demo Server (Windows) is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Medal Of Honor: Spearhead Demo Server (Windows) server for your community.
+ +Check server configurationThe Medal Of Honor: Spearhead Demo Server (Windows) server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Medal Of Honor: Spearhead Demo Server (Windows) Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Medal Of Honor: Spearhead Demo Server (Windows) Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Medal Of Honor: Spearhead Demo Server (Windows) server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Medal Of Honor: Spearhead Demo Server (Windows) Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Medal Of Honor: Spearhead Demo Server (Windows) server hosting +
diff --git a/modules/billing/docs/mohspdemo/metadata.json b/modules/billing/docs/mohspdemo/metadata.json index d15f4897..aa1c4fc2 100644 --- a/modules/billing/docs/mohspdemo/metadata.json +++ b/modules/billing/docs/mohspdemo/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Medal Of Honor: Spearhead Demo Server (Windows) game servers", - "name": "Medal Of Honor: Spearhead Demo Server (Windows)", - "order": 45, - "category": "todo" +{ + "description": "Setup and configuration guide for Medal Of Honor: Spearhead Demo Server (Windows) game servers", + "name": "Medal Of Honor: Spearhead Demo Server (Windows)", + "order": 45, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mordhau/index.php b/modules/billing/docs/mordhau/index.php index 4624dd4e..00518420 100644 --- a/modules/billing/docs/mordhau/index.php +++ b/modules/billing/docs/mordhau/index.php @@ -1,68 +1,381 @@ -Mordhau is available for hosting on our platform. This guide covers the basics of setting up and managing your Mordhau server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Mordhau server:
-After your server is created, you can configure it through the control panel:
+Mordhau is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Mordhau server for your community.
+ +Check server configurationMordhau/Saved/Config/LinuxServer/Game.ini - Main Config FileThe Mordhau server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Mordhau Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Mordhau Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Mordhau server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+Mordhau/Saved/Config/LinuxServer/Game.ini - Main Config FileCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Mordhau Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Mordhau server hosting +
diff --git a/modules/billing/docs/mordhau/metadata.json b/modules/billing/docs/mordhau/metadata.json index a0208b54..1856fae4 100644 --- a/modules/billing/docs/mordhau/metadata.json +++ b/modules/billing/docs/mordhau/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Mordhau game servers", - "name": "Mordhau", - "order": 46, - "category": "todo" +{ + "description": "Setup and configuration guide for Mordhau game servers", + "name": "Mordhau", + "order": 46, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/multitheftauto/index.php b/modules/billing/docs/multitheftauto/index.php index 7c69f5fc..c35b657e 100644 --- a/modules/billing/docs/multitheftauto/index.php +++ b/modules/billing/docs/multitheftauto/index.php @@ -1,68 +1,381 @@ -Multi Theft Auto is available for hosting on our platform. This guide covers the basics of setting up and managing your Multi Theft Auto server.
-22003- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Multi Theft Auto server:
-After your server is created, you can configure it through the control panel:
+Multi Theft Auto is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Multi Theft Auto server for your community.
+ +Check server configurationmods/deathmatch/mtaserver.conf - Server ConfigurationsThe Multi Theft Auto server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Multi Theft Auto Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Multi Theft Auto Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Multi Theft Auto server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+mods/deathmatch/mtaserver.conf - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Multi Theft Auto Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Multi Theft Auto server hosting +
diff --git a/modules/billing/docs/multitheftauto/metadata.json b/modules/billing/docs/multitheftauto/metadata.json index b75911e5..23e2cadd 100644 --- a/modules/billing/docs/multitheftauto/metadata.json +++ b/modules/billing/docs/multitheftauto/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Multi Theft Auto game servers", - "name": "Multi Theft Auto", - "order": 48, - "category": "todo" +{ + "description": "Setup and configuration guide for Multi Theft Auto game servers", + "name": "Multi Theft Auto", + "order": 48, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/mumble/index.php b/modules/billing/docs/mumble/index.php index 79a48f22..c45eb806 100644 --- a/modules/billing/docs/mumble/index.php +++ b/modules/billing/docs/mumble/index.php @@ -1,68 +1,372 @@ -Murmur [Mumble server] is available for hosting on our platform. This guide covers the basics of setting up and managing your Murmur [Mumble server] server.
-64738- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Murmur [Mumble server] server:
-After your server is created, you can configure it through the control panel:
+Murmur [Mumble server] is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Murmur [Mumble server] server for your community.
+ +Check server configurationThe Murmur [Mumble server] server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Murmur [Mumble server] Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Murmur [Mumble server] Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Murmur [Mumble server] server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Murmur [Mumble server] Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Murmur [Mumble server] server hosting +
diff --git a/modules/billing/docs/mumble/metadata.json b/modules/billing/docs/mumble/metadata.json index a687ac10..db6ca658 100644 --- a/modules/billing/docs/mumble/metadata.json +++ b/modules/billing/docs/mumble/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Murmur [Mumble server] game servers", - "name": "Murmur [Mumble server]", - "order": 52, - "category": "todo" +{ + "description": "Setup and configuration guide for Murmur [Mumble server] game servers", + "name": "Murmur [Mumble server]", + "order": 52, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/nexuiz/index.php b/modules/billing/docs/nexuiz/index.php index beb37a65..9b700bbc 100644 --- a/modules/billing/docs/nexuiz/index.php +++ b/modules/billing/docs/nexuiz/index.php @@ -1,68 +1,372 @@ -Nexuiz is available for hosting on our platform. This guide covers the basics of setting up and managing your Nexuiz server.
-26000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Nexuiz server:
-After your server is created, you can configure it through the control panel:
+Nexuiz is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Nexuiz server for your community.
+ +Check server configurationThe Nexuiz server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Nexuiz Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Nexuiz Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Nexuiz server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Nexuiz Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Nexuiz server hosting +
diff --git a/modules/billing/docs/nexuiz/metadata.json b/modules/billing/docs/nexuiz/metadata.json index 95aabfd3..9e82068a 100644 --- a/modules/billing/docs/nexuiz/metadata.json +++ b/modules/billing/docs/nexuiz/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Nexuiz game servers", - "name": "Nexuiz", - "order": 55, - "category": "todo" +{ + "description": "Setup and configuration guide for Nexuiz game servers", + "name": "Nexuiz", + "order": 55, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/nmrih_steam/index.php b/modules/billing/docs/nmrih_steam/index.php index 84ded45b..c15e4c8e 100644 --- a/modules/billing/docs/nmrih_steam/index.php +++ b/modules/billing/docs/nmrih_steam/index.php @@ -1,68 +1,372 @@ -No More Room In Hell is available for hosting on our platform. This guide covers the basics of setting up and managing your No More Room In Hell server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a No More Room In Hell server:
-After your server is created, you can configure it through the control panel:
+No More Room In Hell is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a No More Room In Hell server for your community.
+ +Check server configurationThe No More Room In Hell server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="No More Room In Hell Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="No More Room In Hell Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your No More Room In Hell server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=No More Room In Hell Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For No More Room In Hell server hosting +
diff --git a/modules/billing/docs/nmrih_steam/metadata.json b/modules/billing/docs/nmrih_steam/metadata.json index 9acd0c72..ff503887 100644 --- a/modules/billing/docs/nmrih_steam/metadata.json +++ b/modules/billing/docs/nmrih_steam/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for No More Room In Hell game servers", - "name": "No More Room In Hell", - "order": 58, - "category": "todo" +{ + "description": "Setup and configuration guide for No More Room In Hell game servers", + "name": "No More Room In Hell", + "order": 58, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ns2/index.php b/modules/billing/docs/ns2/index.php index 53c8ba58..1b2c3e26 100644 --- a/modules/billing/docs/ns2/index.php +++ b/modules/billing/docs/ns2/index.php @@ -1,68 +1,372 @@ -Natural Selection 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Natural Selection 2 server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Natural Selection 2 server:
-After your server is created, you can configure it through the control panel:
+Natural Selection 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Natural Selection 2 server for your community.
+ +Check server configurationThe Natural Selection 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Natural Selection 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Natural Selection 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Natural Selection 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Natural Selection 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Natural Selection 2 server hosting +
diff --git a/modules/billing/docs/ns2/metadata.json b/modules/billing/docs/ns2/metadata.json index 63717a06..14440612 100644 --- a/modules/billing/docs/ns2/metadata.json +++ b/modules/billing/docs/ns2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Natural Selection 2 game servers", - "name": "Natural Selection 2", - "order": 54, - "category": "todo" +{ + "description": "Setup and configuration guide for Natural Selection 2 game servers", + "name": "Natural Selection 2", + "order": 54, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/nucleardawn/index.php b/modules/billing/docs/nucleardawn/index.php index 52d7a153..2832a6d8 100644 --- a/modules/billing/docs/nucleardawn/index.php +++ b/modules/billing/docs/nucleardawn/index.php @@ -1,68 +1,372 @@ -Nuclear Dawn (Linux) is available for hosting on our platform. This guide covers the basics of setting up and managing your Nuclear Dawn (Linux) server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Nuclear Dawn (Linux) server:
-After your server is created, you can configure it through the control panel:
+Nuclear Dawn (Linux) is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Nuclear Dawn (Linux) server for your community.
+ +Check server configurationThe Nuclear Dawn (Linux) server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Nuclear Dawn (Linux) Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Nuclear Dawn (Linux) Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Nuclear Dawn (Linux) server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Nuclear Dawn (Linux) Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Nuclear Dawn (Linux) server hosting +
diff --git a/modules/billing/docs/nucleardawn/metadata.json b/modules/billing/docs/nucleardawn/metadata.json index 1af877ca..0d7e325e 100644 --- a/modules/billing/docs/nucleardawn/metadata.json +++ b/modules/billing/docs/nucleardawn/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Nuclear Dawn (Linux) game servers", - "name": "Nuclear Dawn (Linux)", - "order": 60, - "category": "todo" +{ + "description": "Setup and configuration guide for Nuclear Dawn (Linux) game servers", + "name": "Nuclear Dawn (Linux)", + "order": 60, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ootow/index.php b/modules/billing/docs/ootow/index.php index f2a22dd2..05323caf 100644 --- a/modules/billing/docs/ootow/index.php +++ b/modules/billing/docs/ootow/index.php @@ -1,66 +1,372 @@ -Outlaws of the Old West is available for hosting on our platform. This guide covers the basics of setting up and managing your Outlaws of the Old West server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Outlaws of the Old West server:
-After your server is created, you can configure it through the control panel:
+Outlaws of the Old West is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Outlaws of the Old West server for your community.
+ +Check server configurationThe Outlaws of the Old West server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Outlaws of the Old West Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Outlaws of the Old West Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Outlaws of the Old West server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Outlaws of the Old West Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Outlaws of the Old West server hosting +
diff --git a/modules/billing/docs/ootow/metadata.json b/modules/billing/docs/ootow/metadata.json index 22ff7420..f1a7cebe 100644 --- a/modules/billing/docs/ootow/metadata.json +++ b/modules/billing/docs/ootow/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Outlaws of the Old West game servers", - "name": "Outlaws of the Old West", - "order": 62, - "category": "todo" +{ + "description": "Setup and configuration guide for Outlaws of the Old West game servers", + "name": "Outlaws of the Old West", + "order": 62, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/openttd/index.php b/modules/billing/docs/openttd/index.php index 4402eee2..1001cf5f 100644 --- a/modules/billing/docs/openttd/index.php +++ b/modules/billing/docs/openttd/index.php @@ -1,68 +1,381 @@ -OpenTTD is available for hosting on our platform. This guide covers the basics of setting up and managing your OpenTTD server.
-3979- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a OpenTTD server:
-After your server is created, you can configure it through the control panel:
+OpenTTD is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a OpenTTD server for your community.
+ +Check server configurationopenttd.cfg - Server ConfigurationsThe OpenTTD server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="OpenTTD Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="OpenTTD Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your OpenTTD server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+openttd.cfg - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=OpenTTD Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For OpenTTD server hosting +
diff --git a/modules/billing/docs/openttd/metadata.json b/modules/billing/docs/openttd/metadata.json index 86b50426..c63fd23e 100644 --- a/modules/billing/docs/openttd/metadata.json +++ b/modules/billing/docs/openttd/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for OpenTTD game servers", - "name": "OpenTTD", - "order": 63, - "category": "todo" +{ + "description": "Setup and configuration guide for OpenTTD game servers", + "name": "OpenTTD", + "order": 63, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/pixark/index.php b/modules/billing/docs/pixark/index.php index bb3ab7a5..392bbe50 100644 --- a/modules/billing/docs/pixark/index.php +++ b/modules/billing/docs/pixark/index.php @@ -1,68 +1,381 @@ -PixARK is available for hosting on our platform. This guide covers the basics of setting up and managing your PixARK server.
-7777- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a PixARK server:
-After your server is created, you can configure it through the control panel:
+PixARK is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a PixARK server for your community.
+ +Check server configurationShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini - Server ConfigurationsThe PixARK server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="PixARK Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="PixARK Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your PixARK server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=PixARK Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For PixARK server hosting +
diff --git a/modules/billing/docs/pixark/metadata.json b/modules/billing/docs/pixark/metadata.json index 16b256b3..2a401fa1 100644 --- a/modules/billing/docs/pixark/metadata.json +++ b/modules/billing/docs/pixark/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for PixARK game servers", - "name": "PixARK", - "order": 67, - "category": "todo" +{ + "description": "Setup and configuration guide for PixARK game servers", + "name": "PixARK", + "order": 67, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/pvkii/index.php b/modules/billing/docs/pvkii/index.php index 8f6977c3..41d45056 100644 --- a/modules/billing/docs/pvkii/index.php +++ b/modules/billing/docs/pvkii/index.php @@ -1,68 +1,372 @@ -Pirates, Vikings and Knights II is available for hosting on our platform. This guide covers the basics of setting up and managing your Pirates, Vikings and Knights II server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Pirates, Vikings and Knights II server:
-After your server is created, you can configure it through the control panel:
+Pirates, Vikings and Knights II is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Pirates, Vikings and Knights II server for your community.
+ +Check server configurationThe Pirates, Vikings and Knights II server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Pirates, Vikings and Knights II Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Pirates, Vikings and Knights II Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Pirates, Vikings and Knights II server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Pirates, Vikings and Knights II Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Pirates, Vikings and Knights II server hosting +
diff --git a/modules/billing/docs/pvkii/metadata.json b/modules/billing/docs/pvkii/metadata.json index 27de3d3b..c387f8d7 100644 --- a/modules/billing/docs/pvkii/metadata.json +++ b/modules/billing/docs/pvkii/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Pirates, Vikings and Knights II game servers", - "name": "Pirates, Vikings and Knights II", - "order": 68, - "category": "todo" +{ + "description": "Setup and configuration guide for Pirates, Vikings and Knights II game servers", + "name": "Pirates, Vikings and Knights II", + "order": 68, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/quake3/index.php b/modules/billing/docs/quake3/index.php index 4ee0530a..30cc8c82 100644 --- a/modules/billing/docs/quake3/index.php +++ b/modules/billing/docs/quake3/index.php @@ -1,68 +1,372 @@ -Quake 3 is available for hosting on our platform. This guide covers the basics of setting up and managing your Quake 3 server.
-27960- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Quake 3 server:
-After your server is created, you can configure it through the control panel:
+Quake 3 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Quake 3 server for your community.
+ +Check server configurationThe Quake 3 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Quake 3 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Quake 3 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Quake 3 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Quake 3 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Quake 3 server hosting +
diff --git a/modules/billing/docs/quake3/metadata.json b/modules/billing/docs/quake3/metadata.json index fdc20caf..57b53a5c 100644 --- a/modules/billing/docs/quake3/metadata.json +++ b/modules/billing/docs/quake3/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Quake 3 game servers", - "name": "Quake 3", - "order": 69, - "category": "todo" +{ + "description": "Setup and configuration guide for Quake 3 game servers", + "name": "Quake 3", + "order": 69, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/quake4/index.php b/modules/billing/docs/quake4/index.php index 211cc089..f7cf4a3e 100644 --- a/modules/billing/docs/quake4/index.php +++ b/modules/billing/docs/quake4/index.php @@ -1,68 +1,372 @@ -Quake 4 is available for hosting on our platform. This guide covers the basics of setting up and managing your Quake 4 server.
-27666- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Quake 4 server:
-After your server is created, you can configure it through the control panel:
+Quake 4 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Quake 4 server for your community.
+ +Check server configurationThe Quake 4 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Quake 4 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Quake 4 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Quake 4 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Quake 4 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Quake 4 server hosting +
diff --git a/modules/billing/docs/quake4/metadata.json b/modules/billing/docs/quake4/metadata.json index e2f4d553..fd69ce3a 100644 --- a/modules/billing/docs/quake4/metadata.json +++ b/modules/billing/docs/quake4/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Quake 4 game servers", - "name": "Quake 4", - "order": 70, - "category": "todo" +{ + "description": "Setup and configuration guide for Quake 4 game servers", + "name": "Quake 4", + "order": 70, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/redorchestra2/index.php b/modules/billing/docs/redorchestra2/index.php index aad3d336..b0985b1f 100644 --- a/modules/billing/docs/redorchestra2/index.php +++ b/modules/billing/docs/redorchestra2/index.php @@ -1,68 +1,372 @@ -Red Orchestra 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Red Orchestra 2 server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Red Orchestra 2 server:
-After your server is created, you can configure it through the control panel:
+Red Orchestra 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Red Orchestra 2 server for your community.
+ +Check server configurationThe Red Orchestra 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Red Orchestra 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Red Orchestra 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Red Orchestra 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Red Orchestra 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Red Orchestra 2 server hosting +
diff --git a/modules/billing/docs/redorchestra2/metadata.json b/modules/billing/docs/redorchestra2/metadata.json index 6e877db5..cba2b10c 100644 --- a/modules/billing/docs/redorchestra2/metadata.json +++ b/modules/billing/docs/redorchestra2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Red Orchestra 2 game servers", - "name": "Red Orchestra 2", - "order": 71, - "category": "todo" +{ + "description": "Setup and configuration guide for Red Orchestra 2 game servers", + "name": "Red Orchestra 2", + "order": 71, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/reignofkings/index.php b/modules/billing/docs/reignofkings/index.php index 32462038..1629e858 100644 --- a/modules/billing/docs/reignofkings/index.php +++ b/modules/billing/docs/reignofkings/index.php @@ -1,68 +1,387 @@ -Reign of Kings is available for hosting on our platform. This guide covers the basics of setting up and managing your Reign of Kings server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Reign of Kings server:
-After your server is created, you can configure it through the control panel:
+Reign of Kings is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Reign of Kings server for your community.
+ +Check server configurationConfiguration/ServerSettings.cfg - Server ConfigurationsConfiguration/ConsoleSettings.cfg - Console ConfigurationsConfiguration/Users.cfg - User ConfigurationsConfiguration/Whitelist.cfg - Whitelist ConfigurationsThe Reign of Kings server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Reign of Kings Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Reign of Kings Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Reign of Kings server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+Configuration/ServerSettings.cfg - Server ConfigurationsConfiguration/ConsoleSettings.cfg - Console ConfigurationsConfiguration/Users.cfg - User ConfigurationsConfiguration/Whitelist.cfg - Whitelist ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Reign of Kings Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Reign of Kings server hosting +
diff --git a/modules/billing/docs/reignofkings/metadata.json b/modules/billing/docs/reignofkings/metadata.json index 9705b676..593b4e0c 100644 --- a/modules/billing/docs/reignofkings/metadata.json +++ b/modules/billing/docs/reignofkings/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Reign of Kings game servers", - "name": "Reign of Kings", - "order": 72, - "category": "todo" +{ + "description": "Setup and configuration guide for Reign of Kings game servers", + "name": "Reign of Kings", + "order": 72, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/risingstorm2/index.php b/modules/billing/docs/risingstorm2/index.php index 72d7673e..8be40f9c 100644 --- a/modules/billing/docs/risingstorm2/index.php +++ b/modules/billing/docs/risingstorm2/index.php @@ -1,68 +1,372 @@ -Rising Storm 2: Vietnam is available for hosting on our platform. This guide covers the basics of setting up and managing your Rising Storm 2: Vietnam server.
-27102- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Rising Storm 2: Vietnam server:
-After your server is created, you can configure it through the control panel:
+Rising Storm 2: Vietnam is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Rising Storm 2: Vietnam server for your community.
+ +Check server configurationThe Rising Storm 2: Vietnam server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Rising Storm 2: Vietnam Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Rising Storm 2: Vietnam Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Rising Storm 2: Vietnam server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Rising Storm 2: Vietnam Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Rising Storm 2: Vietnam server hosting +
diff --git a/modules/billing/docs/risingstorm2/metadata.json b/modules/billing/docs/risingstorm2/metadata.json index 9606a458..7def3d6b 100644 --- a/modules/billing/docs/risingstorm2/metadata.json +++ b/modules/billing/docs/risingstorm2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Rising Storm 2: Vietnam game servers", - "name": "Rising Storm 2: Vietnam", - "order": 74, - "category": "todo" +{ + "description": "Setup and configuration guide for Rising Storm 2: Vietnam game servers", + "name": "Rising Storm 2: Vietnam", + "order": 74, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/roadkill/index.php b/modules/billing/docs/roadkill/index.php index 820a5fe9..fa915a4e 100644 --- a/modules/billing/docs/roadkill/index.php +++ b/modules/billing/docs/roadkill/index.php @@ -1,66 +1,381 @@ -Roadkill is available for hosting on our platform. This guide covers the basics of setting up and managing your Roadkill server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Roadkill server:
-After your server is created, you can configure it through the control panel:
+Roadkill is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Roadkill server for your community.
+ +Check server configurationGameSettings.txt - server.cfgThe Roadkill server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Roadkill Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Roadkill Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Roadkill server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+GameSettings.txt - server.cfgCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Roadkill Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Roadkill server hosting +
diff --git a/modules/billing/docs/roadkill/metadata.json b/modules/billing/docs/roadkill/metadata.json index 2ae14219..13900c04 100644 --- a/modules/billing/docs/roadkill/metadata.json +++ b/modules/billing/docs/roadkill/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Roadkill game servers", - "name": "Roadkill", - "order": 75, - "category": "todo" +{ + "description": "Setup and configuration guide for Roadkill game servers", + "name": "Roadkill", + "order": 75, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/rorserver/index.php b/modules/billing/docs/rorserver/index.php index 3fc7ab31..66c3cb7e 100644 --- a/modules/billing/docs/rorserver/index.php +++ b/modules/billing/docs/rorserver/index.php @@ -1,66 +1,372 @@ -Rigs of Rods is available for hosting on our platform. This guide covers the basics of setting up and managing your Rigs of Rods server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Rigs of Rods server:
-After your server is created, you can configure it through the control panel:
+Rigs of Rods is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Rigs of Rods server for your community.
+ +Check server configurationThe Rigs of Rods server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Rigs of Rods Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Rigs of Rods Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Rigs of Rods server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Rigs of Rods Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Rigs of Rods server hosting +
diff --git a/modules/billing/docs/rorserver/metadata.json b/modules/billing/docs/rorserver/metadata.json index 34f332c5..002542dc 100644 --- a/modules/billing/docs/rorserver/metadata.json +++ b/modules/billing/docs/rorserver/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Rigs of Rods game servers", - "name": "Rigs of Rods", - "order": 76, - "category": "todo" +{ + "description": "Setup and configuration guide for Rigs of Rods game servers", + "name": "Rigs of Rods", + "order": 76, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/serioussamhdfe/index.php b/modules/billing/docs/serioussamhdfe/index.php index 091e2dcc..78eda518 100644 --- a/modules/billing/docs/serioussamhdfe/index.php +++ b/modules/billing/docs/serioussamhdfe/index.php @@ -1,66 +1,372 @@ -Serious Sam HD The First Encounter is available for hosting on our platform. This guide covers the basics of setting up and managing your Serious Sam HD The First Encounter server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Serious Sam HD The First Encounter server:
-After your server is created, you can configure it through the control panel:
+Serious Sam HD The First Encounter is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Serious Sam HD The First Encounter server for your community.
+ +Check server configurationThe Serious Sam HD The First Encounter server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Serious Sam HD The First Encounter Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Serious Sam HD The First Encounter Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Serious Sam HD The First Encounter server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Serious Sam HD The First Encounter Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Serious Sam HD The First Encounter server hosting +
diff --git a/modules/billing/docs/serioussamhdfe/metadata.json b/modules/billing/docs/serioussamhdfe/metadata.json index 4d93aacc..49c71f6a 100644 --- a/modules/billing/docs/serioussamhdfe/metadata.json +++ b/modules/billing/docs/serioussamhdfe/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Serious Sam HD The First Encounter game servers", - "name": "Serious Sam HD The First Encounter", - "order": 82, - "category": "todo" +{ + "description": "Setup and configuration guide for Serious Sam HD The First Encounter game servers", + "name": "Serious Sam HD The First Encounter", + "order": 82, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/serioussamhdse/index.php b/modules/billing/docs/serioussamhdse/index.php index f3e12bff..4be58447 100644 --- a/modules/billing/docs/serioussamhdse/index.php +++ b/modules/billing/docs/serioussamhdse/index.php @@ -1,66 +1,372 @@ -Serious Sam HD The Second Encounter is available for hosting on our platform. This guide covers the basics of setting up and managing your Serious Sam HD The Second Encounter server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Serious Sam HD The Second Encounter server:
-After your server is created, you can configure it through the control panel:
+Serious Sam HD The Second Encounter is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Serious Sam HD The Second Encounter server for your community.
+ +Check server configurationThe Serious Sam HD The Second Encounter server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Serious Sam HD The Second Encounter Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Serious Sam HD The Second Encounter Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Serious Sam HD The Second Encounter server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Serious Sam HD The Second Encounter Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Serious Sam HD The Second Encounter server hosting +
diff --git a/modules/billing/docs/serioussamhdse/metadata.json b/modules/billing/docs/serioussamhdse/metadata.json index d283481d..827678f1 100644 --- a/modules/billing/docs/serioussamhdse/metadata.json +++ b/modules/billing/docs/serioussamhdse/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Serious Sam HD The Second Encounter game servers", - "name": "Serious Sam HD The Second Encounter", - "order": 83, - "category": "todo" +{ + "description": "Setup and configuration guide for Serious Sam HD The Second Encounter game servers", + "name": "Serious Sam HD The Second Encounter", + "order": 83, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/shoutcast/index.php b/modules/billing/docs/shoutcast/index.php index 91c6a8b0..0c72c890 100644 --- a/modules/billing/docs/shoutcast/index.php +++ b/modules/billing/docs/shoutcast/index.php @@ -1,66 +1,372 @@ -Shoutcast server is available for hosting on our platform. This guide covers the basics of setting up and managing your Shoutcast server server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Shoutcast server server:
-After your server is created, you can configure it through the control panel:
+Shoutcast server is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Shoutcast server server for your community.
+ +Check server configurationThe Shoutcast server server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Shoutcast server Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Shoutcast server Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Shoutcast server server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Shoutcast server Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Shoutcast server server hosting +
diff --git a/modules/billing/docs/shoutcast/metadata.json b/modules/billing/docs/shoutcast/metadata.json index 837f87ec..40245ef3 100644 --- a/modules/billing/docs/shoutcast/metadata.json +++ b/modules/billing/docs/shoutcast/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Shoutcast server game servers", - "name": "Shoutcast server", - "order": 86, - "category": "todo" +{ + "description": "Setup and configuration guide for Shoutcast server game servers", + "name": "Shoutcast server", + "order": 86, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/shoutcast_bot/index.php b/modules/billing/docs/shoutcast_bot/index.php index 7e36bedf..f66fd3e5 100644 --- a/modules/billing/docs/shoutcast_bot/index.php +++ b/modules/billing/docs/shoutcast_bot/index.php @@ -1,66 +1,372 @@ -Shoutcast server Bot is available for hosting on our platform. This guide covers the basics of setting up and managing your Shoutcast server Bot server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Shoutcast server Bot server:
-After your server is created, you can configure it through the control panel:
+Shoutcast server Bot is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Shoutcast server Bot server for your community.
+ +Check server configurationThe Shoutcast server Bot server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Shoutcast server Bot Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Shoutcast server Bot Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Shoutcast server Bot server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Shoutcast server Bot Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Shoutcast server Bot server hosting +
diff --git a/modules/billing/docs/shoutcast_bot/metadata.json b/modules/billing/docs/shoutcast_bot/metadata.json index d239fafe..fb83e6ec 100644 --- a/modules/billing/docs/shoutcast_bot/metadata.json +++ b/modules/billing/docs/shoutcast_bot/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Shoutcast server Bot game servers", - "name": "Shoutcast server Bot", - "order": 87, - "category": "todo" +{ + "description": "Setup and configuration guide for Shoutcast server Bot game servers", + "name": "Shoutcast server Bot", + "order": 87, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/sinusbot/index.php b/modules/billing/docs/sinusbot/index.php index c89a4a4e..2cafcbb9 100644 --- a/modules/billing/docs/sinusbot/index.php +++ b/modules/billing/docs/sinusbot/index.php @@ -1,66 +1,381 @@ -SinusBot for TS 3 and Discord is available for hosting on our platform. This guide covers the basics of setting up and managing your SinusBot for TS 3 and Discord server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a SinusBot for TS 3 and Discord server:
-After your server is created, you can configure it through the control panel:
+SinusBot for TS 3 and Discord is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a SinusBot for TS 3 and Discord server for your community.
+ +Check server configurationconfig.ini - Main Config FileThe SinusBot for TS 3 and Discord server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="SinusBot for TS 3 and Discord Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="SinusBot for TS 3 and Discord Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your SinusBot for TS 3 and Discord server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+config.ini - Main Config FileCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=SinusBot for TS 3 and Discord Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For SinusBot for TS 3 and Discord server hosting +
diff --git a/modules/billing/docs/sinusbot/metadata.json b/modules/billing/docs/sinusbot/metadata.json index db3ce593..ea7350ee 100644 --- a/modules/billing/docs/sinusbot/metadata.json +++ b/modules/billing/docs/sinusbot/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for SinusBot for TS 3 and Discord game servers", - "name": "SinusBot for TS 3 and Discord", - "order": 88, - "category": "todo" +{ + "description": "Setup and configuration guide for SinusBot for TS 3 and Discord game servers", + "name": "SinusBot for TS 3 and Discord", + "order": 88, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/smashball/index.php b/modules/billing/docs/smashball/index.php index 5fae2e07..0b23ae69 100644 --- a/modules/billing/docs/smashball/index.php +++ b/modules/billing/docs/smashball/index.php @@ -1,66 +1,372 @@ -Smashball is available for hosting on our platform. This guide covers the basics of setting up and managing your Smashball server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Smashball server:
-After your server is created, you can configure it through the control panel:
+Smashball is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Smashball server for your community.
+ +Check server configurationThe Smashball server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Smashball Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Smashball Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Smashball server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Smashball Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Smashball server hosting +
diff --git a/modules/billing/docs/smashball/metadata.json b/modules/billing/docs/smashball/metadata.json index 992c11cf..c2c8435d 100644 --- a/modules/billing/docs/smashball/metadata.json +++ b/modules/billing/docs/smashball/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Smashball game servers", - "name": "Smashball", - "order": 3, - "category": "todo" +{ + "description": "Setup and configuration guide for Smashball game servers", + "name": "Smashball", + "order": 3, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/smokinguns/index.php b/modules/billing/docs/smokinguns/index.php index 09ea8b80..c9ea05fb 100644 --- a/modules/billing/docs/smokinguns/index.php +++ b/modules/billing/docs/smokinguns/index.php @@ -1,68 +1,372 @@ -Smokin Guns is available for hosting on our platform. This guide covers the basics of setting up and managing your Smokin Guns server.
-27960- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Smokin Guns server:
-After your server is created, you can configure it through the control panel:
+Smokin Guns is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Smokin Guns server for your community.
+ +Check server configurationThe Smokin Guns server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Smokin Guns Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Smokin Guns Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Smokin Guns server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Smokin Guns Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Smokin Guns server hosting +
diff --git a/modules/billing/docs/smokinguns/metadata.json b/modules/billing/docs/smokinguns/metadata.json index 8d2f1028..0c6dd213 100644 --- a/modules/billing/docs/smokinguns/metadata.json +++ b/modules/billing/docs/smokinguns/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Smokin Guns game servers", - "name": "Smokin Guns", - "order": 89, - "category": "todo" +{ + "description": "Setup and configuration guide for Smokin Guns game servers", + "name": "Smokin Guns", + "order": 89, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/sms/index.php b/modules/billing/docs/sms/index.php index 4473189c..7508f326 100644 --- a/modules/billing/docs/sms/index.php +++ b/modules/billing/docs/sms/index.php @@ -1,66 +1,372 @@ -ShootMania Storm is available for hosting on our platform. This guide covers the basics of setting up and managing your ShootMania Storm server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a ShootMania Storm server:
-After your server is created, you can configure it through the control panel:
+ShootMania Storm is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a ShootMania Storm server for your community.
+ +Check server configurationThe ShootMania Storm server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="ShootMania Storm Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="ShootMania Storm Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your ShootMania Storm server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=ShootMania Storm Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For ShootMania Storm server hosting +
diff --git a/modules/billing/docs/sms/metadata.json b/modules/billing/docs/sms/metadata.json index cb1f4a52..f2a5cbc7 100644 --- a/modules/billing/docs/sms/metadata.json +++ b/modules/billing/docs/sms/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for ShootMania Storm game servers", - "name": "ShootMania Storm", - "order": 84, - "category": "todo" +{ + "description": "Setup and configuration guide for ShootMania Storm game servers", + "name": "ShootMania Storm", + "order": 84, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/sniperelitev2/index.php b/modules/billing/docs/sniperelitev2/index.php index 54831f74..314d6edf 100644 --- a/modules/billing/docs/sniperelitev2/index.php +++ b/modules/billing/docs/sniperelitev2/index.php @@ -1,66 +1,381 @@ -Sniper Elite V2 is available for hosting on our platform. This guide covers the basics of setting up and managing your Sniper Elite V2 server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Sniper Elite V2 server:
-After your server is created, you can configure it through the control panel:
+Sniper Elite V2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Sniper Elite V2 server for your community.
+ +Check server configurationdefault.cfg - Server ConfigurationsThe Sniper Elite V2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Sniper Elite V2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Sniper Elite V2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Sniper Elite V2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+default.cfg - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Sniper Elite V2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Sniper Elite V2 server hosting +
diff --git a/modules/billing/docs/sniperelitev2/metadata.json b/modules/billing/docs/sniperelitev2/metadata.json index e9a12100..83d8661b 100644 --- a/modules/billing/docs/sniperelitev2/metadata.json +++ b/modules/billing/docs/sniperelitev2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Sniper Elite V2 game servers", - "name": "Sniper Elite V2", - "order": 91, - "category": "todo" +{ + "description": "Setup and configuration guide for Sniper Elite V2 game servers", + "name": "Sniper Elite V2", + "order": 91, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/soldatserver/index.php b/modules/billing/docs/soldatserver/index.php index 2f7a750e..dc96c64b 100644 --- a/modules/billing/docs/soldatserver/index.php +++ b/modules/billing/docs/soldatserver/index.php @@ -1,66 +1,372 @@ -Soldat is available for hosting on our platform. This guide covers the basics of setting up and managing your Soldat server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Soldat server:
-After your server is created, you can configure it through the control panel:
+Soldat is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Soldat server for your community.
+ +Check server configurationThe Soldat server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Soldat Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Soldat Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Soldat server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Soldat Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Soldat server hosting +
diff --git a/modules/billing/docs/soldatserver/metadata.json b/modules/billing/docs/soldatserver/metadata.json index eb39208c..5cbbc23b 100644 --- a/modules/billing/docs/soldatserver/metadata.json +++ b/modules/billing/docs/soldatserver/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Soldat game servers", - "name": "Soldat", - "order": 92, - "category": "todo" +{ + "description": "Setup and configuration guide for Soldat game servers", + "name": "Soldat", + "order": 92, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/space_engineers/index.php b/modules/billing/docs/space_engineers/index.php index f94b6d34..c26f73d0 100644 --- a/modules/billing/docs/space_engineers/index.php +++ b/modules/billing/docs/space_engineers/index.php @@ -1,68 +1,381 @@ -Space Engineers is available for hosting on our platform. This guide covers the basics of setting up and managing your Space Engineers server.
-27016- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Space Engineers server:
-After your server is created, you can configure it through the control panel:
+Space Engineers is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Space Engineers server for your community.
+ +Check server configurationSpaceEngineers-Dedicated.cfg - Server settingsThe Space Engineers server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Space Engineers Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Space Engineers Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Space Engineers server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+SpaceEngineers-Dedicated.cfg - Server settingsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Space Engineers Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Space Engineers server hosting +
diff --git a/modules/billing/docs/space_engineers/metadata.json b/modules/billing/docs/space_engineers/metadata.json index 98e891da..b5b5949c 100644 --- a/modules/billing/docs/space_engineers/metadata.json +++ b/modules/billing/docs/space_engineers/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Space Engineers game servers", - "name": "Space Engineers", - "order": 93, - "category": "todo" +{ + "description": "Setup and configuration guide for Space Engineers game servers", + "name": "Space Engineers", + "order": 93, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/spigotmc/index.php b/modules/billing/docs/spigotmc/index.php index 596a5d96..049dc0a8 100644 --- a/modules/billing/docs/spigotmc/index.php +++ b/modules/billing/docs/spigotmc/index.php @@ -1,68 +1,372 @@ -Spigot Server is available for hosting on our platform. This guide covers the basics of setting up and managing your Spigot Server server.
-25565- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Spigot Server server:
-After your server is created, you can configure it through the control panel:
+Spigot Server is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Spigot Server server for your community.
+ +Check server configurationThe Spigot Server server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Spigot Server Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Spigot Server Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Spigot Server server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Spigot Server Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Spigot Server server hosting +
diff --git a/modules/billing/docs/spigotmc/metadata.json b/modules/billing/docs/spigotmc/metadata.json index 8cab41ea..aabe3f37 100644 --- a/modules/billing/docs/spigotmc/metadata.json +++ b/modules/billing/docs/spigotmc/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Spigot Server game servers", - "name": "Spigot Server", - "order": 95, - "category": "todo" +{ + "description": "Setup and configuration guide for Spigot Server game servers", + "name": "Spigot Server", + "order": 95, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/spunkybot/index.php b/modules/billing/docs/spunkybot/index.php index 803f50d3..02e26eb5 100644 --- a/modules/billing/docs/spunkybot/index.php +++ b/modules/billing/docs/spunkybot/index.php @@ -1,66 +1,383 @@ -SpunkyBot is available for hosting on our platform. This guide covers the basics of setting up and managing your SpunkyBot server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a SpunkyBot server:
-After your server is created, you can configure it through the control panel:
+SpunkyBot is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a SpunkyBot server for your community.
+ +Check server configurationconf/rules.conf - Rulesconf/settings.conf - SettingsThe SpunkyBot server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="SpunkyBot Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="SpunkyBot Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your SpunkyBot server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+conf/rules.conf - Rulesconf/settings.conf - SettingsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=SpunkyBot Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For SpunkyBot server hosting +
diff --git a/modules/billing/docs/spunkybot/metadata.json b/modules/billing/docs/spunkybot/metadata.json index 87652358..9f729e50 100644 --- a/modules/billing/docs/spunkybot/metadata.json +++ b/modules/billing/docs/spunkybot/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for SpunkyBot game servers", - "name": "SpunkyBot", - "order": 96, - "category": "todo" +{ + "description": "Setup and configuration guide for SpunkyBot game servers", + "name": "SpunkyBot", + "order": 96, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/synergy/index.php b/modules/billing/docs/synergy/index.php index 8e87f073..04361612 100644 --- a/modules/billing/docs/synergy/index.php +++ b/modules/billing/docs/synergy/index.php @@ -1,68 +1,372 @@ -Synergy is available for hosting on our platform. This guide covers the basics of setting up and managing your Synergy server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Synergy server:
-After your server is created, you can configure it through the control panel:
+Synergy is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Synergy server for your community.
+ +Check server configurationThe Synergy server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Synergy Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Synergy Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Synergy server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Synergy Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Synergy server hosting +
diff --git a/modules/billing/docs/synergy/metadata.json b/modules/billing/docs/synergy/metadata.json index 36bc3669..8d5d168b 100644 --- a/modules/billing/docs/synergy/metadata.json +++ b/modules/billing/docs/synergy/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Synergy game servers", - "name": "Synergy", - "order": 4, - "category": "todo" +{ + "description": "Setup and configuration guide for Synergy game servers", + "name": "Synergy", + "order": 4, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/teamspeak2/index.php b/modules/billing/docs/teamspeak2/index.php index 808a982a..364c8a1e 100644 --- a/modules/billing/docs/teamspeak2/index.php +++ b/modules/billing/docs/teamspeak2/index.php @@ -1,68 +1,372 @@ -TeamSpeak 2 is available for hosting on our platform. This guide covers the basics of setting up and managing your TeamSpeak 2 server.
-8767- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a TeamSpeak 2 server:
-After your server is created, you can configure it through the control panel:
+TeamSpeak 2 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a TeamSpeak 2 server for your community.
+ +Check server configurationThe TeamSpeak 2 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="TeamSpeak 2 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="TeamSpeak 2 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your TeamSpeak 2 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=TeamSpeak 2 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For TeamSpeak 2 server hosting +
diff --git a/modules/billing/docs/teamspeak2/metadata.json b/modules/billing/docs/teamspeak2/metadata.json index 10945b08..b21eea70 100644 --- a/modules/billing/docs/teamspeak2/metadata.json +++ b/modules/billing/docs/teamspeak2/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for TeamSpeak 2 game servers", - "name": "TeamSpeak 2", - "order": 102, - "category": "todo" +{ + "description": "Setup and configuration guide for TeamSpeak 2 game servers", + "name": "TeamSpeak 2", + "order": 102, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/teamspeak3/index.php b/modules/billing/docs/teamspeak3/index.php index 180fe39f..ae1df822 100644 --- a/modules/billing/docs/teamspeak3/index.php +++ b/modules/billing/docs/teamspeak3/index.php @@ -1,68 +1,372 @@ -TeamSpeak 3 is available for hosting on our platform. This guide covers the basics of setting up and managing your TeamSpeak 3 server.
-9987- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a TeamSpeak 3 server:
-After your server is created, you can configure it through the control panel:
+TeamSpeak 3 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a TeamSpeak 3 server for your community.
+ +Check server configurationThe TeamSpeak 3 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="TeamSpeak 3 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="TeamSpeak 3 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your TeamSpeak 3 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=TeamSpeak 3 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For TeamSpeak 3 server hosting +
diff --git a/modules/billing/docs/teamspeak3/metadata.json b/modules/billing/docs/teamspeak3/metadata.json index 23896812..f986ec78 100644 --- a/modules/billing/docs/teamspeak3/metadata.json +++ b/modules/billing/docs/teamspeak3/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for TeamSpeak 3 game servers", - "name": "TeamSpeak 3", - "order": 104, - "category": "todo" +{ + "description": "Setup and configuration guide for TeamSpeak 3 game servers", + "name": "TeamSpeak 3", + "order": 104, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/tfc/index.php b/modules/billing/docs/tfc/index.php index 05625c18..4beaced6 100644 --- a/modules/billing/docs/tfc/index.php +++ b/modules/billing/docs/tfc/index.php @@ -1,66 +1,372 @@ -Team Fortress Classic is available for hosting on our platform. This guide covers the basics of setting up and managing your Team Fortress Classic server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Team Fortress Classic server:
-After your server is created, you can configure it through the control panel:
+Team Fortress Classic is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Team Fortress Classic server for your community.
+ +Check server configurationThe Team Fortress Classic server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Team Fortress Classic Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Team Fortress Classic Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Team Fortress Classic server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Team Fortress Classic Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Team Fortress Classic server hosting +
diff --git a/modules/billing/docs/tfc/metadata.json b/modules/billing/docs/tfc/metadata.json index 44f705ad..ffb5660b 100644 --- a/modules/billing/docs/tfc/metadata.json +++ b/modules/billing/docs/tfc/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Team Fortress Classic game servers", - "name": "Team Fortress Classic", - "order": 112, - "category": "todo" +{ + "description": "Setup and configuration guide for Team Fortress Classic game servers", + "name": "Team Fortress Classic", + "order": 112, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/theforest/index.php b/modules/billing/docs/theforest/index.php index 8c2086e2..c0283c86 100644 --- a/modules/billing/docs/theforest/index.php +++ b/modules/billing/docs/theforest/index.php @@ -1,68 +1,381 @@ -The Forest is available for hosting on our platform. This guide covers the basics of setting up and managing your The Forest server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a The Forest server:
-After your server is created, you can configure it through the control panel:
+The Forest is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a The Forest server for your community.
+ +Check server configurationServer.cfg - Server ConfigurationsThe The Forest server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="The Forest Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="The Forest Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your The Forest server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+Server.cfg - Server ConfigurationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=The Forest Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For The Forest server hosting +
diff --git a/modules/billing/docs/theforest/metadata.json b/modules/billing/docs/theforest/metadata.json index f2ddb568..f3647705 100644 --- a/modules/billing/docs/theforest/metadata.json +++ b/modules/billing/docs/theforest/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for The Forest game servers", - "name": "The Forest", - "order": 114, - "category": "todo" +{ + "description": "Setup and configuration guide for The Forest game servers", + "name": "The Forest", + "order": 114, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/trackmanianations/index.php b/modules/billing/docs/trackmanianations/index.php index 6fa6cfd6..7d822e1b 100644 --- a/modules/billing/docs/trackmanianations/index.php +++ b/modules/billing/docs/trackmanianations/index.php @@ -1,66 +1,372 @@ -TrackMania Nations is available for hosting on our platform. This guide covers the basics of setting up and managing your TrackMania Nations server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a TrackMania Nations server:
-After your server is created, you can configure it through the control panel:
+TrackMania Nations is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a TrackMania Nations server for your community.
+ +Check server configurationThe TrackMania Nations server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="TrackMania Nations Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="TrackMania Nations Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your TrackMania Nations server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=TrackMania Nations Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For TrackMania Nations server hosting +
diff --git a/modules/billing/docs/trackmanianations/metadata.json b/modules/billing/docs/trackmanianations/metadata.json index 6e94f14d..10ca39b1 100644 --- a/modules/billing/docs/trackmanianations/metadata.json +++ b/modules/billing/docs/trackmanianations/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for TrackMania Nations game servers", - "name": "TrackMania Nations", - "order": 115, - "category": "todo" +{ + "description": "Setup and configuration guide for TrackMania Nations game servers", + "name": "TrackMania Nations", + "order": 115, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/trackmanianf/index.php b/modules/billing/docs/trackmanianf/index.php index 799a5879..a215828f 100644 --- a/modules/billing/docs/trackmanianf/index.php +++ b/modules/billing/docs/trackmanianf/index.php @@ -1,66 +1,372 @@ -TrackMania Nations Forever is available for hosting on our platform. This guide covers the basics of setting up and managing your TrackMania Nations Forever server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a TrackMania Nations Forever server:
-After your server is created, you can configure it through the control panel:
+TrackMania Nations Forever is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a TrackMania Nations Forever server for your community.
+ +Check server configurationThe TrackMania Nations Forever server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="TrackMania Nations Forever Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="TrackMania Nations Forever Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your TrackMania Nations Forever server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=TrackMania Nations Forever Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For TrackMania Nations Forever server hosting +
diff --git a/modules/billing/docs/trackmanianf/metadata.json b/modules/billing/docs/trackmanianf/metadata.json index e2e6beb9..6adfb1de 100644 --- a/modules/billing/docs/trackmanianf/metadata.json +++ b/modules/billing/docs/trackmanianf/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for TrackMania Nations Forever game servers", - "name": "TrackMania Nations Forever", - "order": 117, - "category": "todo" +{ + "description": "Setup and configuration guide for TrackMania Nations Forever game servers", + "name": "TrackMania Nations Forever", + "order": 117, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ut2004/index.php b/modules/billing/docs/ut2004/index.php index 2c2d36ef..3f133fc3 100644 --- a/modules/billing/docs/ut2004/index.php +++ b/modules/billing/docs/ut2004/index.php @@ -1,68 +1,372 @@ -Unreal Tournament 2004 is available for hosting on our platform. This guide covers the basics of setting up and managing your Unreal Tournament 2004 server.
-7777- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Unreal Tournament 2004 server:
-After your server is created, you can configure it through the control panel:
+Unreal Tournament 2004 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Unreal Tournament 2004 server for your community.
+ +Check server configurationThe Unreal Tournament 2004 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Unreal Tournament 2004 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Unreal Tournament 2004 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Unreal Tournament 2004 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Unreal Tournament 2004 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Unreal Tournament 2004 server hosting +
diff --git a/modules/billing/docs/ut2004/metadata.json b/modules/billing/docs/ut2004/metadata.json index bc87fb46..d644d69d 100644 --- a/modules/billing/docs/ut2004/metadata.json +++ b/modules/billing/docs/ut2004/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Unreal Tournament 2004 game servers", - "name": "Unreal Tournament 2004", - "order": 126, - "category": "todo" +{ + "description": "Setup and configuration guide for Unreal Tournament 2004 game servers", + "name": "Unreal Tournament 2004", + "order": 126, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ut3/index.php b/modules/billing/docs/ut3/index.php index ee154778..cc2d6443 100644 --- a/modules/billing/docs/ut3/index.php +++ b/modules/billing/docs/ut3/index.php @@ -1,68 +1,372 @@ -Unreal Tournament 3 is available for hosting on our platform. This guide covers the basics of setting up and managing your Unreal Tournament 3 server.
-7777- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Unreal Tournament 3 server:
-After your server is created, you can configure it through the control panel:
+Unreal Tournament 3 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Unreal Tournament 3 server for your community.
+ +Check server configurationThe Unreal Tournament 3 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Unreal Tournament 3 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Unreal Tournament 3 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Unreal Tournament 3 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Unreal Tournament 3 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Unreal Tournament 3 server hosting +
diff --git a/modules/billing/docs/ut3/metadata.json b/modules/billing/docs/ut3/metadata.json index 0532fd57..742bb0f3 100644 --- a/modules/billing/docs/ut3/metadata.json +++ b/modules/billing/docs/ut3/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Unreal Tournament 3 game servers", - "name": "Unreal Tournament 3", - "order": 128, - "category": "todo" +{ + "description": "Setup and configuration guide for Unreal Tournament 3 game servers", + "name": "Unreal Tournament 3", + "order": 128, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ut99/index.php b/modules/billing/docs/ut99/index.php index 3bad69a8..583d4901 100644 --- a/modules/billing/docs/ut99/index.php +++ b/modules/billing/docs/ut99/index.php @@ -1,68 +1,372 @@ -Unreal Tournament is available for hosting on our platform. This guide covers the basics of setting up and managing your Unreal Tournament server.
-7777- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Unreal Tournament server:
-After your server is created, you can configure it through the control panel:
+Unreal Tournament is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Unreal Tournament server for your community.
+ +Check server configurationThe Unreal Tournament server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Unreal Tournament Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Unreal Tournament Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Unreal Tournament server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Unreal Tournament Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Unreal Tournament server hosting +
diff --git a/modules/billing/docs/ut99/metadata.json b/modules/billing/docs/ut99/metadata.json index 7017da93..9d87d8e5 100644 --- a/modules/billing/docs/ut99/metadata.json +++ b/modules/billing/docs/ut99/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Unreal Tournament game servers", - "name": "Unreal Tournament", - "order": 119, - "category": "todo" +{ + "description": "Setup and configuration guide for Unreal Tournament game servers", + "name": "Unreal Tournament", + "order": 119, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/vbox/index.php b/modules/billing/docs/vbox/index.php index 621dc66a..2c020582 100644 --- a/modules/billing/docs/vbox/index.php +++ b/modules/billing/docs/vbox/index.php @@ -1,66 +1,372 @@ -VirtualBox is available for hosting on our platform. This guide covers the basics of setting up and managing your VirtualBox server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a VirtualBox server:
-After your server is created, you can configure it through the control panel:
+VirtualBox is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a VirtualBox server for your community.
+ +Check server configurationThe VirtualBox server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="VirtualBox Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="VirtualBox Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your VirtualBox server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=VirtualBox Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For VirtualBox server hosting +
diff --git a/modules/billing/docs/vbox/metadata.json b/modules/billing/docs/vbox/metadata.json index 5c3655c0..ded719b0 100644 --- a/modules/billing/docs/vbox/metadata.json +++ b/modules/billing/docs/vbox/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for VirtualBox game servers", - "name": "VirtualBox", - "order": 131, - "category": "todo" +{ + "description": "Setup and configuration guide for VirtualBox game servers", + "name": "VirtualBox", + "order": 131, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/ventrilo/index.php b/modules/billing/docs/ventrilo/index.php index 2252d775..610f3cc4 100644 --- a/modules/billing/docs/ventrilo/index.php +++ b/modules/billing/docs/ventrilo/index.php @@ -1,68 +1,372 @@ -Ventrilo is available for hosting on our platform. This guide covers the basics of setting up and managing your Ventrilo server.
-3784- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Ventrilo server:
-After your server is created, you can configure it through the control panel:
+Ventrilo is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Ventrilo server for your community.
+ +Check server configurationThe Ventrilo server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Ventrilo Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Ventrilo Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Ventrilo server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Ventrilo Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Ventrilo server hosting +
diff --git a/modules/billing/docs/ventrilo/metadata.json b/modules/billing/docs/ventrilo/metadata.json index ddc10a7f..9dffc852 100644 --- a/modules/billing/docs/ventrilo/metadata.json +++ b/modules/billing/docs/ventrilo/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Ventrilo game servers", - "name": "Ventrilo", - "order": 132, - "category": "todo" +{ + "description": "Setup and configuration guide for Ventrilo game servers", + "name": "Ventrilo", + "order": 132, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/warsow/index.php b/modules/billing/docs/warsow/index.php index ee33bfa8..6bf6855b 100644 --- a/modules/billing/docs/warsow/index.php +++ b/modules/billing/docs/warsow/index.php @@ -1,68 +1,372 @@ -Warsow is available for hosting on our platform. This guide covers the basics of setting up and managing your Warsow server.
-44400- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Warsow server:
-After your server is created, you can configure it through the control panel:
+Warsow is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Warsow server for your community.
+ +Check server configurationThe Warsow server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Warsow Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Warsow Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Warsow server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Warsow Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Warsow server hosting +
diff --git a/modules/billing/docs/warsow/metadata.json b/modules/billing/docs/warsow/metadata.json index 2391ae2a..0133d5b1 100644 --- a/modules/billing/docs/warsow/metadata.json +++ b/modules/billing/docs/warsow/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Warsow game servers", - "name": "Warsow", - "order": 138, - "category": "todo" +{ + "description": "Setup and configuration guide for Warsow game servers", + "name": "Warsow", + "order": 138, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/wolfrtcw_1-4/index.php b/modules/billing/docs/wolfrtcw_1-4/index.php index cf05be54..bc4fbc2a 100644 --- a/modules/billing/docs/wolfrtcw_1-4/index.php +++ b/modules/billing/docs/wolfrtcw_1-4/index.php @@ -1,66 +1,372 @@ -Wolfenstein: Return To Castle Wolfenstein 1.4 is available for hosting on our platform. This guide covers the basics of setting up and managing your Wolfenstein: Return To Castle Wolfenstein 1.4 server.
-- This game server can be hosted on a VPS or dedicated server. Port configuration depends on the game engine and can typically be set in the server configuration files. -
-- Refer to the official game server documentation for specific port requirements and configuration details. -
+To create a Wolfenstein: Return To Castle Wolfenstein 1.4 server:
-After your server is created, you can configure it through the control panel:
+Wolfenstein: Return To Castle Wolfenstein 1.4 is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Wolfenstein: Return To Castle Wolfenstein 1.4 server for your community.
+ +Check server configurationThe Wolfenstein: Return To Castle Wolfenstein 1.4 server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Wolfenstein: Return To Castle Wolfenstein 1.4 Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Wolfenstein: Return To Castle Wolfenstein 1.4 Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Wolfenstein: Return To Castle Wolfenstein 1.4 server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Wolfenstein: Return To Castle Wolfenstein 1.4 Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Wolfenstein: Return To Castle Wolfenstein 1.4 server hosting +
diff --git a/modules/billing/docs/wolfrtcw_1-4/metadata.json b/modules/billing/docs/wolfrtcw_1-4/metadata.json index 53022275..89e57048 100644 --- a/modules/billing/docs/wolfrtcw_1-4/metadata.json +++ b/modules/billing/docs/wolfrtcw_1-4/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Wolfenstein: Return To Castle Wolfenstein 1.4 game servers", - "name": "Wolfenstein: Return To Castle Wolfenstein 1.4", - "order": 143, - "category": "todo" +{ + "description": "Setup and configuration guide for Wolfenstein: Return To Castle Wolfenstein 1.4 game servers", + "name": "Wolfenstein: Return To Castle Wolfenstein 1.4", + "order": 143, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/wreckfest/index.php b/modules/billing/docs/wreckfest/index.php index 568cf794..d7497894 100644 --- a/modules/billing/docs/wreckfest/index.php +++ b/modules/billing/docs/wreckfest/index.php @@ -1,68 +1,381 @@ -Wreckfest is available for hosting on our platform. This guide covers the basics of setting up and managing your Wreckfest server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Wreckfest server:
-After your server is created, you can configure it through the control panel:
+Wreckfest is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Wreckfest server for your community.
+ +Check server configurationserver_config.cfg - Advanced ModificationsThe Wreckfest server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Wreckfest Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Wreckfest Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Wreckfest server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Important configuration files for this server:
+server_config.cfg - Advanced ModificationsCommon administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Wreckfest Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Wreckfest server hosting +
diff --git a/modules/billing/docs/wreckfest/metadata.json b/modules/billing/docs/wreckfest/metadata.json index d481f452..e0af903a 100644 --- a/modules/billing/docs/wreckfest/metadata.json +++ b/modules/billing/docs/wreckfest/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Wreckfest game servers", - "name": "Wreckfest", - "order": 144, - "category": "todo" +{ + "description": "Setup and configuration guide for Wreckfest game servers", + "name": "Wreckfest", + "order": 144, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/wurmu/index.php b/modules/billing/docs/wurmu/index.php index b53629cd..da9f6a33 100644 --- a/modules/billing/docs/wurmu/index.php +++ b/modules/billing/docs/wurmu/index.php @@ -1,68 +1,372 @@ -Wurm Unlimited is available for hosting on our platform. This guide covers the basics of setting up and managing your Wurm Unlimited server.
-3724- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Wurm Unlimited server:
-After your server is created, you can configure it through the control panel:
+Wurm Unlimited is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Wurm Unlimited server for your community.
+ +Check server configurationThe Wurm Unlimited server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Wurm Unlimited Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Wurm Unlimited Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Wurm Unlimited server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Wurm Unlimited Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Wurm Unlimited server hosting +
diff --git a/modules/billing/docs/wurmu/metadata.json b/modules/billing/docs/wurmu/metadata.json index f894f52f..a59d0b6f 100644 --- a/modules/billing/docs/wurmu/metadata.json +++ b/modules/billing/docs/wurmu/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Wurm Unlimited game servers", - "name": "Wurm Unlimited", - "order": 145, - "category": "todo" +{ + "description": "Setup and configuration guide for Wurm Unlimited game servers", + "name": "Wurm Unlimited", + "order": 145, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/xonotic/index.php b/modules/billing/docs/xonotic/index.php index a413713a..cf76cfe3 100644 --- a/modules/billing/docs/xonotic/index.php +++ b/modules/billing/docs/xonotic/index.php @@ -1,68 +1,372 @@ -Xonotic is available for hosting on our platform. This guide covers the basics of setting up and managing your Xonotic server.
-26000- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Xonotic server:
-After your server is created, you can configure it through the control panel:
+Xonotic is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Xonotic server for your community.
+ +Check server configurationThe Xonotic server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Xonotic Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Xonotic Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Xonotic server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Xonotic Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Xonotic server hosting +
diff --git a/modules/billing/docs/xonotic/metadata.json b/modules/billing/docs/xonotic/metadata.json index c1aaedd4..fc27d192 100644 --- a/modules/billing/docs/xonotic/metadata.json +++ b/modules/billing/docs/xonotic/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Xonotic game servers", - "name": "Xonotic", - "order": 146, - "category": "todo" +{ + "description": "Setup and configuration guide for Xonotic game servers", + "name": "Xonotic", + "order": 146, + "category": "game" } \ No newline at end of file diff --git a/modules/billing/docs/zps/index.php b/modules/billing/docs/zps/index.php index e4a84eaf..a564f248 100644 --- a/modules/billing/docs/zps/index.php +++ b/modules/billing/docs/zps/index.php @@ -1,68 +1,372 @@ -Zombie Panic! Source is available for hosting on our platform. This guide covers the basics of setting up and managing your Zombie Panic! Source server.
-27015- Note: When running on a VPS or dedicated server, you can use the default port or configure a custom port in your server configuration file. -
+To create a Zombie Panic! Source server:
-After your server is created, you can configure it through the control panel:
+Zombie Panic! Source is a multiplayer game server that can be hosted on a VPS or dedicated server. This comprehensive guide covers everything you need to know about hosting a Zombie Panic! Source server for your community.
+ +Check server configurationThe Zombie Panic! Source server typically uses a configurable port. Check your server configuration files for the specific port settings.
+ +Allow server ports through your firewall:
+# UFW (Ubuntu/Debian)
+sudo ufw allow [PORT]/tcp
+sudo ufw allow [PORT]/udp
+sudo ufw reload
+
+# FirewallD (CentOS/RHEL)
+sudo firewall-cmd --permanent --add-port=[PORT]/tcp
+sudo firewall-cmd --permanent --add-port=[PORT]/udp
+sudo firewall-cmd --reload
+
+# Windows Firewall
+netsh advfirewall firewall add rule name="Zombie Panic! Source Server" dir=in action=allow protocol=TCP localport=[PORT]
+netsh advfirewall firewall add rule name="Zombie Panic! Source Server" dir=in action=allow protocol=UDP localport=[PORT]
+Servers are automatically started after creation. You can stop/start your server from the control panel.
+# Update system packages
+sudo apt update && sudo apt upgrade -y
-Connecting to Your Server
-Use your server's IP address and port to connect from the game client.
+# Create server directory
+mkdir -p ~/gameserver
+cd ~/gameserver
-Managing Files
-Access your server files via FTP using the credentials provided in your control panel.
+# Download server files (method varies by game)
+# Check official documentation for download links
+If you need assistance with your Zombie Panic! Source server:
+Download the server files from the official game website or through Steam (if applicable). Extract to a dedicated folder and run the server executable.
+ +Many game servers can be installed via SteamCMD:
+# Install SteamCMD (Ubuntu/Debian)
+sudo apt install lib32gcc-s1 steamcmd
+
+# Run SteamCMD
+steamcmd
+
+# Login and download (use your Steam credentials or anonymous)
+login anonymous
+force_install_dir /path/to/server
+app_update [APP_ID] validate
+quit
+After installation, configure your server through the configuration files typically located in the server directory.
+ +Common administrative commands (access via console or RCON):
+# Kick player
+kick [player_name]
+
+# Ban player
+ban [player_name]
+
+# Change map/level (syntax varies by game)
+changelevel [map_name]
+
+# Set admin password (if supported)
+setadminpassword [password]
+# Generic startup command structure
+./server_executable [parameters]
+-port [number] - Set the server port-maxplayers [number] - Maximum player slots-map [name] - Starting map/level-console - Enable console output-nographics - Run without graphics (headless mode)Linux (start.sh):
+#!/bin/bash
+cd /path/to/server
+./server_executable [parameters] 2>&1 | tee server.log
+chmod +x start.sh
+./start.sh
+Windows (start.bat):
+@echo off
+cd /d "%~dp0"
+server_executable.exe [parameters]
+pause
+Linux (systemd):
+# Create service file: /etc/systemd/system/gameserver.service
+[Unit]
+Description=Zombie Panic! Source Server
+After=network.target
+
+[Service]
+Type=simple
+User=gameserver
+WorkingDirectory=/home/gameserver/server
+ExecStart=/home/gameserver/server/start.sh
+Restart=on-failure
+RestartSec=10
+
+[Install]
+WantedBy=multi-user.target
+# Enable and start service
+sudo systemctl daemon-reload
+sudo systemctl enable gameserver
+sudo systemctl start gameserver
+sudo systemctl status gameserver
+# View recent log entries
+tail -f server.log
+
+# Or check system logs
+journalctl -u gameserver -f
+# Find what's using the port
+sudo lsof -i :[PORT]
+sudo netstat -tulpn | grep [PORT]
+
+# Kill the process or change server port
+Ensure all required dependencies are installed. Check the error messages for missing libraries or packages.
+ +ps aux | grep servernetstat -an | grep [PORT]htop or topiotop# Monitor memory usage
+free -h
+top -p $(pgrep -f server)
+
+# Restart server regularly via cron if needed
+0 4 * * * /home/gameserver/restart.sh
+# Increase file descriptor limits
+echo "* soft nofile 65536" >> /etc/security/limits.conf
+echo "* hard nofile 65536" >> /etc/security/limits.conf
+
+# Network tuning
+sysctl -w net.core.rmem_max=16777216
+sysctl -w net.core.wmem_max=16777216
+sysctl -w net.ipv4.tcp_rmem="4096 87380 16777216"
+sysctl -w net.ipv4.tcp_wmem="4096 87380 16777216"
+Set up monitoring to track server health:
+#!/bin/bash
+# backup.sh - Run via cron
+DATE=$(date +%Y%m%d_%H%M%S)
+BACKUP_DIR="/backups/gameserver"
+SERVER_DIR="/home/gameserver/server"
+
+# Create backup
+tar -czf $BACKUP_DIR/backup_$DATE.tar.gz -C $SERVER_DIR .
+
+# Keep only last 7 days
+find $BACKUP_DIR -name "backup_*.tar.gz" -mtime +7 -delete
+# Minimal firewall - only allow necessary ports
+sudo ufw default deny incoming
+sudo ufw default allow outgoing
+sudo ufw allow [SERVER_PORT]/tcp
+sudo ufw allow [SERVER_PORT]/udp
+sudo ufw allow 22/tcp # SSH
+sudo ufw enable
++ Last updated: November 2025 | For Zombie Panic! Source server hosting +
diff --git a/modules/billing/docs/zps/metadata.json b/modules/billing/docs/zps/metadata.json index 07d9b6f2..3cc7c7c9 100644 --- a/modules/billing/docs/zps/metadata.json +++ b/modules/billing/docs/zps/metadata.json @@ -1,6 +1,6 @@ -{ - "description": "Setup and configuration guide for Zombie Panic! Source game servers", - "name": "Zombie Panic! Source", - "order": 149, - "category": "todo" +{ + "description": "Setup and configuration guide for Zombie Panic! Source game servers", + "name": "Zombie Panic! Source", + "order": 149, + "category": "game" } \ No newline at end of file