removed docs_old
This commit is contained in:
parent
b2a99aa2c5
commit
a908ef893e
213 changed files with 0 additions and 25340 deletions
|
|
@ -1,107 +0,0 @@
|
|||
<?php
|
||||
// docs.php — simple gallery to view or download your PDFs
|
||||
|
||||
$docs = [
|
||||
[
|
||||
'key' => 'sales',
|
||||
'title' => 'Sales & Onboarding Playbook',
|
||||
'desc' => 'Messaging, ICPs, demo flow, onboarding runbook, SLAs.',
|
||||
],
|
||||
[
|
||||
'key' => 'security',
|
||||
'title' => 'Security & Compliance Playbook',
|
||||
'desc' => 'Hygiene checklist, patching cadence, backups, incident response.',
|
||||
],
|
||||
[
|
||||
'key' => 'investor',
|
||||
'title' => 'Investor One-Pager',
|
||||
'desc' => 'Market, product, traction, roadmap, team, basic financials.',
|
||||
],
|
||||
];
|
||||
?>
|
||||
<!doctype html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<title>Playbooks</title>
|
||||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||||
<style>
|
||||
:root { --bg:#0f172a; --card:#111827; --ink:#e5e7eb; --ink-dim:#9ca3af; --accent:#22d3ee; }
|
||||
*{box-sizing:border-box} body{margin:0;background:var(--bg);color:var(--ink);font:16px/1.5 system-ui, -apple-system, Segoe UI, Roboto, Arial}
|
||||
.wrap{max-width:1100px;margin:40px auto;padding:0 16px}
|
||||
h1{font-size:28px;margin:0 0 18px}
|
||||
p.lead{color:var(--ink-dim);margin:0 0 26px}
|
||||
.grid{display:grid;grid-template-columns:repeat(auto-fill,minmax(280px,1fr));gap:16px}
|
||||
.card{background:var(--card);border:1px solid #1f2937;border-radius:14px;padding:16px}
|
||||
.card h3{margin:0 0 6px;font-size:18px}
|
||||
.card p{margin:0 0 12px;color:var(--ink-dim)}
|
||||
.btns{display:flex;gap:8px;flex-wrap:wrap}
|
||||
.btn{appearance:none;border:1px solid #334155;border-radius:10px;padding:9px 12px;cursor:pointer;background:#0b1220;color:var(--ink);}
|
||||
.btn:hover{border-color:var(--accent)}
|
||||
.viewer{margin-top:12px;display:none}
|
||||
.viewer iframe{width:100%;height:680px;border:1px solid #1f2937;border-radius:12px;background:#0b1220}
|
||||
.footer{margin:36px 0 12px;color:var(--ink-dim);font-size:14px}
|
||||
a{color:var(--accent);text-decoration:none} a:hover{text-decoration:underline}
|
||||
.embed-snippet{margin-top:32px;background:#0b1220;border:1px solid #1f2937;border-radius:12px;padding:14px;color:#cbd5e1;overflow:auto}
|
||||
code{font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:13px}
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<div class="wrap">
|
||||
<h1>Playbooks</h1>
|
||||
<p class="lead">View inline or download. You can also copy an embed snippet for any page on your site.</p>
|
||||
|
||||
<div class="grid">
|
||||
<?php foreach ($docs as $doc):
|
||||
$key = htmlspecialchars($doc['key'], ENT_QUOTES, 'UTF-8');
|
||||
$title = htmlspecialchars($doc['title'], ENT_QUOTES, 'UTF-8');
|
||||
$desc = htmlspecialchars($doc['desc'], ENT_QUOTES, 'UTF-8');
|
||||
$viewerId = "viewer-" . $key;
|
||||
$src = "serve.php?doc=" . rawurlencode($key); // inline by default
|
||||
$dl = "serve.php?doc=" . rawurlencode($key) . "&download=1";
|
||||
?>
|
||||
<div class="card" id="card-<?= $key ?>">
|
||||
<h3><?= $title ?></h3>
|
||||
<p><?= $desc ?></p>
|
||||
<div class="btns">
|
||||
<button class="btn" onclick="toggleViewer('<?= $viewerId ?>','<?= $src ?>')">View inline</button>
|
||||
<a class="btn" href="<?= $dl ?>">Download</a>
|
||||
<button class="btn" onclick="copyEmbed('<?= htmlspecialchars('<iframe src=\"' . $src . '\" width=\"100%\" height=\"720\" style=\"border:1px solid #ddd;border-radius:12px\"></iframe>') ?>')">Copy embed</button>
|
||||
</div>
|
||||
<div class="viewer" id="<?= $viewerId ?>">
|
||||
<iframe loading="lazy" title="<?= $title ?>"></iframe>
|
||||
</div>
|
||||
</div>
|
||||
<?php endforeach; ?>
|
||||
</div>
|
||||
|
||||
<div class="embed-snippet">
|
||||
<strong>Generic embed snippet (replace <code>doc=</code> value):</strong>
|
||||
<pre><code><iframe src="/serve.php?doc=sales" width="100%" height="720" class="doc-iframe"></iframe></code></pre>
|
||||
</div>
|
||||
|
||||
<p class="footer">Tip: You can place <code>serve.php</code> and <code>docs.php</code> anywhere; just keep the whitelist in <code>serve.php</code> updated to match your files.</p>
|
||||
</div>
|
||||
|
||||
<script>
|
||||
function toggleViewer(id, src){
|
||||
const el = document.getElementById(id);
|
||||
const frame = el.querySelector('iframe');
|
||||
if (el.style.display === 'block') { el.style.display = 'none'; return; }
|
||||
if (!frame.getAttribute('src')) frame.setAttribute('src', src);
|
||||
el.style.display = 'block';
|
||||
el.scrollIntoView({behavior:'smooth', block:'start'});
|
||||
}
|
||||
|
||||
async function copyEmbed(html){
|
||||
try {
|
||||
await navigator.clipboard.writeText(html.replace(/"/g,'"'));
|
||||
alert('Embed code copied to clipboard!');
|
||||
} catch(e) {
|
||||
prompt('Copy embed HTML:', html.replace(/"/g,'"'));
|
||||
}
|
||||
}
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# 7 Days to Die — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
7DaysToDieServer.exe -configfile=serverconfig.xml -quit -batchmode -nographics -dedicated
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-configfile=<file>` — Server configuration XML file.
|
||||
- `-quit` — Quit after completing operations.
|
||||
- `-batchmode` — Run in batch mode without GUI.
|
||||
- `-nographics` — Disable graphics rendering.
|
||||
- `-dedicated` — Run as dedicated server.
|
||||
- `-logfile <path>` — Log file location.
|
||||
- `-UserDataFolder=<path>` — User data directory.
|
||||
- `-SaveGameFolder=<path>` — Save game directory.
|
||||
- `-configfile=<path>` — Configuration file path.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **26900** (primary)
|
||||
- Steam Query: UDP **26901** (game port + 1)
|
||||
- Web Control Panel: TCP **8080** (if enabled)
|
||||
- Telnet: TCP **8081** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `Data/` — Game data directory
|
||||
- `Logs/` — Log files directory
|
||||
- `ServerConfig/` — Configuration files (varies by game)
|
||||
|
||||
**Linux:**
|
||||
- `~/7-days-to-die/Data/` — Game data directory
|
||||
- `~/7-days-to-die/Logs/` — Log files directory
|
||||
- `~/7-days-to-die/ServerConfig/` — Configuration files
|
||||
|
||||
**Key Files:**
|
||||
- Configuration file names and locations vary significantly between Unity games
|
||||
- Common patterns: server.cfg, config.json, settings.xml
|
||||
- Check game-specific documentation for exact file locations
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for 7 Days to Die
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
File diff suppressed because it is too large
Load diff
|
|
@ -1,50 +0,0 @@
|
|||
# <Game Name> — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
<Path/Executable> <all required flags here> # exact for this game, not generic
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-flagA=<value>` — What it does. Default: `<default>`. Notes / constraints.
|
||||
- `-flagB` — …
|
||||
- (List every valid server flag, 10–40+ as applicable. Include networking, logging, perf, mod-loading, VAC/BE/EAC, RCON, headless clients, etc.)
|
||||
|
||||
**Ports**
|
||||
- Game UDP: **P** (assigned)
|
||||
- Query/Steam sockets/etc: **P+1**, **P+2**, …
|
||||
- RCON / BE / SourceTV / etc: exact numbers or relative math
|
||||
(Spell out all auxiliary ports, protocols, fixed vs relative.)
|
||||
|
||||
## Config Files & Locations
|
||||
- `<path>/server.cfg` — description
|
||||
- `<path>/basic.cfg` — …
|
||||
- `<path>/logs/*.log` — …
|
||||
- **Mods**: where mod files go, keys/signatures, load order files.
|
||||
- **Workshop cache** (if relevant).
|
||||
- Include common paths for Windows & Linux.
|
||||
|
||||
## Steam Workshop (if supported)
|
||||
- How to mount collections / API keys / start map IDs.
|
||||
- Where files cache on disk.
|
||||
- Any special caveats.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **Mod A (e.g., AMX Mod X / ACE3 / Exile / RocketMod / Oxide / uMod / BepInEx / DarkRP / EssentialsX)**
|
||||
- What it’s for.
|
||||
- **Install**: exact folder paths, files to edit, any keys/signatures, load order.
|
||||
- **Configure**: main config files + common options.
|
||||
- (Repeat for each widely used mod for this game.)
|
||||
|
||||
## Database (if used)
|
||||
- Engine (e.g., **MySQL**, SQLite, PostgreSQL).
|
||||
- Connection file & keys to edit (e.g., `HiveExt.ini`, `database.json`, `config.yml`).
|
||||
- Schema notes, migrations, indexes, backup/restore steps.
|
||||
|
||||
## Administration & Scripting (if applicable)
|
||||
- RCON tools / admin plugins.
|
||||
- Backups, rotation, auto-update strategy.
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
- Symptom → likely cause → resolution, with file/flag names.
|
||||
- Include all common errors seen in forums/issue trackers for this game.
|
||||
- Networking, signature/anticheat, mod version mismatches, perf, crashes, persistence, etc.
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Abiotic Factor — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./abiotic-factor_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `abiotic-factor_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/abiotic-factor/server.cfg` — Main server configuration
|
||||
- `~/abiotic-factor/config/` — Configuration directory
|
||||
- `~/abiotic-factor/logs/` — Log files directory
|
||||
- `~/abiotic-factor/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Abiotic Factor
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Action Half-Life — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./action-half-life_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `action-half-life_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/action-half-life/server.cfg` — Main server configuration
|
||||
- `~/action-half-life/config/` — Configuration directory
|
||||
- `~/action-half-life/logs/` — Log files directory
|
||||
- `~/action-half-life/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Action Half-Life
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Action: Source — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./action-source_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `action-source_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/action-source/server.cfg` — Main server configuration
|
||||
- `~/action-source/config/` — Configuration directory
|
||||
- `~/action-source/logs/` — Log files directory
|
||||
- `~/action-source/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Action: Source
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Aliens vs Predator — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./aliens-vs-predator_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `aliens-vs-predator_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/aliens-vs-predator/server.cfg` — Main server configuration
|
||||
- `~/aliens-vs-predator/config/` — Configuration directory
|
||||
- `~/aliens-vs-predator/logs/` — Log files directory
|
||||
- `~/aliens-vs-predator/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Aliens vs Predator
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,210 +0,0 @@
|
|||
Game,Sources
|
||||
7 Days to Die,"G-Portal, GameServers.com, LinuxGSM"
|
||||
ARK: Survival Ascended,Nitrado
|
||||
ARK: Survival Evolved,"G-Portal, LinuxGSM"
|
||||
ARMA 3,LinuxGSM
|
||||
Abiotic Factor,Nitrado
|
||||
Action Half-Life,LinuxGSM
|
||||
Action: Source,LinuxGSM
|
||||
Aliens vs Predator,OGP
|
||||
Aloft,"G-Portal, Nitrado"
|
||||
American Truck Simulator,"LinuxGSM, Nitrado"
|
||||
Arma 2,OGP
|
||||
Arma 2 Combined Operations,OGP
|
||||
Arma 2 Operation Arrowhead,OGP
|
||||
Arma 3,G-Portal
|
||||
Arma Reforger,"G-Portal, LinuxGSM"
|
||||
Assetto Corsa,LinuxGSM
|
||||
Assetto Corsa Competizione,G-Portal
|
||||
Astroneer,G-Portal
|
||||
Atlas,G-Portal
|
||||
Avorion,"G-Portal, LinuxGSM"
|
||||
BATTALION: Legacy,LinuxGSM
|
||||
Ballistic Overkill,LinuxGSM
|
||||
Barotrauma,"G-Portal, LinuxGSM"
|
||||
Base Defense,LinuxGSM
|
||||
Battlefield 1942,LinuxGSM
|
||||
Battlefield 3,G-Portal
|
||||
Battlefield 4,"G-Portal, GameServers.com"
|
||||
Battlefield: Vietnam,LinuxGSM
|
||||
Black Mesa: Deathmatch,LinuxGSM
|
||||
Blade Symphony,LinuxGSM
|
||||
BrainBread 2,LinuxGSM
|
||||
Brainbread,LinuxGSM
|
||||
Call of Duty,LinuxGSM
|
||||
Call of Duty 2,LinuxGSM
|
||||
Call of Duty 4,LinuxGSM
|
||||
Call of Duty: United Offensive,LinuxGSM
|
||||
Call of Duty: World at War,LinuxGSM
|
||||
Chivalry: Medieval Warfare,LinuxGSM
|
||||
Citadel - Forged with fire,G-Portal
|
||||
Codename CURE,LinuxGSM
|
||||
Colony Survival,LinuxGSM
|
||||
Conan Exiles,G-Portal
|
||||
Core Keeper,"G-Portal, LinuxGSM"
|
||||
Counter-Strike,"G-Portal, LinuxGSM"
|
||||
Counter-Strike 2,"G-Portal, GameServers.com, LinuxGSM"
|
||||
Counter-Strike: Condition Zero,LinuxGSM
|
||||
Counter-Strike: Global Offensive,LinuxGSM
|
||||
Counter-Strike: Source,"GameServers.com, LinuxGSM"
|
||||
Craftopia,"G-Portal, LinuxGSM"
|
||||
CryoFall,G-Portal
|
||||
Day of Defeat,LinuxGSM
|
||||
Day of Defeat: Source,LinuxGSM
|
||||
Day of Dragons,"G-Portal, LinuxGSM"
|
||||
Day of Infamy,LinuxGSM
|
||||
DayZ,LinuxGSM
|
||||
DayZ Mod for Arma2CO ,OGP
|
||||
Dead Matter,G-Portal
|
||||
Deadside,G-Portal
|
||||
Deadside (Console),G-Portal
|
||||
Deathmatch Classic,LinuxGSM
|
||||
Don't Starve Together,"G-Portal, LinuxGSM"
|
||||
Double Action: Boogaloo,LinuxGSM
|
||||
Dune: Awakening,G-Portal
|
||||
Dystopia,LinuxGSM
|
||||
ET: Legacy,LinuxGSM
|
||||
Eco,"G-Portal, LinuxGSM"
|
||||
Empires Mod,LinuxGSM
|
||||
Empyrion: Galactic Survival,G-Portal
|
||||
Enshrouded,G-Portal
|
||||
Euro Truck Simulator 2,LinuxGSM
|
||||
Euro Truck Simulator 2 / American Truck Simulator,G-Portal
|
||||
Factorio,"G-Portal, LinuxGSM"
|
||||
Farming Simulator,G-Portal
|
||||
Farming Simulator 2019,GameServers.com
|
||||
Farming Simulator 2022,GameServers.com
|
||||
Farming Simulator 2025,GameServers.com
|
||||
Farming Simulator 25,G-Portal
|
||||
Fistful of Frags,LinuxGSM
|
||||
FiveM,G-Portal
|
||||
Garry's Mod,G-Portal
|
||||
Garry’s Mod,LinuxGSM
|
||||
Ground Branch,G-Portal
|
||||
HEAT,G-Portal
|
||||
HYPERCHARGE: Unboxed,LinuxGSM
|
||||
Half-Life 2: Deathmatch,LinuxGSM
|
||||
Half-Life Deathmatch: Source,LinuxGSM
|
||||
Half-Life: Deathmatch,LinuxGSM
|
||||
Hell Let Loose,G-Portal
|
||||
Humanitz,LinuxGSM
|
||||
Hurtworld,"G-Portal, LinuxGSM"
|
||||
IOSoccer,LinuxGSM
|
||||
Icarus,G-Portal
|
||||
Insurgency,LinuxGSM
|
||||
Insurgency Sandstorm,G-Portal
|
||||
Insurgency: Sandstorm,LinuxGSM
|
||||
Jedi Knight II: Jedi Outcast,LinuxGSM
|
||||
Just Cause 2,LinuxGSM
|
||||
Just Cause 3,LinuxGSM
|
||||
Killing Floor,LinuxGSM
|
||||
Killing Floor 2,"G-Portal, LinuxGSM"
|
||||
LEAP,G-Portal
|
||||
Last Oasis,G-Portal
|
||||
Left 4 Dead,LinuxGSM
|
||||
Left 4 Dead 2,LinuxGSM
|
||||
Life is Feudal,G-Portal
|
||||
Longvinter,G-Portal
|
||||
Medal of Honor: Allied Assault,LinuxGSM
|
||||
Memories of Mars,LinuxGSM
|
||||
Minecraft,"G-Portal, GameServers.com"
|
||||
Minecraft: Bedrock Edition,LinuxGSM
|
||||
Minecraft: Java Edition,LinuxGSM
|
||||
Mordhau,"G-Portal, LinuxGSM"
|
||||
Multi Theft Auto,LinuxGSM
|
||||
Mumble,LinuxGSM
|
||||
Myth of Empires,Nitrado
|
||||
NS2: Combat,LinuxGSM
|
||||
Natural Selection,LinuxGSM
|
||||
Natural Selection 2,LinuxGSM
|
||||
Necesse,LinuxGSM
|
||||
No More Room in Hell,LinuxGSM
|
||||
Nuclear Dawn,LinuxGSM
|
||||
Onset,LinuxGSM
|
||||
Operation: Harsh Doorstop,LinuxGSM
|
||||
Opposing Force,LinuxGSM
|
||||
Outlaws of the Old West,G-Portal
|
||||
Outpost Zero,Nitrado
|
||||
Palworld,"G-Portal, LinuxGSM"
|
||||
Palworld Xbox,Nitrado
|
||||
PaperMC,LinuxGSM
|
||||
Path of Titans,"G-Portal, Nitrado"
|
||||
Pavlov VR,"G-Portal, LinuxGSM"
|
||||
"Pirates, Vikings, & Knights II",LinuxGSM
|
||||
PixARK,Nitrado
|
||||
Project CARS 2,LinuxGSM
|
||||
Project Cars,LinuxGSM
|
||||
Project Zomboid,"G-Portal, GameServers.com, LinuxGSM"
|
||||
Quake 2,LinuxGSM
|
||||
Quake 3: Arena,LinuxGSM
|
||||
Quake 4,LinuxGSM
|
||||
Quake Live,LinuxGSM
|
||||
Quake World,LinuxGSM
|
||||
Red Orchestra: Ostfront 41-45,LinuxGSM
|
||||
RedM,G-Portal
|
||||
Reign of Kings,G-Portal
|
||||
Rem Survival,G-Portal
|
||||
Return to Castle Wolfenstein,LinuxGSM
|
||||
Ricochet,LinuxGSM
|
||||
Rising World,LinuxGSM
|
||||
Risk of Rain 2,Nitrado
|
||||
Rust,"G-Portal, GameServers.com, LinuxGSM"
|
||||
SCP: Secret Laboratory,"LinuxGSM, Nitrado"
|
||||
SCP: Secret Laboratory ServerMod,LinuxGSM
|
||||
SCUM,Nitrado
|
||||
San Andreas Multiplayer,LinuxGSM
|
||||
Satisfactory,"G-Portal, LinuxGSM"
|
||||
Scum,G-Portal
|
||||
Skyrim Together Reborn Mod,G-Portal
|
||||
Soldat,LinuxGSM
|
||||
Soldier of Fortune 2: Double Helix Gold,LinuxGSM
|
||||
Sons Of The Forest,Nitrado
|
||||
Sons of the Forest,G-Portal
|
||||
Soulmask,"G-Portal, LinuxGSM"
|
||||
Source Forts Classic,LinuxGSM
|
||||
Space Engineers,"G-Portal, Nitrado"
|
||||
Squad,"G-Portal, LinuxGSM"
|
||||
Squad 44,LinuxGSM
|
||||
Starbound,"G-Portal, LinuxGSM"
|
||||
Stationeers,LinuxGSM
|
||||
Staxel,G-Portal
|
||||
StickyBots,LinuxGSM
|
||||
Subsistence,"G-Portal, Nitrado"
|
||||
Survive the Nights,LinuxGSM
|
||||
Sven Co-op,LinuxGSM
|
||||
Team Fortress 2,"LinuxGSM, Nitrado"
|
||||
Team Fortress Classic,LinuxGSM
|
||||
Teamspeak 3,"G-Portal, LinuxGSM"
|
||||
Tebex,G-Portal
|
||||
Teeworlds,LinuxGSM
|
||||
TerraTech Worlds,G-Portal
|
||||
Terraria,"G-Portal, LinuxGSM, Nitrado"
|
||||
The Forest,"G-Portal, Nitrado"
|
||||
The Front,LinuxGSM
|
||||
The Isle,"G-Portal, LinuxGSM, Nitrado"
|
||||
The Lord of the Rings: Return to Moria,"G-Portal, Nitrado"
|
||||
The Specialists,LinuxGSM
|
||||
Tinkertown,G-Portal
|
||||
Tower Unite,LinuxGSM
|
||||
Unreal Tournament,LinuxGSM
|
||||
Unreal Tournament 2004,LinuxGSM
|
||||
Unreal Tournament 3,LinuxGSM
|
||||
Unreal Tournament 99,LinuxGSM
|
||||
Unturned,"G-Portal, LinuxGSM, Nitrado"
|
||||
Urban Terror 4,OGP
|
||||
V Rising,G-Portal
|
||||
Valheim,"G-Portal, GameServers.com, LinuxGSM"
|
||||
Vampire Slayer,LinuxGSM
|
||||
Velocity Proxy,LinuxGSM
|
||||
Vintage Story,"G-Portal, LinuxGSM"
|
||||
Warfork,LinuxGSM
|
||||
Warsow,OGP
|
||||
WaterfallMC,LinuxGSM
|
||||
Wolfenstein: Enemy Territory,LinuxGSM
|
||||
World Titans War,G-Portal
|
||||
Wreckfest,G-Portal
|
||||
Wreckfest 2,G-Portal
|
||||
Wurm Unlimited,LinuxGSM
|
||||
Xonotic,LinuxGSM
|
||||
Zombie Master: Reborn,LinuxGSM
|
||||
Zombie Panic! Source,LinuxGSM
|
||||
|
|
|
@ -1,107 +0,0 @@
|
|||
# Aloft — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./aloft_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `aloft_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/aloft/server.cfg` — Main server configuration
|
||||
- `~/aloft/config/` — Configuration directory
|
||||
- `~/aloft/logs/` — Log files directory
|
||||
- `~/aloft/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Aloft
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# American Truck Simulator — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./american-truck-simulator_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `american-truck-simulator_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/american-truck-simulator/server.cfg` — Main server configuration
|
||||
- `~/american-truck-simulator/config/` — Configuration directory
|
||||
- `~/american-truck-simulator/logs/` — Log files directory
|
||||
- `~/american-truck-simulator/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for American Truck Simulator
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,150 +0,0 @@
|
|||
# ARK: Survival Ascended — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
ArkAscendedServer.exe TheIsland?listen?SessionName="My ARK Server"?ServerPassword=""?ServerAdminPassword="adminpass"?Port=7777?QueryPort=27015?MaxPlayers=70
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- Map name (TheIsland, Ragnarok, Extinction, etc.) — Starting map.
|
||||
- `?listen` — Enable server listening.
|
||||
- `?SessionName="<name>"` — Server name in browser.
|
||||
- `?ServerPassword="<pass>"` — Server password.
|
||||
- `?ServerAdminPassword="<pass>"` — Admin password.
|
||||
- `?Port=<port>` — Game port. Default: 7777.
|
||||
- `?QueryPort=<port>` — Query port. Default: 27015.
|
||||
- `?MaxPlayers=<num>` — Maximum players (1-200).
|
||||
- `?PVE=<true|false>` — PvE mode.
|
||||
- `?RCONEnabled=<true|false>` — Enable RCON.
|
||||
- `?RCONPort=<port>` — RCON port.
|
||||
- `?DifficultyOffset=<0.0-1.0>` — Difficulty level.
|
||||
- `?OverrideOfficialDifficulty=<1.0-10.0>` — Override difficulty.
|
||||
- `?TamingSpeedMultiplier=<1.0+>` — Taming speed.
|
||||
- `?XPMultiplier=<1.0+>` — Experience multiplier.
|
||||
- `?HarvestAmountMultiplier=<1.0+>` — Harvest amount.
|
||||
- `?AllowFlyerCarryPvE=<true|false>` — Allow flyer carry in PvE.
|
||||
- `?AlwaysAllowStructurePickup=<true|false>` — Allow structure pickup.
|
||||
- `?BattlEye=<true|false>` — Enable BattlEye anti-cheat.
|
||||
- `-log` — Enable logging.
|
||||
- `-NoHangDetection` — Disable hang detection.
|
||||
- `-UseDynamicConfig` — Use dynamic configuration.
|
||||
- `-ConfigSubDir=<dir>` — Config subdirectory.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **7777** (primary)
|
||||
- Query: UDP **27015** (Steam query)
|
||||
- RCON: TCP **27020** (if enabled)
|
||||
- Raw UDP: UDP **7778** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `WindowsServer/ARK: Survival Ascended/Saved/Config/WindowsServer/` — Configuration directory
|
||||
- `WindowsServer/ARK: Survival Ascended/Saved/Logs/` — Log files
|
||||
- `WindowsServer/ARK: Survival Ascended/Saved/SaveGames/` — Save files
|
||||
|
||||
**Linux:**
|
||||
- `/home/ark-survival-ascended/Saved/Config/LinuxServer/` — Configuration directory
|
||||
- `/home/ark-survival-ascended/Saved/Logs/` — Log files
|
||||
- `/home/ark-survival-ascended/Saved/SaveGames/` — Save files
|
||||
|
||||
**Key Files:**
|
||||
- **GameUserSettings.ini**: Main server configuration
|
||||
- **Game.ini**: Advanced game settings
|
||||
- **Engine.ini**: Engine-specific settings
|
||||
|
||||
## Steam Workshop
|
||||
**Mod Installation:**
|
||||
1. Subscribe to mods via Steam Workshop or ARK server manager
|
||||
2. Add mod IDs to server startup parameters or GameUserSettings.ini
|
||||
3. Server downloads mods automatically on startup
|
||||
|
||||
**Configuration:**
|
||||
- Windows: `ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini`
|
||||
- Linux: `ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini`
|
||||
- Add line: `ActiveMods=mod_id_1,mod_id_2,mod_id_3`
|
||||
|
||||
**Mod Loading:**
|
||||
- Mods load in the order specified in ActiveMods
|
||||
- Some mods have dependencies that must load first
|
||||
- Server must restart after mod changes
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/346110/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/346110/`
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for ARK: Survival Ascended
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
**Engine**: SQLite
|
||||
|
||||
**Configuration**:
|
||||
- Database settings typically in main server configuration file
|
||||
- Connection parameters: host, port, database name, credentials
|
||||
- Enable persistence features in server configuration
|
||||
|
||||
**Setup**:
|
||||
1. Install database engine if required
|
||||
2. Create database and user with appropriate permissions
|
||||
3. Configure connection settings in server config
|
||||
4. Test connection before starting server
|
||||
5. Set up automated backups
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,150 +0,0 @@
|
|||
# ARK: Survival Evolved — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
ShooterGameServer.exe TheIsland?listen?SessionName="My ARK Server"?ServerPassword=""?ServerAdminPassword="adminpass"?Port=7777?QueryPort=27015?MaxPlayers=70
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- Map name (TheIsland, Ragnarok, Extinction, etc.) — Starting map.
|
||||
- `?listen` — Enable server listening.
|
||||
- `?SessionName="<name>"` — Server name in browser.
|
||||
- `?ServerPassword="<pass>"` — Server password.
|
||||
- `?ServerAdminPassword="<pass>"` — Admin password.
|
||||
- `?Port=<port>` — Game port. Default: 7777.
|
||||
- `?QueryPort=<port>` — Query port. Default: 27015.
|
||||
- `?MaxPlayers=<num>` — Maximum players (1-200).
|
||||
- `?PVE=<true|false>` — PvE mode.
|
||||
- `?RCONEnabled=<true|false>` — Enable RCON.
|
||||
- `?RCONPort=<port>` — RCON port.
|
||||
- `?DifficultyOffset=<0.0-1.0>` — Difficulty level.
|
||||
- `?OverrideOfficialDifficulty=<1.0-10.0>` — Override difficulty.
|
||||
- `?TamingSpeedMultiplier=<1.0+>` — Taming speed.
|
||||
- `?XPMultiplier=<1.0+>` — Experience multiplier.
|
||||
- `?HarvestAmountMultiplier=<1.0+>` — Harvest amount.
|
||||
- `?AllowFlyerCarryPvE=<true|false>` — Allow flyer carry in PvE.
|
||||
- `?AlwaysAllowStructurePickup=<true|false>` — Allow structure pickup.
|
||||
- `?BattlEye=<true|false>` — Enable BattlEye anti-cheat.
|
||||
- `-log` — Enable logging.
|
||||
- `-NoHangDetection` — Disable hang detection.
|
||||
- `-UseDynamicConfig` — Use dynamic configuration.
|
||||
- `-ConfigSubDir=<dir>` — Config subdirectory.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **7777** (primary)
|
||||
- Query: UDP **27015** (Steam query)
|
||||
- RCON: TCP **27020** (if enabled)
|
||||
- Raw UDP: UDP **7778** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `WindowsServer/ARK: Survival Evolved/Saved/Config/WindowsServer/` — Configuration directory
|
||||
- `WindowsServer/ARK: Survival Evolved/Saved/Logs/` — Log files
|
||||
- `WindowsServer/ARK: Survival Evolved/Saved/SaveGames/` — Save files
|
||||
|
||||
**Linux:**
|
||||
- `/home/ark-survival-evolved/Saved/Config/LinuxServer/` — Configuration directory
|
||||
- `/home/ark-survival-evolved/Saved/Logs/` — Log files
|
||||
- `/home/ark-survival-evolved/Saved/SaveGames/` — Save files
|
||||
|
||||
**Key Files:**
|
||||
- **GameUserSettings.ini**: Main server configuration
|
||||
- **Game.ini**: Advanced game settings
|
||||
- **Engine.ini**: Engine-specific settings
|
||||
|
||||
## Steam Workshop
|
||||
**Mod Installation:**
|
||||
1. Subscribe to mods via Steam Workshop or ARK server manager
|
||||
2. Add mod IDs to server startup parameters or GameUserSettings.ini
|
||||
3. Server downloads mods automatically on startup
|
||||
|
||||
**Configuration:**
|
||||
- Windows: `ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini`
|
||||
- Linux: `ShooterGame/Saved/Config/LinuxServer/GameUserSettings.ini`
|
||||
- Add line: `ActiveMods=mod_id_1,mod_id_2,mod_id_3`
|
||||
|
||||
**Mod Loading:**
|
||||
- Mods load in the order specified in ActiveMods
|
||||
- Some mods have dependencies that must load first
|
||||
- Server must restart after mod changes
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/346110/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/346110/`
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for ARK: Survival Evolved
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
**Engine**: SQLite
|
||||
|
||||
**Configuration**:
|
||||
- Database settings typically in main server configuration file
|
||||
- Connection parameters: host, port, database name, credentials
|
||||
- Enable persistence features in server configuration
|
||||
|
||||
**Setup**:
|
||||
1. Install database engine if required
|
||||
2. Create database and user with appropriate permissions
|
||||
3. Configure connection settings in server config
|
||||
4. Test connection before starting server
|
||||
5. Set up automated backups
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,111 +0,0 @@
|
|||
# Arma 2 Combined Operations — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./arma-2-combined-operations_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `arma-2-combined-operations_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/arma-2-combined-operations/server.cfg` — Main server configuration
|
||||
- `~/arma-2-combined-operations/config/` — Configuration directory
|
||||
- `~/arma-2-combined-operations/logs/` — Log files directory
|
||||
- `~/arma-2-combined-operations/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Arma 2 Combined Operations
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Bad module info" / Addon errors**
|
||||
- **Cause**: Corrupted mod files or version mismatches
|
||||
- **Fix**: Verify mod integrity, ensure client-server version matching, check signature verification
|
||||
|
||||
**"Session lost" during gameplay**
|
||||
- **Cause**: Network issues or memory problems
|
||||
- **Fix**: Optimize basic.cfg network settings, increase server memory allocation, check mod conflicts
|
||||
|
||||
**High memory usage / Server crashes**
|
||||
- **Cause**: Memory leaks from scripts or excessive mod usage
|
||||
- **Fix**: Restart server regularly, optimize mission scripts, reduce active mod count
|
||||
|
||||
**BattlEye script restriction kicks**
|
||||
- **Cause**: Scripts triggering BE filters
|
||||
- **Fix**: Update BattlEye filters for installed mods, configure proper exceptions
|
||||
|
||||
**Signature verification failed**
|
||||
- **Cause**: Missing or mismatched .bikey files
|
||||
- **Fix**: Ensure all mod .bikey files present in keys/ directory, verify verifySignatures setting
|
||||
|
||||
**Performance issues / Low FPS**
|
||||
- **Cause**: Complex missions, AI overload, or insufficient server resources
|
||||
- **Fix**: Optimize mission complexity, reduce AI count, upgrade server hardware, tune basic.cfg
|
||||
|
|
@ -1,118 +0,0 @@
|
|||
# Arma 2 Operation Arrowhead — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
arma2oaserver.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=ServerProfile -mod=@mod1;@mod2
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-config=<file>` — Server config file (server.cfg).
|
||||
- `-cfg=<file>` — Basic config file (basic.cfg).
|
||||
- `-profiles=<dir>` — Profile directory.
|
||||
- `-mod=<mods>` — Mod folders (semicolon separated).
|
||||
- `-serverMod=<mods>` — Server-side only mods.
|
||||
- `-name=<profilename>` — Server profile name.
|
||||
- `-world=<worldname>` — Empty world name.
|
||||
- `-noSound` — Disable sound processing.
|
||||
- `-nosplash` — Skip intro videos.
|
||||
- `-noPause` — Don't pause when not focused.
|
||||
- `-cpuCount=<num>` — CPU core count override.
|
||||
- `-maxMem=<mb>` — Maximum memory usage.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Query: UDP **2303** (game port + 1)
|
||||
- BattlEye: UDP **2344** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Arma 2 Operation Arrowhead
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Bad module info" / Addon errors**
|
||||
- **Cause**: Corrupted mod files or version mismatches
|
||||
- **Fix**: Verify mod integrity, ensure client-server version matching, check signature verification
|
||||
|
||||
**"Session lost" during gameplay**
|
||||
- **Cause**: Network issues or memory problems
|
||||
- **Fix**: Optimize basic.cfg network settings, increase server memory allocation, check mod conflicts
|
||||
|
||||
**High memory usage / Server crashes**
|
||||
- **Cause**: Memory leaks from scripts or excessive mod usage
|
||||
- **Fix**: Restart server regularly, optimize mission scripts, reduce active mod count
|
||||
|
||||
**BattlEye script restriction kicks**
|
||||
- **Cause**: Scripts triggering BE filters
|
||||
- **Fix**: Update BattlEye filters for installed mods, configure proper exceptions
|
||||
|
||||
**Signature verification failed**
|
||||
- **Cause**: Missing or mismatched .bikey files
|
||||
- **Fix**: Ensure all mod .bikey files present in keys/ directory, verify verifySignatures setting
|
||||
|
||||
**Performance issues / Low FPS**
|
||||
- **Cause**: Complex missions, AI overload, or insufficient server resources
|
||||
- **Fix**: Optimize mission complexity, reduce AI count, upgrade server hardware, tune basic.cfg
|
||||
|
|
@ -1,118 +0,0 @@
|
|||
# Arma 2 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
arma2oaserver.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=ServerProfile -mod=@mod1;@mod2
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-config=<file>` — Server config file (server.cfg).
|
||||
- `-cfg=<file>` — Basic config file (basic.cfg).
|
||||
- `-profiles=<dir>` — Profile directory.
|
||||
- `-mod=<mods>` — Mod folders (semicolon separated).
|
||||
- `-serverMod=<mods>` — Server-side only mods.
|
||||
- `-name=<profilename>` — Server profile name.
|
||||
- `-world=<worldname>` — Empty world name.
|
||||
- `-noSound` — Disable sound processing.
|
||||
- `-nosplash` — Skip intro videos.
|
||||
- `-noPause` — Don't pause when not focused.
|
||||
- `-cpuCount=<num>` — CPU core count override.
|
||||
- `-maxMem=<mb>` — Maximum memory usage.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Query: UDP **2303** (game port + 1)
|
||||
- BattlEye: UDP **2344** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Arma 2
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Bad module info" / Addon errors**
|
||||
- **Cause**: Corrupted mod files or version mismatches
|
||||
- **Fix**: Verify mod integrity, ensure client-server version matching, check signature verification
|
||||
|
||||
**"Session lost" during gameplay**
|
||||
- **Cause**: Network issues or memory problems
|
||||
- **Fix**: Optimize basic.cfg network settings, increase server memory allocation, check mod conflicts
|
||||
|
||||
**High memory usage / Server crashes**
|
||||
- **Cause**: Memory leaks from scripts or excessive mod usage
|
||||
- **Fix**: Restart server regularly, optimize mission scripts, reduce active mod count
|
||||
|
||||
**BattlEye script restriction kicks**
|
||||
- **Cause**: Scripts triggering BE filters
|
||||
- **Fix**: Update BattlEye filters for installed mods, configure proper exceptions
|
||||
|
||||
**Signature verification failed**
|
||||
- **Cause**: Missing or mismatched .bikey files
|
||||
- **Fix**: Ensure all mod .bikey files present in keys/ directory, verify verifySignatures setting
|
||||
|
||||
**Performance issues / Low FPS**
|
||||
- **Cause**: Complex missions, AI overload, or insufficient server resources
|
||||
- **Fix**: Optimize mission complexity, reduce AI count, upgrade server hardware, tune basic.cfg
|
||||
|
|
@ -1,145 +0,0 @@
|
|||
# Arma 3 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
arma3server_x64.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=ServerProfile -name=server -serverMod=""
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-config=<file>` — Server config file (server.cfg).
|
||||
- `-cfg=<file>` — Basic config file (basic.cfg).
|
||||
- `-profiles=<dir>` — Profile directory.
|
||||
- `-name=<profilename>` — Server profile name.
|
||||
- `-serverMod="<mods>"` — Server-side only mods (semicolon separated).
|
||||
- `-mod="<mods>"` — Client and server mods (semicolon separated).
|
||||
- `-world=<worldname>` — Empty world for headless client.
|
||||
- `-autoInit` — Auto-initialize mission.
|
||||
- `-loadMissionToMemory` — Load mission into memory.
|
||||
- `-noSound` — Disable sound.
|
||||
- `-enableHT` — Enable hyperthreading.
|
||||
- `-hugepages` — Enable huge pages (Linux).
|
||||
- `-malloc=<allocator>` — Memory allocator.
|
||||
- `-maxMem=<mb>` — Maximum memory.
|
||||
- `-cpuCount=<num>` — CPU core count.
|
||||
- `-exThreads=<num>` — Extra threads.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Steam Query: UDP **2303** (game port + 1)
|
||||
- BattlEye: UDP **2344** (game port + 42)
|
||||
- VON: UDP **2304** (game port + 2)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
**Mod Installation:**
|
||||
1. Subscribe to mods via Steam Workshop
|
||||
2. Add mod IDs to server startup: `-mod="@workshop_id_1;@workshop_id_2"`
|
||||
3. For server-only mods use: `-serverMod="@mod_folder"`
|
||||
|
||||
**Workshop Collection:**
|
||||
- Create Steam collection with all server mods
|
||||
- Use Arma 3 Server tools or community launchers for bulk downloading
|
||||
- Verify all clients have same mod versions
|
||||
|
||||
**Mod Loading:**
|
||||
- Order matters for some mods (CBA_A3 should load first)
|
||||
- Use proper folder structure: `@mod_name/addons/*.pbo`
|
||||
- Include signature files (.bisign) for key verification
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/107410/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/107410/`
|
||||
|
||||
## Common Mods (curated)
|
||||
- **ACE3**
|
||||
- **Purpose**: Advanced Combat Environment - realistic medical, ballistics, and logistics.
|
||||
- **Install**: Subscribe via Workshop, add `@ace` to startup mods.
|
||||
- **Configure**: ACE settings via in-game addon options or mission parameters.
|
||||
|
||||
- **CBA_A3**
|
||||
- **Purpose**: Community Base Addons - framework required by most Arma 3 mods.
|
||||
- **Install**: Subscribe via Workshop, ensure loads before other mods.
|
||||
- **Configure**: No direct configuration - provides API for other mods.
|
||||
|
||||
- **TFAR (Task Force Radio)**
|
||||
- **Purpose**: Realistic radio communication system.
|
||||
- **Install**: Workshop subscription, requires TeamSpeak 3 plugin for clients.
|
||||
- **Configure**: Radio frequencies and settings in mission files.
|
||||
|
||||
- **RHS: Armed Forces**
|
||||
- **Purpose**: High-quality modern military units and equipment.
|
||||
- **Install**: Subscribe to RHS collections via Workshop.
|
||||
- **Configure**: Unit availability configured in mission editor.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Bad module info" / Addon errors**
|
||||
- **Cause**: Corrupted mod files or version mismatches
|
||||
- **Fix**: Verify mod integrity, ensure client-server version matching, check signature verification
|
||||
|
||||
**"Session lost" during gameplay**
|
||||
- **Cause**: Network issues or memory problems
|
||||
- **Fix**: Optimize basic.cfg network settings, increase server memory allocation, check mod conflicts
|
||||
|
||||
**High memory usage / Server crashes**
|
||||
- **Cause**: Memory leaks from scripts or excessive mod usage
|
||||
- **Fix**: Restart server regularly, optimize mission scripts, reduce active mod count
|
||||
|
||||
**BattlEye script restriction kicks**
|
||||
- **Cause**: Scripts triggering BE filters
|
||||
- **Fix**: Update BattlEye filters for installed mods, configure proper exceptions
|
||||
|
||||
**Signature verification failed**
|
||||
- **Cause**: Missing or mismatched .bikey files
|
||||
- **Fix**: Ensure all mod .bikey files present in keys/ directory, verify verifySignatures setting
|
||||
|
||||
**Performance issues / Low FPS**
|
||||
- **Cause**: Complex missions, AI overload, or insufficient server resources
|
||||
- **Fix**: Optimize mission complexity, reduce AI count, upgrade server hardware, tune basic.cfg
|
||||
|
|
@ -1,118 +0,0 @@
|
|||
# Arma Reforger — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
arma2oaserver.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=ServerProfile -mod=@mod1;@mod2
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-config=<file>` — Server config file (server.cfg).
|
||||
- `-cfg=<file>` — Basic config file (basic.cfg).
|
||||
- `-profiles=<dir>` — Profile directory.
|
||||
- `-mod=<mods>` — Mod folders (semicolon separated).
|
||||
- `-serverMod=<mods>` — Server-side only mods.
|
||||
- `-name=<profilename>` — Server profile name.
|
||||
- `-world=<worldname>` — Empty world name.
|
||||
- `-noSound` — Disable sound processing.
|
||||
- `-nosplash` — Skip intro videos.
|
||||
- `-noPause` — Don't pause when not focused.
|
||||
- `-cpuCount=<num>` — CPU core count override.
|
||||
- `-maxMem=<mb>` — Maximum memory usage.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Query: UDP **2303** (game port + 1)
|
||||
- BattlEye: UDP **2344** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Arma Reforger
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Bad module info" / Addon errors**
|
||||
- **Cause**: Corrupted mod files or version mismatches
|
||||
- **Fix**: Verify mod integrity, ensure client-server version matching, check signature verification
|
||||
|
||||
**"Session lost" during gameplay**
|
||||
- **Cause**: Network issues or memory problems
|
||||
- **Fix**: Optimize basic.cfg network settings, increase server memory allocation, check mod conflicts
|
||||
|
||||
**High memory usage / Server crashes**
|
||||
- **Cause**: Memory leaks from scripts or excessive mod usage
|
||||
- **Fix**: Restart server regularly, optimize mission scripts, reduce active mod count
|
||||
|
||||
**BattlEye script restriction kicks**
|
||||
- **Cause**: Scripts triggering BE filters
|
||||
- **Fix**: Update BattlEye filters for installed mods, configure proper exceptions
|
||||
|
||||
**Signature verification failed**
|
||||
- **Cause**: Missing or mismatched .bikey files
|
||||
- **Fix**: Ensure all mod .bikey files present in keys/ directory, verify verifySignatures setting
|
||||
|
||||
**Performance issues / Low FPS**
|
||||
- **Cause**: Complex missions, AI overload, or insufficient server resources
|
||||
- **Fix**: Optimize mission complexity, reduce AI count, upgrade server hardware, tune basic.cfg
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Assetto Corsa Competizione — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./assetto-corsa-competizione_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `assetto-corsa-competizione_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/assetto-corsa-competizione/server.cfg` — Main server configuration
|
||||
- `~/assetto-corsa-competizione/config/` — Configuration directory
|
||||
- `~/assetto-corsa-competizione/logs/` — Log files directory
|
||||
- `~/assetto-corsa-competizione/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Assetto Corsa Competizione
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Assetto Corsa — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./assetto-corsa_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `assetto-corsa_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/assetto-corsa/server.cfg` — Main server configuration
|
||||
- `~/assetto-corsa/config/` — Configuration directory
|
||||
- `~/assetto-corsa/logs/` — Log files directory
|
||||
- `~/assetto-corsa/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Assetto Corsa
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Astroneer — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./astroneer_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `astroneer_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/astroneer/server.cfg` — Main server configuration
|
||||
- `~/astroneer/config/` — Configuration directory
|
||||
- `~/astroneer/logs/` — Log files directory
|
||||
- `~/astroneer/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Astroneer
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Atlas — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./atlas_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `atlas_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/atlas/server.cfg` — Main server configuration
|
||||
- `~/atlas/config/` — Configuration directory
|
||||
- `~/atlas/logs/` — Log files directory
|
||||
- `~/atlas/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Atlas
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Avorion — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./avorion_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `avorion_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/avorion/server.cfg` — Main server configuration
|
||||
- `~/avorion/config/` — Configuration directory
|
||||
- `~/avorion/logs/` — Log files directory
|
||||
- `~/avorion/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Avorion
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Ballistic Overkill — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./ballistic-overkill_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `ballistic-overkill_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/ballistic-overkill/server.cfg` — Main server configuration
|
||||
- `~/ballistic-overkill/config/` — Configuration directory
|
||||
- `~/ballistic-overkill/logs/` — Log files directory
|
||||
- `~/ballistic-overkill/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Ballistic Overkill
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Barotrauma — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./barotrauma_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `barotrauma_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/barotrauma/server.cfg` — Main server configuration
|
||||
- `~/barotrauma/config/` — Configuration directory
|
||||
- `~/barotrauma/logs/` — Log files directory
|
||||
- `~/barotrauma/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Barotrauma
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Base Defense — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./base-defense_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `base-defense_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/base-defense/server.cfg` — Main server configuration
|
||||
- `~/base-defense/config/` — Configuration directory
|
||||
- `~/base-defense/logs/` — Log files directory
|
||||
- `~/base-defense/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Base Defense
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# BATTALION: Legacy — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./battalion-legacy_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `battalion-legacy_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/battalion-legacy/server.cfg` — Main server configuration
|
||||
- `~/battalion-legacy/config/` — Configuration directory
|
||||
- `~/battalion-legacy/logs/` — Log files directory
|
||||
- `~/battalion-legacy/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for BATTALION: Legacy
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Battlefield 1942 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./battlefield-1942_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `battlefield-1942_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/battlefield-1942/server.cfg` — Main server configuration
|
||||
- `~/battlefield-1942/config/` — Configuration directory
|
||||
- `~/battlefield-1942/logs/` — Log files directory
|
||||
- `~/battlefield-1942/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Battlefield 1942
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Battlefield 3 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./battlefield-3_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `battlefield-3_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/battlefield-3/server.cfg` — Main server configuration
|
||||
- `~/battlefield-3/config/` — Configuration directory
|
||||
- `~/battlefield-3/logs/` — Log files directory
|
||||
- `~/battlefield-3/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Battlefield 3
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Battlefield 4 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./battlefield-4_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `battlefield-4_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/battlefield-4/server.cfg` — Main server configuration
|
||||
- `~/battlefield-4/config/` — Configuration directory
|
||||
- `~/battlefield-4/logs/` — Log files directory
|
||||
- `~/battlefield-4/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Battlefield 4
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Battlefield: Vietnam — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./battlefield-vietnam_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `battlefield-vietnam_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/battlefield-vietnam/server.cfg` — Main server configuration
|
||||
- `~/battlefield-vietnam/config/` — Configuration directory
|
||||
- `~/battlefield-vietnam/logs/` — Log files directory
|
||||
- `~/battlefield-vietnam/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Battlefield: Vietnam
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Black Mesa: Deathmatch — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./black-mesa-deathmatch_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `black-mesa-deathmatch_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/black-mesa-deathmatch/server.cfg` — Main server configuration
|
||||
- `~/black-mesa-deathmatch/config/` — Configuration directory
|
||||
- `~/black-mesa-deathmatch/logs/` — Log files directory
|
||||
- `~/black-mesa-deathmatch/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Black Mesa: Deathmatch
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Blade Symphony — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./blade-symphony_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `blade-symphony_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/blade-symphony/server.cfg` — Main server configuration
|
||||
- `~/blade-symphony/config/` — Configuration directory
|
||||
- `~/blade-symphony/logs/` — Log files directory
|
||||
- `~/blade-symphony/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Blade Symphony
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# BrainBread 2 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./brainbread-2_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `brainbread-2_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/brainbread-2/server.cfg` — Main server configuration
|
||||
- `~/brainbread-2/config/` — Configuration directory
|
||||
- `~/brainbread-2/logs/` — Log files directory
|
||||
- `~/brainbread-2/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for BrainBread 2
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Brainbread — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./brainbread_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `brainbread_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/brainbread/server.cfg` — Main server configuration
|
||||
- `~/brainbread/config/` — Configuration directory
|
||||
- `~/brainbread/logs/` — Log files directory
|
||||
- `~/brainbread/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Brainbread
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Call of Duty 2 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./call-of-duty-2_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `call-of-duty-2_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/call-of-duty-2/server.cfg` — Main server configuration
|
||||
- `~/call-of-duty-2/config/` — Configuration directory
|
||||
- `~/call-of-duty-2/logs/` — Log files directory
|
||||
- `~/call-of-duty-2/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Call of Duty 2
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Call of Duty 4 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./call-of-duty-4_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `call-of-duty-4_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/call-of-duty-4/server.cfg` — Main server configuration
|
||||
- `~/call-of-duty-4/config/` — Configuration directory
|
||||
- `~/call-of-duty-4/logs/` — Log files directory
|
||||
- `~/call-of-duty-4/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Call of Duty 4
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Call of Duty: United Offensive — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./call-of-duty-united-offensive_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `call-of-duty-united-offensive_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/call-of-duty-united-offensive/server.cfg` — Main server configuration
|
||||
- `~/call-of-duty-united-offensive/config/` — Configuration directory
|
||||
- `~/call-of-duty-united-offensive/logs/` — Log files directory
|
||||
- `~/call-of-duty-united-offensive/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Call of Duty: United Offensive
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Call of Duty: World at War — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./call-of-duty-world-at-war_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `call-of-duty-world-at-war_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/call-of-duty-world-at-war/server.cfg` — Main server configuration
|
||||
- `~/call-of-duty-world-at-war/config/` — Configuration directory
|
||||
- `~/call-of-duty-world-at-war/logs/` — Log files directory
|
||||
- `~/call-of-duty-world-at-war/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Call of Duty: World at War
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Call of Duty — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./call-of-duty_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `call-of-duty_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/call-of-duty/server.cfg` — Main server configuration
|
||||
- `~/call-of-duty/config/` — Configuration directory
|
||||
- `~/call-of-duty/logs/` — Log files directory
|
||||
- `~/call-of-duty/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Call of Duty
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Chivalry: Medieval Warfare — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./chivalry-medieval-warfare_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `chivalry-medieval-warfare_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/chivalry-medieval-warfare/server.cfg` — Main server configuration
|
||||
- `~/chivalry-medieval-warfare/config/` — Configuration directory
|
||||
- `~/chivalry-medieval-warfare/logs/` — Log files directory
|
||||
- `~/chivalry-medieval-warfare/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Chivalry: Medieval Warfare
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Citadel - Forged with fire — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./citadel-forged-with-fire_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `citadel-forged-with-fire_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/citadel-forged-with-fire/server.cfg` — Main server configuration
|
||||
- `~/citadel-forged-with-fire/config/` — Configuration directory
|
||||
- `~/citadel-forged-with-fire/logs/` — Log files directory
|
||||
- `~/citadel-forged-with-fire/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Citadel - Forged with fire
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Codename CURE — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./codename-cure_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `codename-cure_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/codename-cure/server.cfg` — Main server configuration
|
||||
- `~/codename-cure/config/` — Configuration directory
|
||||
- `~/codename-cure/logs/` — Log files directory
|
||||
- `~/codename-cure/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Codename CURE
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Colony Survival — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./colony-survival_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `colony-survival_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/colony-survival/server.cfg` — Main server configuration
|
||||
- `~/colony-survival/config/` — Configuration directory
|
||||
- `~/colony-survival/logs/` — Log files directory
|
||||
- `~/colony-survival/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Colony Survival
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Conan Exiles — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
ConanSandboxServer.exe -log -Port=7777 -QueryPort=27015 -MaxPlayers=40
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-log` — Enable logging.
|
||||
- `-Port=<port>` — Game port. Default: 7777.
|
||||
- `-QueryPort=<port>` — Query port. Default: 27015.
|
||||
- `-MaxPlayers=<num>` — Maximum players (1-40).
|
||||
- `-ServerName="<name>"` — Server name.
|
||||
- `-ServerPassword="<pass>"` — Server password.
|
||||
- `-AdminPassword="<pass>"` — Admin password.
|
||||
- `-RconEnabled=<True|False>` — Enable RCON.
|
||||
- `-RconPort=<port>` — RCON port.
|
||||
- `-RconPassword="<pass>"` — RCON password.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **7777** (primary)
|
||||
- Query: UDP **27015** (Steam query)
|
||||
- RCON: TCP **25575** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `WindowsServer/Conan Exiles/Saved/Config/WindowsServer/` — Configuration directory
|
||||
- `WindowsServer/Conan Exiles/Saved/Logs/` — Log files
|
||||
- `WindowsServer/Conan Exiles/Saved/SaveGames/` — Save files
|
||||
|
||||
**Linux:**
|
||||
- `/home/conan-exiles/Saved/Config/LinuxServer/` — Configuration directory
|
||||
- `/home/conan-exiles/Saved/Logs/` — Log files
|
||||
- `/home/conan-exiles/Saved/SaveGames/` — Save files
|
||||
|
||||
**Key Files:**
|
||||
- **GameUserSettings.ini**: Main server configuration
|
||||
- **Game.ini**: Advanced game settings
|
||||
- **Engine.ini**: Engine-specific settings
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Conan Exiles
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Core Keeper — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./core-keeper_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `core-keeper_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/core-keeper/server.cfg` — Main server configuration
|
||||
- `~/core-keeper/config/` — Configuration directory
|
||||
- `~/core-keeper/logs/` — Log files directory
|
||||
- `~/core-keeper/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Core Keeper
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,78 +0,0 @@
|
|||
# Counter-Strike 1.6 (HLDS) — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
hlds_run -game cstrike -port 27015 +map de_dust2 +maxplayers 16 +sv_lan 0 +sv_region 255 +log on +exec server.cfg -pingboost 3 -sys_ticrate 1000 -secure
|
||||
|
||||
**Parameters (HLDS)**
|
||||
- `-game cstrike` — game dir.
|
||||
- `-port=<P>` — game/query on UDP P (default 27015).
|
||||
- `+map`, `+maxplayers`, `+sv_lan`, `+sv_region`, `+rcon_password`, `+sv_password`.
|
||||
- `-sys_ticrate <n>` — server FPS cap (Linux).
|
||||
- `-pingboost {1|2|3}` — scheduling tweak (Linux).
|
||||
- `-secure` — VAC on.
|
||||
- `-noipx`, `-insecure` (testing only), `-norestart`, `-debug`.
|
||||
- Logs: `+log on`, `-condebug`.
|
||||
- Auto-update (SteamCMD wrapper): `-steam_dir`, `-steamcmd_script`.
|
||||
|
||||
**Ports**
|
||||
- Game/Query: UDP **P** (default 27015)
|
||||
- RCON: TCP on same P
|
||||
- HLTV (if used): UDP **27020**
|
||||
|
||||
## Config Files & Locations
|
||||
- `cstrike/server.cfg` — core cvars (rates, friendlyfire, mp_*, etc.)
|
||||
- `cstrike/mapcycle.txt`, `cstrike/motd.txt`, `cstrike/banned.cfg`
|
||||
- Logs: `cstrike/logs/`
|
||||
|
||||
## Steam Workshop
|
||||
Not applicable (pre-Workshop). Use legacy map packs in `cstrike/maps/`.
|
||||
|
||||
## Common Mods
|
||||
- **AMX Mod X (admin & plugins)**
|
||||
- **Install:**
|
||||
- Place AMXX files under `cstrike/addons/amxmodx/`
|
||||
- Ensure `metamod` is installed: `cstrike/addons/metamod/dlls/metamod_i386.so` (Linux) or `.dll` (Windows)
|
||||
- Edit `cstrike/liblist.gam` to point to Metamod:
|
||||
- Replace `gamedll` with `gamedll "addons/metamod/dlls/metamod.dll"` (Windows) or `gamedll_linux "addons/metamod/dlls/metamod_i386.so"`
|
||||
- Add AMXX to Metamod: `cstrike/addons/metamod/plugins.ini`:
|
||||
- `win32 addons/amxmodx/dlls/amxmodx_mm.dll`
|
||||
- `linux addons/amxmodx/dlls/amxmodx_mm_i386.so`
|
||||
- **Configure:**
|
||||
- Admins: `cstrike/addons/amxmodx/configs/users.ini`
|
||||
- Plugins: `cstrike/addons/amxmodx/configs/plugins.ini`
|
||||
- Modules: `cstrike/addons/amxmodx/configs/modules.ini`
|
||||
- **Database (optional for SQLX):**
|
||||
- `cstrike/addons/amxmodx/configs/sql.cfg` — MySQL host/db/user/pass and table prefixes.
|
||||
|
||||
## Database
|
||||
- **Optional** for AMXX plugins (Bans, StatsX SQL, etc.) via MySQL. Configure `sql.cfg`.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- AMX Mod X admin commands and plugin system
|
||||
- In-game admin commands via AMXX
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting
|
||||
- **“Bad load” for AMXX:** wrong Metamod path or architecture; check `meta list` in server console.
|
||||
- **Players kicked for “Consistency”:** `sv_consistency` and custom models/sounds; adjust whitelist or remove conflicting files.
|
||||
- **High choke/lag:** tune `sv_maxrate`, `sv_minrate`, `sv_maxupdaterate`; ensure sufficient upstream bandwidth; avoid outrageous `sys_ticrate`.
|
||||
|
|
@ -1,151 +0,0 @@
|
|||
# Counter-Strike 2 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
cs2 -dedicated +map de_dust2 +maxplayers 10 +sv_setsteamaccount YOUR_GSLT +game_type 0 +game_mode 1
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-dedicated` — Run as dedicated server.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (2-64).
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token. Required for public servers.
|
||||
- `+game_type <num>` — Game type (0=Classic Casual, 1=Classic Competitive).
|
||||
- `+game_mode <num>` — Game mode (0=Casual, 1=Competitive, 2=Wingman, 3=Arms Race, 4=Demolition).
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_password <pass>` — Server password.
|
||||
- `+rcon_password <pass>` — RCON password.
|
||||
- `-port <port>` — Server port. Default: 27015.
|
||||
- `-ip <address>` — Bind IP address.
|
||||
- `+sv_lan <0|1>` — LAN mode.
|
||||
- `+exec <file>` — Execute config file.
|
||||
- `-usercon` — Enable user console.
|
||||
- `-console` — Enable console output.
|
||||
- `+sv_region <num>` — Server region.
|
||||
- `+sv_cheats <0|1>` — Enable cheats (for practice).
|
||||
- `+mp_autokick <0|1>` — Auto-kick idle players.
|
||||
- `+mp_autoteambalance <0|1>` — Auto team balance.
|
||||
- `+sv_logfile <0|1>` — Enable logging.
|
||||
- `-tickrate <rate>` — Server tickrate (64 or 128).
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
- GOTV: UDP **27020** (game port + 5)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Counter-Strike 2/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Counter-Strike 2/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Counter-Strike 2/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Counter-Strike 2/motd.txt` — Message of the day
|
||||
- `steamapps/common/Counter-Strike 2/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Counter-Strike 2/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Counter-Strike 2/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Counter-Strike 2/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
**Collection Mounting:**
|
||||
1. Create Steam Workshop collection with desired maps/content
|
||||
2. Add collection ID to server startup: `+host_workshop_collection <collection_id>`
|
||||
3. Add Steam Web API key: `+sv_setsteamaccount <game_server_token>`
|
||||
|
||||
**Map Starting:**
|
||||
- Use workshop map IDs: `+map workshop/<map_id>`
|
||||
- Example: `+map workshop/125438255`
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/<app_id>/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/<app_id>/`
|
||||
|
||||
**API Key Setup:**
|
||||
1. Get Game Server Login Token from: https://steamcommunity.com/dev/managegameservers
|
||||
2. Add to startup parameters: `+sv_setsteamaccount <token>`
|
||||
|
||||
**Workshop Content Updates:**
|
||||
- Content updates automatically when server restarts
|
||||
- Force update with `workshop_download_item <app_id> <item_id>` console command
|
||||
|
||||
## Common Mods (curated)
|
||||
- **SourceMod (CS:GO Legacy)**
|
||||
- **Purpose**: Admin framework for CS:GO servers.
|
||||
- **Install**: Download SourceMod for CS:GO, requires MetaMod:Source.
|
||||
- **Configure**: Admin configuration in `addons/sourcemod/configs/`.
|
||||
|
||||
- **CS2 Server Manager (CS2)**
|
||||
- **Purpose**: Modern admin framework for Counter-Strike 2.
|
||||
- **Install**: Follow CS2-specific installation guides.
|
||||
- **Configure**: Configuration varies by chosen admin system.
|
||||
|
||||
- **Practice Mode Plugins**
|
||||
- **Purpose**: Enable practice configurations for competitive training.
|
||||
- **Install**: Various practice plugins available for both CS:GO and CS2.
|
||||
- **Configure**: Practice commands and features configuration.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Server not appearing in browser"**
|
||||
- **Cause**: Missing Game Server Login Token or firewall blocking ports
|
||||
- **Fix**: Add `+sv_setsteamaccount <token>` to startup, verify ports 27015 UDP/TCP are open
|
||||
|
||||
**"VAC Unable to verify"**
|
||||
- **Cause**: Modified game files or outdated server binaries
|
||||
- **Fix**: Verify server files integrity via SteamCMD, remove custom plugins temporarily
|
||||
|
||||
**"Map change crashes server"**
|
||||
- **Cause**: Invalid map file or insufficient memory
|
||||
- **Fix**: Verify map file integrity, increase server memory allocation, check map compatibility
|
||||
|
||||
**"High CPU usage/lag"**
|
||||
- **Cause**: Incorrect tickrate settings or too many plugins
|
||||
- **Fix**: Adjust `-tickrate` parameter, disable unnecessary plugins, optimize server.cfg rates
|
||||
|
||||
**"RCON not working"**
|
||||
- **Cause**: Incorrect password or blocked TCP port
|
||||
- **Fix**: Verify `rcon_password` setting, ensure TCP port (same as game port) is accessible
|
||||
|
||||
**"Players getting kicked for 'Authentication timeout'"**
|
||||
- **Cause**: Steam authentication issues or network problems
|
||||
- **Fix**: Check internet connectivity, verify Steam services status, adjust timeout settings
|
||||
|
|
@ -1,131 +0,0 @@
|
|||
# Counter-Strike: Condition Zero — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
hlds_run -game cstrike -port 27015 +map de_dust2 +maxplayers 16 +sv_lan 0 -pingboost 3 -sys_ticrate 1000
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory (cstrike, valve, etc.).
|
||||
- `-port <port>` — Server port. Default: 27015.
|
||||
- `+map <mapname>` — Starting map.
|
||||
- `+maxplayers <num>` — Maximum players (1-32).
|
||||
- `+sv_lan <0|1>` — LAN mode.
|
||||
- `+rcon_password <pass>` — RCON password.
|
||||
- `+sv_password <pass>` — Server password.
|
||||
- `+hostname <name>` — Server name.
|
||||
- `+exec <file>` — Execute config file.
|
||||
- `-pingboost <1|2|3>` — Performance optimization (Linux).
|
||||
- `-sys_ticrate <rate>` — Server FPS (Linux, default: 100).
|
||||
- `-secure` — Enable VAC.
|
||||
- `-insecure` — Disable VAC.
|
||||
- `-noipx` — Disable IPX networking.
|
||||
- `-norestart` — Don't restart on crash.
|
||||
- `+log <on|off>` — Enable logging.
|
||||
- `-condebug` — Console debug logging.
|
||||
- `+sv_region <num>` — Server region.
|
||||
- `-zone <bytes>` — Memory allocation.
|
||||
- `-heapsize <kb>` — Heap size in kilobytes.
|
||||
|
||||
**Ports**
|
||||
- Game/Query: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- HLTV: UDP **27020** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `game_dir/server.cfg` — Main server configuration
|
||||
- `game_dir/mapcycle.txt` — Map rotation list
|
||||
- `game_dir/motd.txt` — Message of the day
|
||||
- `game_dir/banned.cfg` — Banned users list
|
||||
- `game_dir/listip.cfg` — Banned IP addresses
|
||||
- `game_dir/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/counter-strike-condition-zero/server.cfg` — Main server configuration
|
||||
- `~/counter-strike-condition-zero/mapcycle.txt` — Map rotation list
|
||||
- `~/counter-strike-condition-zero/motd.txt` — Message of the day
|
||||
- `~/counter-strike-condition-zero/banned.cfg` — Banned users list
|
||||
- `~/counter-strike-condition-zero/logs/` — Server logs directory
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings (rates, friendly fire, admin commands)
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message for connecting players
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **AMX Mod X**
|
||||
- **Purpose**: Complete admin and scripting framework for GoldSrc games.
|
||||
- **Install**: Download from amxmodx.org, extract to game directory, add `meta load addons/amxmodx/dlls/amxmodx_mm` to `addons/metamod/plugins.ini`.
|
||||
- **Configure**: Edit `addons/amxmodx/configs/amxx.cfg` for basic settings, `configs/users.ini` for admin users.
|
||||
|
||||
- **Metamod**
|
||||
- **Purpose**: Plugin loading framework required by most mods.
|
||||
- **Install**: Extract metamod.dll to `addons/metamod/dlls/`, add `gamedll_linux "addons/metamod/dlls/metamod.so"` to liblist.gam.
|
||||
- **Configure**: Plugins list in `addons/metamod/plugins.ini`.
|
||||
|
||||
- **StatsMe**
|
||||
- **Purpose**: Player statistics tracking and ranking system.
|
||||
- **Install**: Requires AMX Mod X, install plugin files to `addons/amxmodx/plugins/`.
|
||||
- **Configure**: Database settings in plugin configuration files.
|
||||
|
||||
- **PodBot MM**
|
||||
- **Purpose**: AI bots for offline practice or filling servers.
|
||||
- **Install**: Extract to game directory, requires Metamod.
|
||||
- **Configure**: Bot skills and behavior in `podbot/podbot.cfg`.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Server not appearing in browser"**
|
||||
- **Cause**: Missing Game Server Login Token or firewall blocking ports
|
||||
- **Fix**: Add `+sv_setsteamaccount <token>` to startup, verify ports 27015 UDP/TCP are open
|
||||
|
||||
**"VAC Unable to verify"**
|
||||
- **Cause**: Modified game files or outdated server binaries
|
||||
- **Fix**: Verify server files integrity via SteamCMD, remove custom plugins temporarily
|
||||
|
||||
**"Map change crashes server"**
|
||||
- **Cause**: Invalid map file or insufficient memory
|
||||
- **Fix**: Verify map file integrity, increase server memory allocation, check map compatibility
|
||||
|
||||
**"High CPU usage/lag"**
|
||||
- **Cause**: Incorrect tickrate settings or too many plugins
|
||||
- **Fix**: Adjust `-tickrate` parameter, disable unnecessary plugins, optimize server.cfg rates
|
||||
|
||||
**"RCON not working"**
|
||||
- **Cause**: Incorrect password or blocked TCP port
|
||||
- **Fix**: Verify `rcon_password` setting, ensure TCP port (same as game port) is accessible
|
||||
|
||||
**"Players getting kicked for 'Authentication timeout'"**
|
||||
- **Cause**: Steam authentication issues or network problems
|
||||
- **Fix**: Check internet connectivity, verify Steam services status, adjust timeout settings
|
||||
|
|
@ -1,163 +0,0 @@
|
|||
# Counter-Strike: Global Offensive — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game cstrike -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/motd.txt` — Message of the day
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Counter-Strike: Global Offensive/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Global Offensive/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
**Collection Mounting:**
|
||||
1. Create Steam Workshop collection with desired maps/content
|
||||
2. Add collection ID to server startup: `+host_workshop_collection <collection_id>`
|
||||
3. Add Steam Web API key: `+sv_setsteamaccount <game_server_token>`
|
||||
|
||||
**Map Starting:**
|
||||
- Use workshop map IDs: `+map workshop/<map_id>`
|
||||
- Example: `+map workshop/125438255`
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/<app_id>/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/<app_id>/`
|
||||
|
||||
**API Key Setup:**
|
||||
1. Get Game Server Login Token from: https://steamcommunity.com/dev/managegameservers
|
||||
2. Add to startup parameters: `+sv_setsteamaccount <token>`
|
||||
|
||||
**Workshop Content Updates:**
|
||||
- Content updates automatically when server restarts
|
||||
- Force update with `workshop_download_item <app_id> <item_id>` console command
|
||||
|
||||
## Common Mods (curated)
|
||||
- **AMX Mod X**
|
||||
- **Purpose**: Complete admin and scripting framework for GoldSrc games.
|
||||
- **Install**: Download from amxmodx.org, extract to game directory, add `meta load addons/amxmodx/dlls/amxmodx_mm` to `addons/metamod/plugins.ini`.
|
||||
- **Configure**: Edit `addons/amxmodx/configs/amxx.cfg` for basic settings, `configs/users.ini` for admin users.
|
||||
|
||||
- **Metamod**
|
||||
- **Purpose**: Plugin loading framework required by most mods.
|
||||
- **Install**: Extract metamod.dll to `addons/metamod/dlls/`, add `gamedll_linux "addons/metamod/dlls/metamod.so"` to liblist.gam.
|
||||
- **Configure**: Plugins list in `addons/metamod/plugins.ini`.
|
||||
|
||||
- **StatsMe**
|
||||
- **Purpose**: Player statistics tracking and ranking system.
|
||||
- **Install**: Requires AMX Mod X, install plugin files to `addons/amxmodx/plugins/`.
|
||||
- **Configure**: Database settings in plugin configuration files.
|
||||
|
||||
- **PodBot MM**
|
||||
- **Purpose**: AI bots for offline practice or filling servers.
|
||||
- **Install**: Extract to game directory, requires Metamod.
|
||||
- **Configure**: Bot skills and behavior in `podbot/podbot.cfg`.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Server not appearing in browser"**
|
||||
- **Cause**: Missing Game Server Login Token or firewall blocking ports
|
||||
- **Fix**: Add `+sv_setsteamaccount <token>` to startup, verify ports 27015 UDP/TCP are open
|
||||
|
||||
**"VAC Unable to verify"**
|
||||
- **Cause**: Modified game files or outdated server binaries
|
||||
- **Fix**: Verify server files integrity via SteamCMD, remove custom plugins temporarily
|
||||
|
||||
**"Map change crashes server"**
|
||||
- **Cause**: Invalid map file or insufficient memory
|
||||
- **Fix**: Verify map file integrity, increase server memory allocation, check map compatibility
|
||||
|
||||
**"High CPU usage/lag"**
|
||||
- **Cause**: Incorrect tickrate settings or too many plugins
|
||||
- **Fix**: Adjust `-tickrate` parameter, disable unnecessary plugins, optimize server.cfg rates
|
||||
|
||||
**"RCON not working"**
|
||||
- **Cause**: Incorrect password or blocked TCP port
|
||||
- **Fix**: Verify `rcon_password` setting, ensure TCP port (same as game port) is accessible
|
||||
|
||||
**"Players getting kicked for 'Authentication timeout'"**
|
||||
- **Cause**: Steam authentication issues or network problems
|
||||
- **Fix**: Check internet connectivity, verify Steam services status, adjust timeout settings
|
||||
|
|
@ -1,139 +0,0 @@
|
|||
# Counter-Strike: Source — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game cstrike -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Counter-Strike: Source/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Counter-Strike: Source/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Counter-Strike: Source/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Counter-Strike: Source/motd.txt` — Message of the day
|
||||
- `steamapps/common/Counter-Strike: Source/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Counter-Strike: Source/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Counter-Strike: Source/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Counter-Strike: Source/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **SourceMod**
|
||||
- **Purpose**: Admin and scripting framework for Source engine games.
|
||||
- **Install**: Download from sourcemod.net, extract to game directory, requires MetaMod:Source.
|
||||
- **Configure**: Edit `addons/sourcemod/configs/admins_simple.ini` for admin users.
|
||||
|
||||
- **MetaMod:Source**
|
||||
- **Purpose**: Plugin loading framework for Source engine.
|
||||
- **Install**: Extract to game directory, add to gameinfo.txt.
|
||||
- **Configure**: Plugin loading handled automatically.
|
||||
|
||||
- **Mani Admin Plugin**
|
||||
- **Purpose**: Alternative admin framework with extensive features.
|
||||
- **Install**: Extract to game directory, configure via mani_server.cfg.
|
||||
- **Configure**: Admin settings in `cfg/mani_server.cfg`.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Server not appearing in browser"**
|
||||
- **Cause**: Missing Game Server Login Token or firewall blocking ports
|
||||
- **Fix**: Add `+sv_setsteamaccount <token>` to startup, verify ports 27015 UDP/TCP are open
|
||||
|
||||
**"VAC Unable to verify"**
|
||||
- **Cause**: Modified game files or outdated server binaries
|
||||
- **Fix**: Verify server files integrity via SteamCMD, remove custom plugins temporarily
|
||||
|
||||
**"Map change crashes server"**
|
||||
- **Cause**: Invalid map file or insufficient memory
|
||||
- **Fix**: Verify map file integrity, increase server memory allocation, check map compatibility
|
||||
|
||||
**"High CPU usage/lag"**
|
||||
- **Cause**: Incorrect tickrate settings or too many plugins
|
||||
- **Fix**: Adjust `-tickrate` parameter, disable unnecessary plugins, optimize server.cfg rates
|
||||
|
||||
**"RCON not working"**
|
||||
- **Cause**: Incorrect password or blocked TCP port
|
||||
- **Fix**: Verify `rcon_password` setting, ensure TCP port (same as game port) is accessible
|
||||
|
||||
**"Players getting kicked for 'Authentication timeout'"**
|
||||
- **Cause**: Steam authentication issues or network problems
|
||||
- **Fix**: Check internet connectivity, verify Steam services status, adjust timeout settings
|
||||
|
|
@ -1,144 +0,0 @@
|
|||
# Counter-Strike — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game cstrike -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Counter-Strike/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Counter-Strike/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Counter-Strike/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Counter-Strike/motd.txt` — Message of the day
|
||||
- `steamapps/common/Counter-Strike/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Counter-Strike/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Counter-Strike/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Counter-Strike/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Counter-Strike/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Counter-Strike/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Counter-Strike/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Counter-Strike/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Counter-Strike/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Counter-Strike/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **AMX Mod X**
|
||||
- **Purpose**: Complete admin and scripting framework for GoldSrc games.
|
||||
- **Install**: Download from amxmodx.org, extract to game directory, add `meta load addons/amxmodx/dlls/amxmodx_mm` to `addons/metamod/plugins.ini`.
|
||||
- **Configure**: Edit `addons/amxmodx/configs/amxx.cfg` for basic settings, `configs/users.ini` for admin users.
|
||||
|
||||
- **Metamod**
|
||||
- **Purpose**: Plugin loading framework required by most mods.
|
||||
- **Install**: Extract metamod.dll to `addons/metamod/dlls/`, add `gamedll_linux "addons/metamod/dlls/metamod.so"` to liblist.gam.
|
||||
- **Configure**: Plugins list in `addons/metamod/plugins.ini`.
|
||||
|
||||
- **StatsMe**
|
||||
- **Purpose**: Player statistics tracking and ranking system.
|
||||
- **Install**: Requires AMX Mod X, install plugin files to `addons/amxmodx/plugins/`.
|
||||
- **Configure**: Database settings in plugin configuration files.
|
||||
|
||||
- **PodBot MM**
|
||||
- **Purpose**: AI bots for offline practice or filling servers.
|
||||
- **Install**: Extract to game directory, requires Metamod.
|
||||
- **Configure**: Bot skills and behavior in `podbot/podbot.cfg`.
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Server not appearing in browser"**
|
||||
- **Cause**: Missing Game Server Login Token or firewall blocking ports
|
||||
- **Fix**: Add `+sv_setsteamaccount <token>` to startup, verify ports 27015 UDP/TCP are open
|
||||
|
||||
**"VAC Unable to verify"**
|
||||
- **Cause**: Modified game files or outdated server binaries
|
||||
- **Fix**: Verify server files integrity via SteamCMD, remove custom plugins temporarily
|
||||
|
||||
**"Map change crashes server"**
|
||||
- **Cause**: Invalid map file or insufficient memory
|
||||
- **Fix**: Verify map file integrity, increase server memory allocation, check map compatibility
|
||||
|
||||
**"High CPU usage/lag"**
|
||||
- **Cause**: Incorrect tickrate settings or too many plugins
|
||||
- **Fix**: Adjust `-tickrate` parameter, disable unnecessary plugins, optimize server.cfg rates
|
||||
|
||||
**"RCON not working"**
|
||||
- **Cause**: Incorrect password or blocked TCP port
|
||||
- **Fix**: Verify `rcon_password` setting, ensure TCP port (same as game port) is accessible
|
||||
|
||||
**"Players getting kicked for 'Authentication timeout'"**
|
||||
- **Cause**: Steam authentication issues or network problems
|
||||
- **Fix**: Check internet connectivity, verify Steam services status, adjust timeout settings
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Craftopia — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./craftopia_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `craftopia_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/craftopia/server.cfg` — Main server configuration
|
||||
- `~/craftopia/config/` — Configuration directory
|
||||
- `~/craftopia/logs/` — Log files directory
|
||||
- `~/craftopia/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Craftopia
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# CryoFall — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./cryofall_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `cryofall_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/cryofall/server.cfg` — Main server configuration
|
||||
- `~/cryofall/config/` — Configuration directory
|
||||
- `~/cryofall/logs/` — Log files directory
|
||||
- `~/cryofall/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for CryoFall
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,135 +0,0 @@
|
|||
# Day of Defeat: Source — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game dod -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Day of Defeat: Source/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Day of Defeat: Source/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Day of Defeat: Source/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Day of Defeat: Source/motd.txt` — Message of the day
|
||||
- `steamapps/common/Day of Defeat: Source/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Day of Defeat: Source/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Day of Defeat: Source/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Day of Defeat: Source/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Day of Defeat: Source
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Day of Defeat — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./day-of-defeat_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `day-of-defeat_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/day-of-defeat/server.cfg` — Main server configuration
|
||||
- `~/day-of-defeat/config/` — Configuration directory
|
||||
- `~/day-of-defeat/logs/` — Log files directory
|
||||
- `~/day-of-defeat/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Day of Defeat
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Day of Dragons — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./day-of-dragons_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `day-of-dragons_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/day-of-dragons/server.cfg` — Main server configuration
|
||||
- `~/day-of-dragons/config/` — Configuration directory
|
||||
- `~/day-of-dragons/logs/` — Log files directory
|
||||
- `~/day-of-dragons/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Day of Dragons
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Day of Infamy — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./day-of-infamy_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `day-of-infamy_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/day-of-infamy/server.cfg` — Main server configuration
|
||||
- `~/day-of-infamy/config/` — Configuration directory
|
||||
- `~/day-of-infamy/logs/` — Log files directory
|
||||
- `~/day-of-infamy/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Day of Infamy
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,143 +0,0 @@
|
|||
# DayZ Mod (Arma 2 OA) — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
arma2oaserver.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=ServerProfile -mod=@mod1;@mod2
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-config=<file>` — Server config file (server.cfg).
|
||||
- `-cfg=<file>` — Basic config file (basic.cfg).
|
||||
- `-profiles=<dir>` — Profile directory.
|
||||
- `-mod=<mods>` — Mod folders (semicolon separated).
|
||||
- `-serverMod=<mods>` — Server-side only mods.
|
||||
- `-name=<profilename>` — Server profile name.
|
||||
- `-world=<worldname>` — Empty world name.
|
||||
- `-noSound` — Disable sound processing.
|
||||
- `-nosplash` — Skip intro videos.
|
||||
- `-noPause` — Don't pause when not focused.
|
||||
- `-cpuCount=<num>` — CPU core count override.
|
||||
- `-maxMem=<mb>` — Maximum memory usage.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Query: UDP **2303** (game port + 1)
|
||||
- BattlEye: UDP **2344** (if enabled)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **DayZ Epoch**
|
||||
- **Purpose**: Enhanced DayZ experience with base building and vehicles.
|
||||
- **Install**: Download server and client files, place in `@DayZ_Epoch` folder.
|
||||
- **Configure**: Database setup and server configuration in `@hive` folder.
|
||||
|
||||
- **DayZ Overwatch**
|
||||
- **Purpose**: Military-focused DayZ variant with additional weapons.
|
||||
- **Install**: Download mod files, combine with Epoch for Overpoch.
|
||||
- **Configure**: Mission file configuration for weapon spawns.
|
||||
|
||||
- **infiSTAR**
|
||||
- **Purpose**: Advanced anti-hack and admin tools.
|
||||
- **Install**: Purchase and download, server-side installation only.
|
||||
- **Configure**: Admin IDs and settings in infiSTAR configuration files.
|
||||
|
||||
## Database
|
||||
**Engine**: MySQL (required for character persistence)
|
||||
|
||||
**Configuration File**: `@hive/HiveExt.ini`
|
||||
```ini
|
||||
[Database]
|
||||
Type = mysql
|
||||
Host = localhost
|
||||
Port = 3306
|
||||
Database = dayz_epoch
|
||||
Username = dayz_user
|
||||
Password = your_password_here
|
||||
|
||||
[Characters]
|
||||
;Enables persistence
|
||||
LoadCharacter = true
|
||||
SaveCharacter = true
|
||||
```
|
||||
|
||||
**Database Setup**:
|
||||
1. Install MySQL server
|
||||
2. Create database: `CREATE DATABASE dayz_epoch;`
|
||||
3. Import schema from mod documentation
|
||||
4. Create user with appropriate permissions
|
||||
5. Test connection before starting server
|
||||
|
||||
**Backup Strategy**:
|
||||
- Daily automated backups of character and vehicle data
|
||||
- Retention of 7 daily backups
|
||||
- Test restore procedures regularly
|
||||
- Monitor database size and performance
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Waiting for host" infinite loop**
|
||||
- **Cause**: Database connection issues or incorrect mission file
|
||||
- **Fix**: Verify MySQL connection in HiveExt.ini, check mission PBO integrity, review server RPT logs
|
||||
|
||||
**"No message received" / Player disconnect**
|
||||
- **Cause**: Network timeout or BattlEye issues
|
||||
- **Fix**: Optimize basic.cfg network settings, update BattlEye filters, check server performance
|
||||
|
||||
**Database connection failed**
|
||||
- **Cause**: MySQL server down or incorrect credentials
|
||||
- **Fix**: Verify MySQL service running, check HiveExt.ini credentials, test database connectivity
|
||||
|
||||
**Script restriction kicks**
|
||||
- **Cause**: BattlEye script filters blocking legitimate commands
|
||||
- **Fix**: Update BattlEye filters from mod documentation, merge custom filter exceptions
|
||||
|
||||
**Character reset / Database issues**
|
||||
- **Cause**: Database corruption or incorrect instance configuration
|
||||
- **Fix**: Verify database integrity, check Instance ID matches between DB and config
|
||||
|
|
@ -1,90 +0,0 @@
|
|||
# DayZ Mod (Arma 2 OA) — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
arma2oaserver.exe -port=2302 -config=server.cfg -cfg=basic.cfg -profiles=profiles -name=server -world=empty -mod="@DayZ;@DayZ_Epoch" -serverMod="@DayZ_Server;@hive" -cpuCount=4 -exThreads=7 -nosplash -noPause -noSound -malloc=system -hugepages
|
||||
|
||||
**Parameters**
|
||||
- `-port=<P>` — Game UDP port. Default 2302.
|
||||
- `-config=server.cfg` — gameplay, passwords, mission rotation.
|
||||
- `-cfg=basic.cfg` — networking (MaxMsgSend, packet sizes), timestamps.
|
||||
- `-profiles=<dir>` — logs (`.RPT`), netlogs, dumps.
|
||||
- `-name=<profile>` — creates `<profile>.ArmA2OAProfile` (difficulty, view distance).
|
||||
- `-mod=` — client+server mods; load order matters.
|
||||
- `-serverMod=` — server-only mods (Hive/antihack).
|
||||
- `-cpuCount`, `-exThreads`, `-malloc`, `-hugepages`, `-world=empty`, `-noPause`, `-noSound`, `-nosplash`, `-logFile`, `-pid`, `-ranking`.
|
||||
- `-BEpath=<dir>` — BattlEye directory.
|
||||
|
||||
**Ports**
|
||||
- Game: **P** UDP (default 2302)
|
||||
- Query: **P+1** UDP
|
||||
- Steam master: **27016** UDP
|
||||
- BattlEye: **2344–2345** UDP, RCon TCP as per `BEServer.cfg`
|
||||
|
||||
## Config Files & Locations
|
||||
- Root:
|
||||
- `server.cfg` — hostname, verifySignatures, vote rules, MOTD, missions.
|
||||
- `basic.cfg` — bandwidth & network tuning.
|
||||
- Profiles (`-profiles`):
|
||||
- `<name>.ArmA2OAProfile` — difficulty profile.
|
||||
- `*.RPT` — main runtime log.
|
||||
- BattlEye (`Expansion/BattlEye` or `-BEpath`):
|
||||
- `BEServer.cfg` — `RConPassword`, `RConPort`.
|
||||
- `scripts.txt`, `remoteexec.txt` — filter lists.
|
||||
- Keys: `keys/*.bikey` (required when `verifySignatures=2`).
|
||||
- DayZ/Epoch server component:
|
||||
- `@DayZ_Server` / `@hive` with `HiveExt.dll`.
|
||||
- Mission PBO: `MPMissions/DayZ_Epoch_11.Chernarus.pbo` (example).
|
||||
|
||||
## Steam Workshop
|
||||
Not natively used for Arma 2 OA; install `@Mod` folders manually and copy `.bikey` to `keys/`.
|
||||
|
||||
## Common Mods
|
||||
- **DayZ Epoch**
|
||||
- **Install:** place `@DayZ_Epoch` and `@DayZ_Server` in root; add to `-mod` and `-serverMod`.
|
||||
- **Configure:** `@DayZ_Server\config.cfg` and `HiveExt.ini` (DB). Ensure server and client versions match.
|
||||
- **Overwatch / Overpoch**
|
||||
- Install `@DayZOverwatch`, adjust mission PBO to Overpoch variant.
|
||||
- Merge/add `.bikey` keys.
|
||||
- **Anti-hack/admin (e.g., infiSTAR)**
|
||||
- Server-side only in `-serverMod`; follow vendor config.
|
||||
|
||||
## Database
|
||||
- **MySQL** (port 3306). Connection is in `HiveExt.ini`:
|
||||
- `Host = <ip_or_dns>`
|
||||
- `Database = dayz`
|
||||
- `Username = dayzuser`
|
||||
- `Password = ********`
|
||||
- `Instance = 11` (matches mission instance)
|
||||
- Create schema using mod-provided SQL. Index cleanup & periodic maintenance recommended.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- BattlEye RCON for server management and player control
|
||||
- In-game admin tools via infiSTAR or similar anti-hack solutions
|
||||
- Database admin tools for character/vehicle management
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of MySQL database (character data, vehicles, bases)
|
||||
- Configuration file backups (server.cfg, basic.cfg, mission files)
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test database restore procedures regularly
|
||||
|
||||
**Auto-Update:**
|
||||
- Monitor mod releases for client/server version synchronization
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup database and configs before applying updates
|
||||
- Test mod compatibility before deploying to production
|
||||
|
||||
**Monitoring:**
|
||||
- Database performance monitoring (connection counts, query performance)
|
||||
- Server performance via .RPT logs and BattlEye reports
|
||||
- Player statistics and anti-cheat logging
|
||||
- Uptime and restart scheduling for stability
|
||||
|
||||
## Troubleshooting
|
||||
- **HiveExt.dll fails / DB won’t connect:** wrong creds or MySQL not reachable; VC++ redists missing.
|
||||
- **“Waiting for host” loop:** wrong `Instance` vs DB content; mission PBO mismatch; see `.RPT`.
|
||||
- **Script restriction kicks:** update/merge BE filters with mod’s recommended entries.
|
||||
- **Signature mismatch:** missing `.bikey` for a loaded mod; ensure `keys/` contains all and clients use same versions.
|
||||
- **Severe desync:** tune `basic.cfg` bandwidth settings; reduce AI/vehicles; lower player cap.
|
||||
|
|
@ -1,138 +0,0 @@
|
|||
# DayZ — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
DayZServer_x64.exe -config=serverDZ.cfg -port=2302 -profiles=ServerProfile -dologs -adminlog -netlog -freezecheck
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-config=<file>` — Server config file (serverDZ.cfg).
|
||||
- `-port=<port>` — Server port. Default: 2302.
|
||||
- `-profiles=<dir>` — Profile directory name.
|
||||
- `-dologs` — Enable logging.
|
||||
- `-adminlog` — Enable admin logging.
|
||||
- `-netlog` — Enable network logging.
|
||||
- `-freezecheck` — Enable freeze detection.
|
||||
- `-scriptDebug=<true|false>` — Enable script debugging.
|
||||
- `-filePatching` — Enable file patching (dev mode).
|
||||
- `-scrAllowFileWrite` — Allow script file writing.
|
||||
- `-limitFPS=<fps>` — Limit server FPS.
|
||||
- `-cpuCount=<num>` — CPU core count override.
|
||||
- `-maxMem=<mb>` — Maximum memory usage.
|
||||
- `-malloc=<system>` — Memory allocator (system, tbb4malloc_bi).
|
||||
- `-exThreads=<num>` — Extra threads count.
|
||||
- `-enableHT` — Enable hyperthreading.
|
||||
- `-hugepages` — Enable huge pages (Linux).
|
||||
- `-BEpath=<path>` — BattlEye path.
|
||||
- `-instanceId=<num>` — Server instance ID.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **2302** (primary)
|
||||
- Steam Query: UDP **27016** (fixed)
|
||||
- BattlEye: UDP **2344** (game port + 42)
|
||||
- VON: UDP **2303** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `server.cfg` — Main server configuration
|
||||
- `basic.cfg` — Basic networking and performance settings
|
||||
- `ServerProfile/` — Profile directory with logs and user data
|
||||
- `MPMissions/` — Mission files directory
|
||||
- `keys/` — Signature keys for mod verification
|
||||
|
||||
**Linux:**
|
||||
- `~/arma/server.cfg` — Main server configuration
|
||||
- `~/arma/basic.cfg` — Basic networking settings
|
||||
- `~/arma/ServerProfile/` — Profile directory
|
||||
- `~/arma/MPMissions/` — Mission files
|
||||
- `~/arma/keys/` — Signature keys
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Server name, password, mission rotation, admin settings
|
||||
- **basic.cfg**: Network bandwidth and performance tuning
|
||||
- **Profile logs**: Server performance and error logs
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
- **CF (Community Framework)**
|
||||
- **Purpose**: Modding framework required by many DayZ mods.
|
||||
- **Install**: Subscribe via Workshop, ensure loads first in mod order.
|
||||
- **Configure**: No direct configuration - provides API framework.
|
||||
|
||||
- **BuildAnywhere**
|
||||
- **Purpose**: Allows base building in normally restricted areas.
|
||||
- **Install**: Workshop subscription, add to server mods.
|
||||
- **Configure**: Settings in mod configuration files.
|
||||
|
||||
- **Trader**
|
||||
- **Purpose**: NPC traders and economy system.
|
||||
- **Install**: Download from modding sites, requires server restart.
|
||||
- **Configure**: Trader locations and items in mod config files.
|
||||
|
||||
- **DayZ Editor Loader**
|
||||
- **Purpose**: Custom spawns, buildings, and map modifications.
|
||||
- **Install**: Workshop or manual installation.
|
||||
- **Configure**: Map edits and spawn configurations in JSON files.
|
||||
|
||||
## Database
|
||||
**Engine**: SQLite
|
||||
|
||||
**Configuration**:
|
||||
- Database settings typically in main server configuration file
|
||||
- Connection parameters: host, port, database name, credentials
|
||||
- Enable persistence features in server configuration
|
||||
|
||||
**Setup**:
|
||||
1. Install database engine if required
|
||||
2. Create database and user with appropriate permissions
|
||||
3. Configure connection settings in server config
|
||||
4. Test connection before starting server
|
||||
5. Set up automated backups
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**"Authentication timeout" on connect**
|
||||
- **Cause**: Steam authentication server issues or network problems
|
||||
- **Fix**: Check Steam server status, verify internet connectivity, restart Steam services
|
||||
|
||||
**"Session lost" / Frequent disconnects**
|
||||
- **Cause**: Network instability or server performance issues
|
||||
- **Fix**: Optimize server performance, check network quality, adjust timeout settings
|
||||
|
||||
**Mods not loading / Version mismatch**
|
||||
- **Cause**: Client-server mod version differences or missing dependencies
|
||||
- **Fix**: Verify all mods updated, check mod dependencies, ensure Workshop sync
|
||||
|
||||
**Character stuck / Can't move**
|
||||
- **Cause**: Database synchronization issues or server lag
|
||||
- **Fix**: Character reset via admin tools, server restart, check database performance
|
||||
|
||||
**BattlEye initialization failed**
|
||||
- **Cause**: Missing BattlEye files or configuration issues
|
||||
- **Fix**: Verify BattlEye installation, check file permissions, update BattlEye client
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Dead Matter — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./dead-matter_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `dead-matter_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/dead-matter/server.cfg` — Main server configuration
|
||||
- `~/dead-matter/config/` — Configuration directory
|
||||
- `~/dead-matter/logs/` — Log files directory
|
||||
- `~/dead-matter/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Dead Matter
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Deadside (Console) — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./deadside-console_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `deadside-console_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/deadside-console/server.cfg` — Main server configuration
|
||||
- `~/deadside-console/config/` — Configuration directory
|
||||
- `~/deadside-console/logs/` — Log files directory
|
||||
- `~/deadside-console/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Deadside (Console)
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Deadside — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./deadside_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `deadside_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/deadside/server.cfg` — Main server configuration
|
||||
- `~/deadside/config/` — Configuration directory
|
||||
- `~/deadside/logs/` — Log files directory
|
||||
- `~/deadside/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Deadside
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Deathmatch Classic — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./deathmatch-classic_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `deathmatch-classic_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/deathmatch-classic/server.cfg` — Main server configuration
|
||||
- `~/deathmatch-classic/config/` — Configuration directory
|
||||
- `~/deathmatch-classic/logs/` — Log files directory
|
||||
- `~/deathmatch-classic/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Deathmatch Classic
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Don't Starve Together — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./don-t-starve-together_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `don-t-starve-together_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/don-t-starve-together/server.cfg` — Main server configuration
|
||||
- `~/don-t-starve-together/config/` — Configuration directory
|
||||
- `~/don-t-starve-together/logs/` — Log files directory
|
||||
- `~/don-t-starve-together/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Don't Starve Together
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Double Action: Boogaloo — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./double-action-boogaloo_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `double-action-boogaloo_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/double-action-boogaloo/server.cfg` — Main server configuration
|
||||
- `~/double-action-boogaloo/config/` — Configuration directory
|
||||
- `~/double-action-boogaloo/logs/` — Log files directory
|
||||
- `~/double-action-boogaloo/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Double Action: Boogaloo
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Dune: Awakening — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./dune-awakening_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `dune-awakening_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/dune-awakening/server.cfg` — Main server configuration
|
||||
- `~/dune-awakening/config/` — Configuration directory
|
||||
- `~/dune-awakening/logs/` — Log files directory
|
||||
- `~/dune-awakening/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Dune: Awakening
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Dystopia — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./dystopia_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `dystopia_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/dystopia/server.cfg` — Main server configuration
|
||||
- `~/dystopia/config/` — Configuration directory
|
||||
- `~/dystopia/logs/` — Log files directory
|
||||
- `~/dystopia/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Dystopia
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Eco — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./eco_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `eco_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/eco/server.cfg` — Main server configuration
|
||||
- `~/eco/config/` — Configuration directory
|
||||
- `~/eco/logs/` — Log files directory
|
||||
- `~/eco/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Eco
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Empires Mod — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./empires-mod_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `empires-mod_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/empires-mod/server.cfg` — Main server configuration
|
||||
- `~/empires-mod/config/` — Configuration directory
|
||||
- `~/empires-mod/logs/` — Log files directory
|
||||
- `~/empires-mod/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Empires Mod
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Empyrion: Galactic Survival — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./empyrion-galactic-survival_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `empyrion-galactic-survival_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/empyrion-galactic-survival/server.cfg` — Main server configuration
|
||||
- `~/empyrion-galactic-survival/config/` — Configuration directory
|
||||
- `~/empyrion-galactic-survival/logs/` — Log files directory
|
||||
- `~/empyrion-galactic-survival/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Empyrion: Galactic Survival
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Enshrouded — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./enshrouded_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `enshrouded_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/enshrouded/server.cfg` — Main server configuration
|
||||
- `~/enshrouded/config/` — Configuration directory
|
||||
- `~/enshrouded/logs/` — Log files directory
|
||||
- `~/enshrouded/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Enshrouded
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# ET: Legacy — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./et-legacy_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `et-legacy_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/et-legacy/server.cfg` — Main server configuration
|
||||
- `~/et-legacy/config/` — Configuration directory
|
||||
- `~/et-legacy/logs/` — Log files directory
|
||||
- `~/et-legacy/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for ET: Legacy
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Euro Truck Simulator 2 / American Truck Simulator — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./euro-truck-simulator-2-american-truck-simulator_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `euro-truck-simulator-2-american-truck-simulator_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/euro-truck-simulator-2-american-truck-simulator/server.cfg` — Main server configuration
|
||||
- `~/euro-truck-simulator-2-american-truck-simulator/config/` — Configuration directory
|
||||
- `~/euro-truck-simulator-2-american-truck-simulator/logs/` — Log files directory
|
||||
- `~/euro-truck-simulator-2-american-truck-simulator/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Euro Truck Simulator 2 / American Truck Simulator
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Euro Truck Simulator 2 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./euro-truck-simulator-2_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `euro-truck-simulator-2_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/euro-truck-simulator-2/server.cfg` — Main server configuration
|
||||
- `~/euro-truck-simulator-2/config/` — Configuration directory
|
||||
- `~/euro-truck-simulator-2/logs/` — Log files directory
|
||||
- `~/euro-truck-simulator-2/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Euro Truck Simulator 2
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Factorio — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./factorio_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `factorio_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/factorio/server.cfg` — Main server configuration
|
||||
- `~/factorio/config/` — Configuration directory
|
||||
- `~/factorio/logs/` — Log files directory
|
||||
- `~/factorio/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Factorio
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Farming Simulator 2019 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./farming-simulator-2019_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `farming-simulator-2019_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/farming-simulator-2019/server.cfg` — Main server configuration
|
||||
- `~/farming-simulator-2019/config/` — Configuration directory
|
||||
- `~/farming-simulator-2019/logs/` — Log files directory
|
||||
- `~/farming-simulator-2019/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Farming Simulator 2019
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Farming Simulator 2022 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./farming-simulator-2022_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `farming-simulator-2022_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/farming-simulator-2022/server.cfg` — Main server configuration
|
||||
- `~/farming-simulator-2022/config/` — Configuration directory
|
||||
- `~/farming-simulator-2022/logs/` — Log files directory
|
||||
- `~/farming-simulator-2022/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Farming Simulator 2022
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Farming Simulator 2025 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./farming-simulator-2025_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `farming-simulator-2025_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/farming-simulator-2025/server.cfg` — Main server configuration
|
||||
- `~/farming-simulator-2025/config/` — Configuration directory
|
||||
- `~/farming-simulator-2025/logs/` — Log files directory
|
||||
- `~/farming-simulator-2025/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Farming Simulator 2025
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Farming Simulator 25 — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./farming-simulator-25_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `farming-simulator-25_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/farming-simulator-25/server.cfg` — Main server configuration
|
||||
- `~/farming-simulator-25/config/` — Configuration directory
|
||||
- `~/farming-simulator-25/logs/` — Log files directory
|
||||
- `~/farming-simulator-25/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Farming Simulator 25
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Farming Simulator — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./farming-simulator_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `farming-simulator_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/farming-simulator/server.cfg` — Main server configuration
|
||||
- `~/farming-simulator/config/` — Configuration directory
|
||||
- `~/farming-simulator/logs/` — Log files directory
|
||||
- `~/farming-simulator/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Farming Simulator
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Fistful of Frags — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./fistful-of-frags_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `fistful-of-frags_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/fistful-of-frags/server.cfg` — Main server configuration
|
||||
- `~/fistful-of-frags/config/` — Configuration directory
|
||||
- `~/fistful-of-frags/logs/` — Log files directory
|
||||
- `~/fistful-of-frags/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Fistful of Frags
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# FiveM — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./fivem_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `fivem_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/fivem/server.cfg` — Main server configuration
|
||||
- `~/fivem/config/` — Configuration directory
|
||||
- `~/fivem/logs/` — Log files directory
|
||||
- `~/fivem/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for FiveM
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,55 +0,0 @@
|
|||
<?php
|
||||
// game.php — renders a single Markdown doc and shows a Print / Save PDF button.
|
||||
$g = $_GET['g'] ?? '';
|
||||
$filenameOnly = pathinfo($g, PATHINFO_FILENAME); // strips .md or any extension
|
||||
$slug = preg_replace('/[^a-z0-9\-]/', '', strtolower($filenameOnly));
|
||||
|
||||
$path = __DIR__ . "/{$slug}.md";
|
||||
|
||||
|
||||
if (!$slug || !file_exists($path)) {
|
||||
http_response_code(404);
|
||||
echo "Guide not found.";
|
||||
exit;
|
||||
}
|
||||
require_once __dir__ . '/Parsedown.php'; // single-file Markdown parser (drop into repo root)
|
||||
$md = file_get_contents($path);
|
||||
$Parsedown = new Parsedown();
|
||||
$html = $Parsedown->text($md);
|
||||
?><!doctype html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<title><?php echo htmlspecialchars($slug); ?> — Game Guide</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<style>
|
||||
:root { --bg:#0f172a; --paper:#ffffff; --text:#111827; --ink:#111827; }
|
||||
body { margin:0; background:var(--bg); }
|
||||
.toolbar { position:sticky; top:0; background:#0b1220; border-bottom:1px solid #1f2937; padding:10px 16px; display:flex; gap:8px; align-items:center; }
|
||||
.btn { border:1px solid #1f2937; background:#111827; color:#e5e7eb; padding:8px 12px; border-radius:10px; cursor:pointer; }
|
||||
.btn:hover { opacity:.9; }
|
||||
.wrap { max-width: 900px; margin: 18px auto 48px; background:var(--paper); color:var(--text); padding:28px; border-radius:14px; }
|
||||
.wrap h1,h2,h3 { color:var(--ink); }
|
||||
pre, code { background:#f3f4f6; border-radius:8px; padding:2px 6px; }
|
||||
pre { padding:12px; overflow:auto; }
|
||||
@media print {
|
||||
body { background:#fff; }
|
||||
.toolbar { display:none !important; }
|
||||
.wrap { margin:0; max-width:100%; border-radius:0; padding:24mm; }
|
||||
a[href]:after { content:" (" attr(href) ")"; font-size:10pt; }
|
||||
h1 { page-break-before: always; }
|
||||
h2 { page-break-after: avoid; }
|
||||
pre { page-break-inside: avoid; }
|
||||
}
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<div class="toolbar">
|
||||
<button class="btn" onclick="window.print()">Print / Save PDF</button>
|
||||
<a class="btn" href="<?php echo 'https://github.com/Gameservers-World/ControlPanel/tree/main/docs/games/'.rawurlencode($slug).'.md'; ?>" target="_blank" rel="noopener">Edit in GitHub</a>
|
||||
</div>
|
||||
<div class="wrap">
|
||||
<?php echo $html; ?>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,169 +0,0 @@
|
|||
# Garry’s Mod — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game garrysmod -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Garry’s Mod/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Garry’s Mod/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Garry’s Mod/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Garry’s Mod/motd.txt` — Message of the day
|
||||
- `steamapps/common/Garry’s Mod/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Garry’s Mod/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Garry’s Mod/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Garry’s Mod/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
**Collection Mounting:**
|
||||
1. Create Steam Workshop collection with server content
|
||||
2. Add to startup: `+host_workshop_collection <collection_id>`
|
||||
3. Set Steam Web API key: `+sv_setsteamaccount <token>`
|
||||
|
||||
**Resource Management:**
|
||||
- Use `resource.AddWorkshopFile(id)` in Lua for required downloads
|
||||
- Large workshop collections may cause long loading times
|
||||
- Consider FastDL for faster content delivery
|
||||
|
||||
**Auto-Download:**
|
||||
- Players automatically download workshop content
|
||||
- Monitor download progress in server console
|
||||
- Some content may require manual subscription by players
|
||||
|
||||
**Cache Location:**
|
||||
- Windows: `steamapps/workshop/content/4000/`
|
||||
- Linux: `~/.steam/steamapps/workshop/content/4000/`
|
||||
|
||||
## Common Mods (curated)
|
||||
- **DarkRP**
|
||||
- **Purpose**: Popular roleplay gamemode framework.
|
||||
- **Install**: Download from workshop or GitHub, extract to gamemodes directory.
|
||||
- **Configure**: Edit `gamemodes/darkrp/gamemode/config.lua` for server settings.
|
||||
|
||||
- **ULX/ULib**
|
||||
- **Purpose**: Admin framework with extensive user management.
|
||||
- **Install**: Download both ULX and ULib, extract to addons directory.
|
||||
- **Configure**: Admin groups and permissions in `data/ulx/` directory.
|
||||
|
||||
- **Wiremod**
|
||||
- **Purpose**: Advanced contraption building with electronic components.
|
||||
- **Install**: Subscribe via Workshop or manual installation to addons.
|
||||
- **Configure**: No specific configuration required, workshop auto-download.
|
||||
|
||||
- **PAC3**
|
||||
- **Purpose**: Player appearance customization system.
|
||||
- **Install**: Workshop subscription, auto-downloads to clients.
|
||||
- **Configure**: Server settings in `cfg/pac.cfg` if needed.
|
||||
|
||||
## Database
|
||||
**Engine**: SQLite/MySQL
|
||||
|
||||
**Configuration**:
|
||||
- Database settings typically in main server configuration file
|
||||
- Connection parameters: host, port, database name, credentials
|
||||
- Enable persistence features in server configuration
|
||||
|
||||
**Setup**:
|
||||
1. Install database engine if required
|
||||
2. Create database and user with appropriate permissions
|
||||
3. Configure connection settings in server config
|
||||
4. Test connection before starting server
|
||||
5. Set up automated backups
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Ground Branch — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./ground-branch_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `ground-branch_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/ground-branch/server.cfg` — Main server configuration
|
||||
- `~/ground-branch/config/` — Configuration directory
|
||||
- `~/ground-branch/logs/` — Log files directory
|
||||
- `~/ground-branch/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Ground Branch
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,135 +0,0 @@
|
|||
# Half-Life 2: Deathmatch — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
srcds_run -game hl2mp -console -usercon +hostport 27015 +map de_dust2 +maxplayers 16 +exec server.cfg
|
||||
```
|
||||
|
||||
**Parameters (exhaustive, server-relevant only)**
|
||||
- `-game <dir>` — Game directory. Required.
|
||||
- `-console` — Enable server console output.
|
||||
- `-usercon` — Enable user console commands.
|
||||
- `+hostport <port>` — Server port (UDP). Default: 27015.
|
||||
- `+ip <address>` — Bind to specific IP address.
|
||||
- `+map <mapname>` — Starting map. Required.
|
||||
- `+maxplayers <num>` — Maximum players (1-64).
|
||||
- `+exec <file>` — Execute config file on startup.
|
||||
- `+sv_setsteamaccount <token>` — Game Server Login Token for public servers.
|
||||
- `+rcon_password <pass>` — RCON password for remote administration.
|
||||
- `+sv_password <pass>` — Server password for private games.
|
||||
- `+hostname <name>` — Server name in browser.
|
||||
- `+sv_lan <0|1>` — LAN mode (0=Internet, 1=LAN only).
|
||||
- `-tickrate <rate>` — Server tickrate (default: 66, competitive: 128).
|
||||
- `-port <port>` — Alternative syntax for hostport.
|
||||
- `-nohltv` — Disable SourceTV.
|
||||
- `+tv_enable <0|1>` — Enable/disable SourceTV.
|
||||
- `+tv_port <port>` — SourceTV port (default: hostport + 5).
|
||||
- `-secure` — Enable VAC (Valve Anti-Cheat).
|
||||
- `-insecure` — Disable VAC (for testing only).
|
||||
- `+sv_region <num>` — Server region (255=world, 0-7=specific regions).
|
||||
- `+fps_max <fps>` — Server FPS limit.
|
||||
- `-threads <num>` — Number of worker threads.
|
||||
- `-norestart` — Don't restart server on crash.
|
||||
- `+log <on|off>` — Enable/disable logging.
|
||||
- `-condebug` — Log console output to file.
|
||||
- `+sv_logfile <0|1>` — Enable server logging.
|
||||
- `+sv_logflush <0|1>` — Flush logs immediately.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (primary)
|
||||
- RCON: TCP **27015** (same as game port)
|
||||
- SourceTV: UDP **27020** (game port + 5)
|
||||
- Steam Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/cfg/server.cfg` — Main server configuration
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/mapcycle.txt` — Map rotation list
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/motd.txt` — Message of the day
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/banned_user.cfg` — Banned users
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/banned_ip.cfg` — Banned IP addresses
|
||||
- `steamapps/common/Half-Life 2: Deathmatch/logs/` — Server logs directory
|
||||
|
||||
**Linux:**
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/cfg/server.cfg` — Main server configuration
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/cfg/autoexec.cfg` — Auto-executed commands
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/mapcycle.txt` — Map rotation list
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/motd.txt` — Message of the day
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/banned_user.cfg` — Banned users
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/banned_ip.cfg` — Banned IP addresses
|
||||
- `~/.steam/steamapps/common/Half-Life 2: Deathmatch/logs/` — Server logs directory
|
||||
|
||||
**Key Configuration Files:**
|
||||
- **server.cfg**: Core server settings (rates, game rules, admin settings)
|
||||
- **autoexec.cfg**: Commands executed on server start
|
||||
- **mapcycle.txt**: Map rotation configuration
|
||||
- **motd.txt**: Welcome message displayed to connecting players
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Half-Life 2: Deathmatch
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Half-Life Deathmatch: Source — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./half-life-deathmatch-source_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `half-life-deathmatch-source_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/half-life-deathmatch-source/server.cfg` — Main server configuration
|
||||
- `~/half-life-deathmatch-source/config/` — Configuration directory
|
||||
- `~/half-life-deathmatch-source/logs/` — Log files directory
|
||||
- `~/half-life-deathmatch-source/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Half-Life Deathmatch: Source
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Half-Life: Deathmatch — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./half-life-deathmatch_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `half-life-deathmatch_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/half-life-deathmatch/server.cfg` — Main server configuration
|
||||
- `~/half-life-deathmatch/config/` — Configuration directory
|
||||
- `~/half-life-deathmatch/logs/` — Log files directory
|
||||
- `~/half-life-deathmatch/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Half-Life: Deathmatch
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# HEAT — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./heat_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `heat_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/heat/server.cfg` — Main server configuration
|
||||
- `~/heat/config/` — Configuration directory
|
||||
- `~/heat/logs/` — Log files directory
|
||||
- `~/heat/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for HEAT
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,102 +0,0 @@
|
|||
# Hell Let Loose — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
Hell Let LooseServer.exe -log -Port=7777 -QueryPort=27015
|
||||
```
|
||||
|
||||
**Parameters (common Unreal server flags)**
|
||||
- `-log` — Enable logging.
|
||||
- `-Port=<port>` — Game port.
|
||||
- `-QueryPort=<port>` — Steam query port.
|
||||
- `-MaxPlayers=<num>` — Maximum players.
|
||||
- `-ServerName="<name>"` — Server name.
|
||||
- `-ServerPassword="<pass>"` — Server password.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **7777** (typical)
|
||||
- Query: UDP **27015** (Steam query)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `WindowsServer/Hell Let Loose/Saved/Config/WindowsServer/` — Configuration directory
|
||||
- `WindowsServer/Hell Let Loose/Saved/Logs/` — Log files
|
||||
- `WindowsServer/Hell Let Loose/Saved/SaveGames/` — Save files
|
||||
|
||||
**Linux:**
|
||||
- `/home/hell-let-loose/Saved/Config/LinuxServer/` — Configuration directory
|
||||
- `/home/hell-let-loose/Saved/Logs/` — Log files
|
||||
- `/home/hell-let-loose/Saved/SaveGames/` — Save files
|
||||
|
||||
**Key Files:**
|
||||
- **GameUserSettings.ini**: Main server configuration
|
||||
- **Game.ini**: Advanced game settings
|
||||
- **Engine.ini**: Engine-specific settings
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Hell Let Loose
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Humanitz — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./humanitz_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `humanitz_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/humanitz/server.cfg` — Main server configuration
|
||||
- `~/humanitz/config/` — Configuration directory
|
||||
- `~/humanitz/logs/` — Log files directory
|
||||
- `~/humanitz/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Humanitz
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,102 +0,0 @@
|
|||
# Hurtworld — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
hurtworld_server.exe -batchmode -nographics -dedicated -port 27015
|
||||
```
|
||||
|
||||
**Parameters (common Unity server flags)**
|
||||
- `-batchmode` — Run without GUI.
|
||||
- `-nographics` — Disable graphics rendering.
|
||||
- `-dedicated` — Dedicated server mode.
|
||||
- `-port <port>` — Server port.
|
||||
- `-logFile <path>` — Log file location.
|
||||
- `-quit` — Quit after operations complete.
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `Data/` — Game data directory
|
||||
- `Logs/` — Log files directory
|
||||
- `ServerConfig/` — Configuration files (varies by game)
|
||||
|
||||
**Linux:**
|
||||
- `~/hurtworld/Data/` — Game data directory
|
||||
- `~/hurtworld/Logs/` — Log files directory
|
||||
- `~/hurtworld/ServerConfig/` — Configuration files
|
||||
|
||||
**Key Files:**
|
||||
- Configuration file names and locations vary significantly between Unity games
|
||||
- Common patterns: server.cfg, config.json, settings.xml
|
||||
- Check game-specific documentation for exact file locations
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Hurtworld
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# HYPERCHARGE: Unboxed — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./hypercharge-unboxed_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `hypercharge-unboxed_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/hypercharge-unboxed/server.cfg` — Main server configuration
|
||||
- `~/hypercharge-unboxed/config/` — Configuration directory
|
||||
- `~/hypercharge-unboxed/logs/` — Log files directory
|
||||
- `~/hypercharge-unboxed/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for HYPERCHARGE: Unboxed
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Icarus — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./icarus_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `icarus_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/icarus/server.cfg` — Main server configuration
|
||||
- `~/icarus/config/` — Configuration directory
|
||||
- `~/icarus/logs/` — Log files directory
|
||||
- `~/icarus/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Icarus
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,92 +0,0 @@
|
|||
<?php
|
||||
// index.php — lists all games (from CSV) and links to per-game pages in new tabs.
|
||||
|
||||
$csvPath = __DIR__ . '/all_hostable_games_union.csv';
|
||||
$docsDir = __DIR__ ;
|
||||
|
||||
function slugify($name) {
|
||||
$s = strtolower($name);
|
||||
$s = preg_replace('/[^a-z0-9]+/','-',$s);
|
||||
$s = trim($s,'-');
|
||||
return $s;
|
||||
}
|
||||
function hasDoc($slug, $docsDir) {
|
||||
return file_exists("$docsDir/$slug.md");
|
||||
}
|
||||
|
||||
$rows = [];
|
||||
if (file_exists($csvPath)) {
|
||||
if (($fh = fopen($csvPath, 'r')) !== false) {
|
||||
// Try to detect header; expect first column to be game name.
|
||||
$header = fgetcsv($fh);
|
||||
$hasHeader = $header && preg_match('/game/i', implode(' ', $header));
|
||||
if (!$hasHeader && $header) { $rows[] = $header; } // headerless, keep first line
|
||||
while (($data = fgetcsv($fh)) !== false) { $rows[] = $data; }
|
||||
fclose($fh);
|
||||
}
|
||||
}
|
||||
?><!doctype html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<title>Game Server Guides</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<style>
|
||||
:root { --bg:#0f172a; --card:#111827; --text:#e5e7eb; --muted:#94a3b8; --accent:#38bdf8; }
|
||||
body { background:var(--bg); color:var(--text); font:16px/1.5 system-ui,Segoe UI,Roboto,Helvetica,Arial; margin:0; }
|
||||
header { padding:24px; border-bottom:1px solid #1f2937; }
|
||||
h1 { margin:0 0 8px; font-size:24px; }
|
||||
.wrap { padding:24px; max-width:1100px; margin:0 auto; }
|
||||
.search { width:100%; padding:12px 14px; border-radius:12px; border:1px solid #1f2937; background:#0b1220;color:var(--text); }
|
||||
.grid { display:grid; grid-template-columns:repeat(auto-fill,minmax(260px,1fr)); gap:12px; margin-top:16px; }
|
||||
.card { background:var(--card); border:1px solid #1f2937; border-radius:12px; padding:14px; }
|
||||
.card a { color:var(--accent); text-decoration:none; font-weight:600; }
|
||||
.pending { color:var(--muted); }
|
||||
.tag { display:inline-block; font-size:12px; color:#cbd5e1; background:#0b1220; padding:2px 8px; border-radius:999px; margin-top:8px; border:1px solid #1f2937; }
|
||||
footer { color:var(--muted); padding:24px; border-top:1px solid #1f2937; }
|
||||
</style>
|
||||
<script>
|
||||
function filterList(q) {
|
||||
q = q.toLowerCase();
|
||||
document.querySelectorAll('.card').forEach(card => {
|
||||
const name = card.dataset.name;
|
||||
card.style.display = name.includes(q) ? '' : 'none';
|
||||
});
|
||||
}
|
||||
</script>
|
||||
</head>
|
||||
<body>
|
||||
<header class="wrap">
|
||||
<h1>Game Server Guides</h1>
|
||||
<input class="search" placeholder="Search games…" oninput="filterList(this.value)">
|
||||
<p class="muted">Click a game to open its guide in a new tab; each page has a “Print / Save PDF” button.</p>
|
||||
</header>
|
||||
<div class="wrap">
|
||||
<div class="grid">
|
||||
<?php
|
||||
$count = 0;
|
||||
foreach ($rows as $r) {
|
||||
$game = trim($r[0] ?? '');
|
||||
if ($game === '' || strtolower($game) === 'game') continue;
|
||||
$slug = slugify($game);
|
||||
$exists = hasDoc($slug, $docsDir);
|
||||
$count++;
|
||||
echo '<div class="card" data-name="'.htmlspecialchars(strtolower($game)).'">';
|
||||
if ($exists) {
|
||||
echo '<a href="game.php?g='.urlencode($slug).'" target="_blank">'.htmlspecialchars($game).'</a>';
|
||||
echo '<div class="tag">Guide ready</div>';
|
||||
} else {
|
||||
echo '<span class="pending">'.htmlspecialchars($game).'</span>';
|
||||
echo '<div class="tag">Pending</div>';
|
||||
}
|
||||
echo '</div>';
|
||||
}
|
||||
if ($count === 0) {
|
||||
echo '<p>No games found. Make sure all_hostable_games_union.csv exists in repo root.</p>';
|
||||
}
|
||||
?>
|
||||
</div>
|
||||
</div>
|
||||
<footer class="wrap">Tip: add or edit docs under <code>docs/games/<slug>.md</code>. Slug = lowercased name with non-alphanumerics as dashes.</footer>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -1,111 +0,0 @@
|
|||
# Insurgency: Sandstorm — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./insurgency-sandstorm_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `insurgency-sandstorm_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/insurgency-sandstorm/server.cfg` — Main server configuration
|
||||
- `~/insurgency-sandstorm/config/` — Configuration directory
|
||||
- `~/insurgency-sandstorm/logs/` — Log files directory
|
||||
- `~/insurgency-sandstorm/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
**Workshop Integration:**
|
||||
- Check Steam Workshop for community content
|
||||
- Subscribe to collections via Steam client
|
||||
- Server automatically downloads subscribed content
|
||||
- Configure workshop content loading in server configuration
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Insurgency: Sandstorm
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# Insurgency — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./insurgency_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `insurgency_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/insurgency/server.cfg` — Main server configuration
|
||||
- `~/insurgency/config/` — Configuration directory
|
||||
- `~/insurgency/logs/` — Log files directory
|
||||
- `~/insurgency/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for Insurgency
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# IOSoccer — Complete Dedicated Server Guide
|
||||
|
||||
## Startup Parameters
|
||||
**Default command line**
|
||||
```bash
|
||||
./iosoccer_server -port 27015 -maxplayers 16 -config server.cfg
|
||||
```
|
||||
|
||||
**Parameters (common server flags)**
|
||||
- `-port <port>` — Server port (default varies by game)
|
||||
- `-maxplayers <num>` — Maximum player count
|
||||
- `-config <file>` — Configuration file to load
|
||||
- `-log` — Enable logging
|
||||
- `-console` — Enable console output
|
||||
- `-dedicated` — Run as dedicated server
|
||||
- `-name "<name>"` — Server name
|
||||
- `-password "<pass>"` — Server password
|
||||
|
||||
**Ports**
|
||||
- Game: UDP **27015** (typical default)
|
||||
- Query: UDP **27016** (game port + 1)
|
||||
- Admin/RCON: TCP **varies by game**
|
||||
|
||||
## Config Files & Locations
|
||||
**Windows:**
|
||||
- `iosoccer_server.cfg` — Main server configuration
|
||||
- `config/` — Configuration directory
|
||||
- `logs/` — Log files directory
|
||||
- `data/` — Server data and saves
|
||||
|
||||
**Linux:**
|
||||
- `~/iosoccer/server.cfg` — Main server configuration
|
||||
- `~/iosoccer/config/` — Configuration directory
|
||||
- `~/iosoccer/logs/` — Log files directory
|
||||
- `~/iosoccer/data/` — Server data and saves
|
||||
|
||||
**Key Files:**
|
||||
- **server.cfg**: Core server settings and game rules
|
||||
- **admins.cfg**: Administrator configuration (if applicable)
|
||||
- **banned.cfg**: Banned players list (if applicable)
|
||||
|
||||
## Steam Workshop
|
||||
Not supported by this game.
|
||||
|
||||
## Common Mods (curated)
|
||||
**Admin/Management Mods**
|
||||
- Check official mod repositories or community sites for IOSoccer
|
||||
- Look for server administration, anti-cheat, and quality-of-life mods
|
||||
- Install according to game's modding framework (if available)
|
||||
|
||||
**Popular Community Mods**
|
||||
- Search Steam Workshop (if supported) for highly-rated server mods
|
||||
- Check game's official forums and community sites for recommended mods
|
||||
- Verify mod compatibility with current server version
|
||||
|
||||
**Installation Notes**
|
||||
- Follow each mod's specific installation instructions
|
||||
- Some games require mod loading frameworks or special startup parameters
|
||||
- Test mods individually before combining multiple mods
|
||||
|
||||
## Database
|
||||
Not applicable - this game does not use a database for core functionality.
|
||||
|
||||
## Administration & Scripting
|
||||
**Remote Administration:**
|
||||
- RCON (Remote Console) access for server management
|
||||
- Web-based admin panels (game-specific or third-party)
|
||||
- In-game admin commands and permissions
|
||||
|
||||
**Backup Strategy:**
|
||||
- Automated daily backups of save files and configuration
|
||||
- Rotate backups (keep 7 daily, 4 weekly, 12 monthly)
|
||||
- Test backup restoration procedures regularly
|
||||
- Store backups in separate location/drive
|
||||
|
||||
**Auto-Update:**
|
||||
- Use SteamCMD for automatic server updates (Steam games)
|
||||
- Schedule updates during low-traffic periods
|
||||
- Backup before applying updates
|
||||
- Monitor for update announcements and patch notes
|
||||
|
||||
**Monitoring:**
|
||||
- Server performance monitoring (CPU, memory, network)
|
||||
- Player connection logs and statistics
|
||||
- Error log monitoring and alerting
|
||||
- Uptime tracking and availability reporting
|
||||
|
||||
## Troubleshooting (game-specific)
|
||||
**Server not starting**
|
||||
- **Cause**: Missing dependencies, incorrect configuration, or port conflicts
|
||||
- **Fix**: Check server logs, verify all required files are present, ensure ports are available
|
||||
|
||||
**Players cannot connect**
|
||||
- **Cause**: Firewall blocking server port or incorrect network configuration
|
||||
- **Fix**: Open required ports in firewall, verify server is binding to correct IP address
|
||||
|
||||
**Performance issues/lag**
|
||||
- **Cause**: Insufficient server resources or suboptimal configuration
|
||||
- **Fix**: Monitor CPU/memory usage, optimize server settings, reduce player/entity limits
|
||||
|
||||
**Configuration not loading**
|
||||
- **Cause**: Syntax errors in config files or incorrect file paths
|
||||
- **Fix**: Validate configuration file syntax, check file permissions, review server logs
|
||||
|
||||
**Mod/plugin conflicts**
|
||||
- **Cause**: Incompatible mods or plugin version mismatches
|
||||
- **Fix**: Test mods individually, update to compatible versions, check for known conflicts
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Add a link
Reference in a new issue