Repo Cleanup

docs/research/creation-kit-notes.md

@@ -0,0 +1,46 @@
+# Creation Kit Notes
+
+The Creation Kit side of Commonwealth Online should provide controlled test content for multiplayer development.
+
+## First Creation Kit Goals
+
+- Create a small test cell
+- Add player start markers
+- Add remote player placeholder markers
+- Add simple lighting
+- Avoid quests, doors, hostile NPCs, and complex world state
+
+## Suggested Test Cell
+
+```text
+F4TTestCell01
+```
+
+## Suggested Test Plugin
+
+```text
+Fallout4Together_Test.esp
+```
+
+## Test Cell Requirements
+
+The first test cell should include:
+
+- Flat ground
+- Clear lighting
+- No enemies
+- No quest dependencies
+- No doors to other cells
+- A few visual markers to judge movement
+- Enough space for movement syncing tests
+
+## Papyrus Scripts
+
+Papyrus may eventually be useful for helper systems, but networking should not be handled in Papyrus.
+
+Possible Papyrus uses:
+
+- Debug startup quest
+- Spawning helper actors
+- Showing messages
+- Triggering test events

docs/research/f4se-notes.md

@@ -0,0 +1,42 @@
+# F4SE Notes
+
+F4SE is expected to be the main entry point for the native plugin side of Commonwealth Online.
+
+## Plugin Goals
+
+The first plugin goals are:
+
+- Confirm the plugin loads
+- Create a log file
+- Detect the game version
+- Read the local player reference
+- Read the local player position
+- Send basic data to a local server
+
+## Expected Plugin Output
+
+Eventually, the compiled plugin should output something like:
+
+```text
+Data/F4SE/Plugins/CommonwealthOnline.dll
+```
+
+## Important Notes
+
+Do not commit F4SE binaries to this repository.
+
+Do not commit Fallout 4 executable files or game assets.
+
+Use a CommonLibF4 template to reduce setup friction.
+
+## Plugin Safety
+
+Avoid modifying Fallout 4 game objects directly from a networking thread.
+
+Recommended flow:
+
+```text
+Networking thread receives packets
+Networking thread stores packet data
+Main/game update applies safe changes
+```