Skip to content

Allow different cutscenes to play at the same time#1107

Merged
SnipUndercover merged 2 commits into
EverestAPI:devfrom
maddie480:finally-fix-999-mayhaps
May 12, 2026
Merged

Allow different cutscenes to play at the same time#1107
SnipUndercover merged 2 commits into
EverestAPI:devfrom
maddie480:finally-fix-999-mayhaps

Conversation

@maddie480
Copy link
Copy Markdown
Member

The whole reason why #999 is held in beta since forever (4 months? wow) is that triggering multiple cutscenes at once was used... by TASers I think? The compromise is to block triggering of the cutscene if a duplicate of it (as in, the same dialog, unless I missed something) is already running, not if any cutscene is running.

@maddie480-bot maddie480-bot added the 1: review needed This PR needs 2 approvals to be merged (bot-managed) label Apr 7, 2026
@maddie480 maddie480 force-pushed the finally-fix-999-mayhaps branch from a69cdbb to d0ce85a Compare April 12, 2026 14:11
@maddie480
Copy link
Copy Markdown
Member Author

Branch updated to include the restoration of PR #999 as a separate commit

Copy link
Copy Markdown
Member

@microlith57 microlith57 left a comment

Choose a reason for hiding this comment

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

cool! please inform lönn team about the new fields ^_^

Comment on lines +49 to -29
if (Scene is not Level level)
return;

if (triggered)
return;

if (deathCount >= 0 && level.Session.DeathsInCurrentLevel != deathCount)
return;

if (ignoreIntroState && ((patch_Player) player).IsIntroState)
return;

// don't activate if the same dialog is already in progress
if (DialogCutscene.IsInProgress(dialogEntry))
return;
}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

praise: very nice, clean guard chain

@maddie480-bot
Copy link
Copy Markdown
Member

The pull request was approved and entered the 3-day last-call window.
If no further reviews happen, it will end on May 12, 2026, 12:05 AM UTC, after which the pull request will be able to be merged.

@maddie480-bot maddie480-bot added 3: last call window This PR was approved, and is in the 5-day last-call window before getting merged (bot-managed) and removed 1: review needed This PR needs 2 approvals to be merged (bot-managed) labels May 9, 2026
@maddie480-bot
Copy link
Copy Markdown
Member

The last-call window for this pull request ended. It can now be merged if no blockers were brought up.

@maddie480-bot maddie480-bot added 4: ready to merge This PR was approved and the last-call window is over (bot-managed) and removed 3: last call window This PR was approved, and is in the 5-day last-call window before getting merged (bot-managed) labels May 12, 2026
@SnipUndercover SnipUndercover merged commit bf0adbf into EverestAPI:dev May 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4: ready to merge This PR was approved and the last-call window is over (bot-managed)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants