Show tutorial prompts as pad arrows in one centered cue #13
+46
−73
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The cabinet input is a dance pad, so a prompt like "A" or "J" names a key no player can see, and the same lesson looked different depending on which player was taking it. The cue for advancing dialogue was also a small chip in the bottom right, while the cue for the next move was large and centered right above it. TutorialInputLabels now exposes fixed pad glyphs for left, right, and place. This is display only: bindings and remapping still live in InputSystem_Actions, and the tutorial keeps routing input through the active player's action map, so Player 2 still plays on the Player2 map. TutorialController.SetContinueVisible shows the place glyph in the large centered BindingLabel and keeps the bottom-right ContinuePrompt hidden, so a dialogue step and a move step prompt in the same place at the same size. The chip stays in the hierarchy and in TutorialUILayout, so the authored scene and the guide style asset need no changes. Wrong-direction hints in TutorialLessonConfig are built from the same glyph constants rather than repeating the arrows, and DefaultTutorialLesson.asset carries the matching text for the lesson that actually ships. Docs: Tutorial.md 0.6.0 to 0.6.1 with the new right-panel behavior, COMPONENT_INDEX version bump, and a CHANGELOG entry noting that this supersedes the per-player key hints for direction cues. Co-authored-by: Cursor <cursoragent@cursor.com>
Sign in
to join this conversation on GitHub.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The cabinet input is a dance pad, so a prompt like "A" or "J" names a key no player can see, and the same lesson looked different depending on which player was taking it. The cue for advancing dialogue was also a small chip in the bottom right, while the cue for the next move was large and centered right above it.
TutorialInputLabels now exposes fixed pad glyphs for left, right, and place. This is display only: bindings and remapping still live in InputSystem_Actions, and the tutorial keeps routing input through the active player's action map, so Player 2 still plays on the Player2 map.
TutorialController.SetContinueVisible shows the place glyph in the large centered BindingLabel and keeps the bottom-right ContinuePrompt hidden, so a dialogue step and a move step prompt in the same place at the same size. The chip stays in the hierarchy and in TutorialUILayout, so the authored scene and the guide style asset need no changes.
Wrong-direction hints in TutorialLessonConfig are built from the same glyph constants rather than repeating the arrows, and DefaultTutorialLesson.asset carries the matching text for the lesson that actually ships.
Docs: Tutorial.md 0.6.0 to 0.6.1 with the new right-panel behavior, COMPONENT_INDEX version bump, and a CHANGELOG entry noting that this supersedes the per-player key hints for direction cues.