38 lines
960 B
Markdown
38 lines
960 B
Markdown
# Companion Programs
|
|
|
|
## Current State
|
|
|
|
Companion programs are not yet a first-class managed system. Current behavior is mostly script-driven and game-specific.
|
|
|
|
Important references:
|
|
|
|
- `docs/decisions/0003-companion-programs.md`
|
|
- `Agent_Linux/ogp_agent.pl`
|
|
- `Agent-Windows/OGP64/OGP/ogp_agent.pl`
|
|
- `Panel/modules/config_games/schema_server_config.xml`
|
|
|
|
## What The System Needs To Do
|
|
|
|
- start companion apps with the server
|
|
- stop companion apps when the server stops
|
|
- restart companion apps when the server restarts
|
|
- track PIDs or handles
|
|
- log stdout/stderr
|
|
- avoid customer-editable privileged startup scripts
|
|
|
|
## Good Companion Examples
|
|
|
|
- BEC for Arma/DayZ
|
|
- B3
|
|
- Discord bots or bridges
|
|
- log watchers
|
|
- stats collectors
|
|
- anti-cheat helpers
|
|
|
|
## Recommended Shape
|
|
|
|
The system should be XML/admin-defined and agent-managed.
|
|
|
|
## Recommendation
|
|
|
|
Keep the design centralized and game-aware. Do not rely on one-off helper files as the source of truth.
|