Repository navigation
feat(recorder): pass save tag to extension on :MISSION:SAVE: - #129
Conversation
Send the effective save tag (explicit OCAP_exportData override, else the
OCAP_settings_saveTag setting) as the first :MISSION:SAVE: arg so the
extension can forward it on the streaming end_mission envelope as
{"tag":"..."} (OCAP2/extension#213, OCAP2/web#571).
Extensions built before the arg parse ignore :MISSION:SAVE: args, so this
degrades silently to today's behavior.
c2f5f90 to
d3f5cc4
Compare
|
🔏 Readiness attested — the Readiness summaryPR Readiness Check (#129, d3f5cc4) — FOLLOW-UP REFRESH |
What
fnc_exportData.sqfnow sends the effective save tag as the first:MISSION:SAVE:argument instead of an empty args array:_saveTagis the explicitOCAP_exportDatathird-param override, falling back to theOCAP_settings_saveTagsetting (default"TvT"), so the effective tag always ships.Why
The extension (OCAP2/extension#213, merged) now parses the
:MISSION:SAVE:first arg, SQF-unquotes it, and forwards non-empty tags on the streamingend_missionenvelope as{"tag":"..."}, which the web (OCAP2/web#571) consumes as the save-tag override. Previously the tag was computed but never left the addon (no-op[]).:EVENT:ENDMISSION:is intentionally untouched — it stays a gameplay (side/message) event; the save tag is a lifecycle/finalization value.Compatibility
Extensions built before the arg parse ignore
:MISSION:SAVE:args entirely, so this degrades silently to today's behavior (tag dropped, mission-start tag used). An empty/blank tag is treated by the extension as "no override".Test plan
["OCAP_exportData", [west, "msg", "myTag"]] call CBA_fnc_serverEvent;→ tag reaches web as override.