60 lines
2.9 KiB
Markdown
60 lines
2.9 KiB
Markdown
# Workshop preview
|
||
|
||
Project name: **Co10 Escape Reintroduced**. Author: **Jakub Jim Žáček**.
|
||
The only shipped scenario is **Co10 Escape Reintroduced — Automatic terrain**:
|
||
|
||
```text
|
||
{C1E20667DCE324ED}Missions/ERR_Everon.conf
|
||
```
|
||
|
||
The legacy `ERR_Everon_Base.conf` diagnostic header has been removed from the
|
||
addon. Diagnostics now use the same main scenario. Hiding the duplicate from the
|
||
in-game menu did not remove its published Workshop listing. Before publishing,
|
||
rescan/rebuild the project resources and create a fresh package from current
|
||
source; do not reuse an older frozen `.build` package containing that header.
|
||
After publication, verify that the latest Workshop revision lists only the main
|
||
scenario. The currently published listing is not changed by this source edit.
|
||
Servers using the retired `{AD62322D5213C440}` scenario ID must select the main
|
||
entry above. Its ID remains unchanged.
|
||
|
||
The generic launcher title avoids advertising the wrong terrain after an in-game
|
||
terrain redirect; it does not make backend terrain-name updates dynamic.
|
||
|
||
Use `previewImage.png` in Workbench's **Publish project → Preview Image** field.
|
||
It is the original 512×256 PNG supplied by the user, downloaded unchanged from
|
||
[CaptainPStar/co10_Escape](https://github.com/CaptainPStar/co10_Escape/blob/master/escape_banner.png).
|
||
The artwork retains its original **Co10 ESCAPE** title.
|
||
|
||
On this Linux/Proton installation, the file-picker path is:
|
||
|
||
```text
|
||
Z:\home\jakub\devel\escapistsrereintroduced\publishing\previewImage.png
|
||
```
|
||
|
||
Workbench also supports passing the image path using
|
||
[`-publishAddonPreviewImage`](https://community.bistudio.com/wiki/Arma_Reforger:Startup_Parameters#publishAddonPreviewImage).
|
||
Saving this file does not automatically select it in an already-open publishing
|
||
dialog. Select it before publishing.
|
||
|
||
This directory holds publishing artwork separately from game resources, so the
|
||
PNG does not need Enfusion texture metadata or inclusion in the runtime PAK.
|
||
|
||
## Recording the published version
|
||
|
||
The project `.gproj` does not store the Workshop release version. Workbench stores
|
||
it as `asset.version` in its local publishing `manifest.json`; the top-level
|
||
`version` is the manifest schema. The latest recorded published version is in
|
||
the preamble of [CHANGELOG.md](../CHANGELOG.md).
|
||
|
||
After a successful Workshop upload, run
|
||
`python3 tools/workshop_changelog.py --published` to copy the version into
|
||
`CHANGELOG.md`. The default manifest path
|
||
targets this Linux/Proton Workbench installation; `--manifest PATH` overrides it.
|
||
Running without `--published` only shows the bundled version. The helper does not
|
||
publish or verify the online Workshop revision, so compilation alone is not enough
|
||
to record a release as published.
|
||
|
||
Add the player-facing changes to the newest changelog entry, commit all intended
|
||
source and changelog changes, then push. Drone includes the recorded version in
|
||
the Discord changelog. See [the notification workflow](../docs/discord-changelog-ci.md).
|