"vault backup: 2026-03-20 14:45:56 from Flow"
This commit is contained in:
@@ -160,6 +160,24 @@ GAME_MOD_IDS: "839162288,1999447172,1609138312,..."
|
|||||||
|
|
||||||
Mods are downloaded automatically on container start.
|
Mods are downloaded automatically on container start.
|
||||||
|
|
||||||
|
## Future Ideas
|
||||||
|
|
||||||
|
### Event Webhooks (Discord / n8n)
|
||||||
|
ARK logs all server events to `ShooterGame.log`. A lightweight log-watcher sidecar container can tail this file and fire webhooks on pattern matches — routing through n8n or directly to Discord.
|
||||||
|
|
||||||
|
Detectable events and their log patterns:
|
||||||
|
| Event | Log pattern |
|
||||||
|
|---|---|
|
||||||
|
| Server ready | `Full Startup` |
|
||||||
|
| Player join | `joined this ARK` |
|
||||||
|
| Player leave | `left this ARK` |
|
||||||
|
| World save | `World Saved` |
|
||||||
|
| Shutdown | `DoExit` |
|
||||||
|
|
||||||
|
The sidecar would mount `/ARK_Server/data/server/ShooterGame/Saved/Logs` read-only and POST to an n8n webhook. arkmanager has a native `discordWebhookURL` config option but it only covers update warnings — the log-watcher approach covers everything.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## Notes
|
## Notes
|
||||||
|
|
||||||
- Uses `hermsi/ark-server` which wraps `arkmanager` internally — use `docker exec ark_server arkmanager <cmd>` for manual operations
|
- Uses `hermsi/ark-server` which wraps `arkmanager` internally — use `docker exec ark_server arkmanager <cmd>` for manual operations
|
||||||
|
|||||||
Reference in New Issue
Block a user