Skip to content

[BUGFIX] Don't dispatch conductor events if substate is active#6886

Open
KoloInDaCrib wants to merge 1 commit intoFunkinCrew:developfrom
KoloInDaCrib:dont-scare-me-like-that-brah
Open

[BUGFIX] Don't dispatch conductor events if substate is active#6886
KoloInDaCrib wants to merge 1 commit intoFunkinCrew:developfrom
KoloInDaCrib:dont-scare-me-like-that-brah

Conversation

@KoloInDaCrib
Copy link
Contributor

Linked Issues

Nope.

Description

When in a SubState, for example after dying in PlayState, the callbacks beatHit and stepHit of the parent state are still attached to the same Conductor instance and get dispatched. This leads to a weird effect where if you die in the week 2 stage, lightning can still strike.
This PR fixes it by checking if the parent state has a substate attached to it and if it can update with it attached before dispatching the conductor callbacks.

Screenshots/Videos

image The trace was added manually to the script and doesn't exist in the original file.

@github-actions github-actions bot added status: pending triage Awaiting review. size: small A small pull request with 10 or fewer changes. pr: haxe PR modifies game code. and removed size: small A small pull request with 10 or fewer changes. labels Feb 5, 2026
@Hundrec Hundrec added type: minor bug Involves a minor bug or issue. size: small A small pull request with 10 or fewer changes. labels Feb 6, 2026
@Hundrec Hundrec changed the title dont dispatch conductor events if substate is active [BUGFIX] Don't dispatch conductor events if substate is active Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: haxe PR modifies game code. size: small A small pull request with 10 or fewer changes. status: pending triage Awaiting review. type: minor bug Involves a minor bug or issue.

Development

Successfully merging this pull request may close these issues.

2 participants

Comments