Files
Commonwealth-Online-Public/docs/dev-log.md
T
andrew a643f86c34 Add initial docs: dev log and version targets
Add docs/dev-log.md and docs/version-targets.md to seed project documentation. dev-log.md provides a development log and template for recording setup steps, decisions, current focus, status, and next steps. version-targets.md records primary target platform and exact Fallout 4/F4SE version targets, testing notes, and compatibility guidance to ensure consistent environment for early native plugin development.
2026-05-30 18:21:02 +12:00

92 lines
1.9 KiB
Markdown

# Development Log
This file tracks the development progress of Fallout 4 Together.
Use this log to record setup decisions, tool versions, technical discoveries, failed experiments, and successful tests.
---
## 2026-05-30
### Repo Setup
* Created the Fallout 4 Together repository.
* Added the initial repository folder structure.
* Added starter Markdown documentation files.
* Added project roadmap, disclaimer, setup notes, protocol notes, and plugin planning documents.
### Current Focus
The current focus is setting up the early development environment before writing multiplayer logic.
The immediate priority is to make sure the project has:
* A documented target Fallout 4 version
* A documented F4SE version
* A chosen CommonLibF4 plugin template
* A clean Fallout 4 test profile
* A basic native plugin that can load through F4SE
### Decisions Made
* Project name: Fallout 4 Together
* Internal prefix: F4T
* Primary target platform: Steam Fallout 4
* First prototype goal: two clients in a controlled test cell, with each player visible as a synced remote actor
* Early test cell name: F4TTestCell01
* Early test ESP name: Fallout4Together_Test.esp
* Early plugin DLL name: Fallout4Together.dll
### Current Status
```text
Repository created
Documentation structure added
Version tracking started
No plugin code yet
No server code yet
No Creation Kit test cell yet
```
### Next Steps
* Add `docs/version-targets.md` to the repository.
* Fill in the exact installed Fallout 4 version.
* Fill in the exact installed F4SE version.
* Choose a CommonLibF4 plugin template.
* Create the first GitHub milestones.
* Create the first GitHub issues.
* Set up a clean Fallout 4 test profile.
* Build an empty F4SE plugin.
* Confirm the empty plugin loads in Fallout 4.
---
## Template Entry
Use this format for future updates:
```markdown
## YYYY-MM-DD
### What Changed
-
### What Worked
-
### What Broke
-
### Notes
-
### Next Steps
-
```