Skip to content

Handle Guitar Hero band-name setup in V6 - #143

Merged
ProhibitedTV merged 5 commits into
mainfrom
fix/guitar-hero-band-name-v6
Sep 6, 2026
Merged

ProhibitedTV merged 5 commits into
mainfrom
fix/guitar-hero-band-name-v6

Conversation

@ProhibitedTV

Copy link
Copy Markdown
Owner

Live failure

The next retained GH1 run successfully left USING THE GUITAR CONTROLLER, but stopped on the real NAME YOUR BAND / save-name card. The console continued reporting controller-tutorial retries even though the screen explicitly says PRESS START BUTTON TO ACCEPT NAME AND CONTINUE.

The cause is a second first-run-card collision: NAME YOUR BAND has the same broad pale/green paper, dark headline text, and green action badge that V3's tutorial detector uses. V5 therefore kept tutorial ownership after the visual transition and exhausted its confirm -> L2 -> confirm budget instead of pressing Start.

V6 fix

  • add dedicated structural ownership for the NAME YOUR BAND card before the inherited tutorial path
  • distinguish it with the two-button footer: green NEXT plus adjacent red DELETE, combined with the paper/title topology
  • explicitly revoke any stale controller-tutorial latch when the band-name card is recognized
  • press virtual Start to accept the default band/save name, matching the instruction printed on the retained live screen
  • use bounded Start retries and a quiet transition-grace window
  • suppress the broader tutorial detector for strong-but-partial band-name evidence so filtering cannot hand ownership back to V5
  • expose band-name score/active/attempt/input telemetry
  • activate GuitarHeroV6Profile in the registry and package alias

Regression coverage

Adds tests proving that a band-name-like card can satisfy the old tutorial detector yet V6 preempts it and sends only Start; Start retries remain bounded; a real tutorial topology without the red DELETE badge still uses V5's corrected Confirm/Cross path; telemetry and registry aliases report V6.

Evidence boundary

This fixes the exact retained first-run blocker shown in the latest live capture. Guitar Hero remains diagnostic until the remaining main-menu -> setlist -> difficulty -> highway -> results lifecycle is proven end to end.

@ProhibitedTV
ProhibitedTV merged commit 8c824c8 into main Sep 6, 2026
2 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7574a86145

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +129 to +131
band_score = self._band_name_evidence(ctx)
if band_score >= self.band_name_tutorial_guard_threshold:
return 0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep partial band-name evidence under safe ownership

When a filtered NAME YOUR BAND frame scores between the default guard (0.55) and ownership threshold (0.70), this returns zero tutorial evidence without claiming the screen itself. After any 0.75-second band-name transition grace expires, tick() delegates to V2; if the frame has presentation-level motion, V2 waits indefinitely, and otherwise its unrelated boot/menu classifiers may act. Thus the exact partial-evidence case described here can still fail to send Start and recreate the first-run blocker; the guard range should retain input-silent band-name ownership or otherwise route into the bounded Start path.

Useful? React with 👍 / 👎.

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