Duran’s story continues after Bruiser

What it plays

Starting at Bruiser’s surrender, the controller approaches King Richard, follows the background narration and family memories, crosses the rooftop, checks the fallen guard and pursues the intruder through the castle. It continues through the next-day council and Wendy’s visit, then pauses when control returns at the pub.

The intruder battle is a required story defeat. The controller observes Duran survive at low health, waits for the soldiers and follows the retreat. Actual runs ended at 7 or 8 HP. It does not claim that encounter as a win. The original game restores health later in the story.

What training changed

Long legitimate fades needed a story observation mode. Room metadata could change before the image finished transitioning, so story completion now also checks the captured scene. A first continuous replay reached the guard but stopped outside talking range; the corrected approach checks that the conversation opens. Navigation uses short position-guided moves and checks each doorway. Dialogue uses stable screen observations instead of holding confirm through the entire scene.

Demonstrations retain their original unrated labels. Independent autonomous runs are saved separately. Genuine gameplay checkpoints were restored through the normal confirmed snapshot loader; no cheats or edited winning state were used. This training evidence is separate from the prior statue-save download/reopen test.

Watch or take over

Choose Continue Duran’s story after Bruiser in the bot task list at the victory checkpoint, then Watch bot play. The combined Duran opening task first runs the existing Bruiser duel controller and chains into the same story route after a win. Pause bot ends a run and releases controls; restore the starting checkpoint to restart. Take over returns player control.

Only the listed starting scenes and trained routes are supported. Full campaign, arbitrary goals, outdoor exploration, inventory management, later bosses and cross-game play remain development goals. This is an authored controller informed by gameplay data, with no external model service.

Download source and training data · Coverage and acceptance

Damage variation and caption readiness

The first public 0.4 replay reached the intruder, then stopped on a genuine 7 HP spell outcome because its check expected exactly 8. Version 0.4.1 allows 1–16 HP only within this required-loss encounter and still requires the expected council scene before advancing. Ordinary combat health guards remain in place. A separate trial starts from the unchanged public 7 HP checkpoint.

A fresh opening run also showed that confirming a still-typing surrender line can merely finish that line. The bot now waits before confirming it. Passing autonomous runs, stopped attempts and original unrated demonstrations are preserved separately in the source package.