Time-limit pick lists go from 9 entries (max 30 min) to 23:
1-15, 20, 25, 30, 45, 60, 120, 180, 240. Default stays 7 min.
Content + console only, no MW4.exe rebuild: nothing between the
dropdown and the mission timer clamps the value, and m_gameLength is
8 bits on the wire (MWApplication.cpp:790), so 255 min was always the
real ceiling.
- ConLobbyMission.script (venue console) + HostLobbyMission.script
(PC host lobby): new list, max_displayed = 10 on the time dropdown,
drop_list_size[5] 9 -> 23, and the hardcoded 9 loop bounds plus the
nselected = 3 fallbacks updated.
- TIME_LIST_DEFAULT is now the literal 6 (index of 7 min) instead of
the C++ global g_nTimeList_Index = 3: index 3 is 4 min in the new
list, and changing the global would have forced an exe rebuild. The
reset-to-defaults path matches by VALUE (g_nTimeList_Value = 7) and
needed no change.
- MISSION-TIME-LIMITS.md: value flow, display formats, why 0 (no time
limit) black-screens the networked HUD as shipped, and the Plan B
outline for going past 255.
Sources only: the repacked resource\*.mw4 packages, their .dep files,
the deployed MW4\resource copies and the staged MW4pro.exe are build
output and are NOT tracked here - rebuild them from main after this
merges (build-env\build-resources.ps1).
Verified locally against the built packages: FSConsole self-test green
against vpod_ctcl.py; the console launched windowed on the dev box with
the list scrolling 1 -> 240 and 240 selectable. Not yet run against a
real bay.
FSConsole's own changes (23-entry catalog, NmpBuilder 1-255 guard,
SelfTest.CheckTimeLimits) live in the still-untracked venue/ tree, so
they are NOT in this commit either.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
3514acf6d9