andrew
8dfec0a4b3
Replace occurrences of "Fallout 4 Together" with "Commonwealth Online" across docs and testing guidance. Add Interface assets and tooling: MainMenu/Pipboy SWFs, translation/fonts, exported scripts (Interface/exported/scripts/MainMenu.as) and a PATCH_MainMenu_Multiplayer.md describing how to add a Multiplayer menu entry that calls root.f4se.plugins.commonwealthOnline.openManager(). Also add build/run batch scripts and apply assorted updates to README, plugin, server and protocol documentation/source to align with the rename and UI changes.
47 lines
939 B
Markdown
47 lines
939 B
Markdown
# 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
|