fix: checkQTE guard against stale scene closures
Since onTimeUpdate callbacks are now additive (Set), goToScene closures for old scenes persist. Add currentScene?.id !== scene.id check to prevent QTE from re-triggering for past scenes after scene transitions.
This commit is contained in:
@@ -85,6 +85,7 @@ export class Engine {
|
|||||||
}
|
}
|
||||||
|
|
||||||
private checkQTE(scene: SceneNode, time: number) {
|
private checkQTE(scene: SceneNode, time: number) {
|
||||||
|
if (this.currentScene?.id !== scene.id) return
|
||||||
if (!scene.qte || this.qteTriggered) return
|
if (!scene.qte || this.qteTriggered) return
|
||||||
if (time >= scene.qte.triggerTime) {
|
if (time >= scene.qte.triggerTime) {
|
||||||
this.qteTriggered = true
|
this.qteTriggered = true
|
||||||
|
|||||||
Reference in New Issue
Block a user