Files
Commonwealth-Online-Public/docs/version-targets.md
T
andrew 8dfec0a4b3 Rename project to Commonwealth Online
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.
2026-06-07 16:22:50 +12:00

51 lines
1.3 KiB
Markdown

# Version Targets
Commonwealth Online is version-sensitive because it depends on Fallout 4, F4SE, and native plugin development.
## Primary Target
```text
Platform: Steam
Fallout 4 Version: 1.11.221.0
F4SE Version: 1.11.221.0
Creation Kit Version:
CommonLibF4 Template:
Compiler:
Build System:
```
## Notes
All multiplayer testing should use the same:
* Fallout 4 version
* F4SE version
* Commonwealth Online plugin version
* Commonwealth Online test ESP version
* Load order
* Test save
## Secondary Targets
```text
GOG: Not currently tested
Microsoft Store/Game Pass: Not supported
Console: Not supported
```
## Reasoning
F4SE supports the latest Fallout 4 versions available on Steam and GOG, but Steam and GOG are not always the same version. This means native plugin work should lock to one primary target during early development.
## Current Development Decision
Commonwealth Online will use the Steam build of Fallout 4 as the primary development target.
GOG support may be investigated later once the plugin loads successfully and the basic transform-sync prototype is working.
## Compatibility Warning
Commonwealth Online may not work across different Fallout 4 executable versions.
During testing, every connected player should use the same game version, F4SE version, plugin version, ESP version, and load order.