server content features improved
This commit is contained in:
parent
a28d3e1a4f
commit
8a56ddc83c
7 changed files with 464 additions and 3 deletions
|
|
@ -33,10 +33,31 @@ The module can already represent several content types, including:
|
|||
- downloads/extracted packages
|
||||
- post-script driven installs
|
||||
- config packs
|
||||
- server-side applications with lifecycle hooks
|
||||
- future profile-type content
|
||||
|
||||
Steam Workshop is no longer a user-facing Server Content category. Workshop access belongs to the dedicated `steam_workshop` module.
|
||||
|
||||
## Server-Side Applications
|
||||
|
||||
`Server-side Application` content writes an agent-readable hook manifest under
|
||||
the target game home:
|
||||
|
||||
```text
|
||||
_gsp_content/hooks/<app>.json
|
||||
```
|
||||
|
||||
The agents generate runtime watchdog scripts in `_gsp_content/generated/` and
|
||||
track side-application PIDs in `_gsp_content/runtime/server_content.pids`.
|
||||
|
||||
Use this type for companion applications such as BEC, Big Brother Bot, Discord
|
||||
bridges, RCON tools, and log watchers. The application files themselves may
|
||||
still be installed wherever the game requires them.
|
||||
|
||||
Detailed lifecycle documentation:
|
||||
|
||||
- `docs/features/SERVER_CONTENT_APPLICATION_HOOKS.md`
|
||||
|
||||
## Current Limitations
|
||||
|
||||
- Cache and cleanup policy need a clearer product design.
|
||||
|
|
@ -56,6 +77,7 @@ This module is the right place for:
|
|||
- add-ons
|
||||
- config packs
|
||||
- script-driven installs
|
||||
- server-side companion application hooks
|
||||
- server content manifests
|
||||
- install history
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue