Skip to content

Dark Forces: level 2 reachable again (a nameless agent no longer vanishes after mission 1); saving in big levels no longer crashes - #36

Merged
finger563 merged 2 commits into
mainfrom
fix/df-nameless-agent
Nov 21, 2026
Merged

finger563 merged 2 commits into
mainfrom
fix/df-nameless-agent

Conversation

@finger563

Copy link
Copy Markdown
Contributor

Summary

Bumps TheForceEngine to esp-cpp/TheForceEngine#2 (fix/nameless-agent), which fixes Dark Forces level 2 never becoming reachable:

  • A nameless agent no longer vanishes after mission 1. The agent menu lists agents up to the first one without a name, and New Agent accepted an empty name, which is easy with the gamepad text entry. After mission 1, mission 2 couldn't be begun, and the agent's progress was written back cleared. Agents now always have a name (AGENT <n>), and a stored nameless agent with progress gets one when the pilot file is read.
  • Saving in big levels no longer crashes. The save header captured the screen into a 256 KB buffer for its 4 × 4 image, and the screen capture is a stub here anyway. In Talay the allocation failed and the save crashed, leaving an empty slot. The header now gets the placeholder directly.

Testing

On the box and the Tab5 with the box's pilot file:

  • The agent menu lists AGENT 1, and Talay: Tak Base loads.
  • The existing Talay save loads.
  • A save in Talay completes and loads back (on the box).
  • On the box in Talay, about 120 KB of PSRAM is left. Memory there is tight, and that's a separate follow-up.

Merge esp-cpp/TheForceEngine#2 first; the submodule points at its branch.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SFCMzomCZ5wRHJN4sxwkvY

finger563 and others added 2 commits November 21, 2026 14:32
TheForceEngine fix/nameless-agent. The agent menu lists agents up to the
first one without a name, and the New Agent dialog accepted an empty name
(easy with the gamepad text entry). Such an agent played mission 1, then
the agent menu came back without it: mission 2 could not be begun, and the
agent's progress was written back cleared. Agents now always have a name
("AGENT <n>"), and a stored nameless agent with progress gets one when the
pilot file is read, so it comes back with its completed missions.

Tested on the Tab5 with the box's DARKPILO.CFG (a nameless agent with
mission 1 done): the agent menu lists AGENT 1 with Secret Base completed
and Talay: Tak Base available, and Talay loads (13.5 MB PSRAM free).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SFCMzomCZ5wRHJN4sxwkvY
…e buffer for the save header)

TheForceEngine fix/nameless-agent 8e777a8: on the handhelds the save
header's image is the 4x4 placeholder, written without allocating the
256 KB capture buffer (which failed in Talay on the box and crashed the
save, leaving the slot empty).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SFCMzomCZ5wRHJN4sxwkvY
@finger563
finger563 merged commit fe53b6c into main Nov 21, 2026
1 check passed
@finger563
finger563 deleted the fix/df-nameless-agent branch November 21, 2026 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant