complete codex docs
This commit is contained in:
parent
b5dcf01a8c
commit
3cefad183d
62 changed files with 2730 additions and 50 deletions
28
docs/decisions/0006-installers.md
Normal file
28
docs/decisions/0006-installers.md
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
# Decision 0006: Installers Must Be Game-Capability Driven
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Decision
|
||||
|
||||
Installer behavior should be driven by game XML capabilities and module metadata instead of ad hoc shell scripts or one-off module pages.
|
||||
|
||||
## Reasoning
|
||||
|
||||
- Different games need different install strategies.
|
||||
- Some games are content-copy based.
|
||||
- Some are SteamCMD based.
|
||||
- Some need key copying, startup parameter edits, or profile transforms.
|
||||
- The Panel needs a structured model to support all of them cleanly.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- per-game custom shell scripts only
|
||||
- raw customer-provided installer commands
|
||||
|
||||
## Why Those Were Not Chosen
|
||||
|
||||
- They are harder to secure and harder to document.
|
||||
- They do not scale cleanly across games or platforms.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue