Order of lua cutscene execution is confusing

[late trail]

I'm asking this for someone else but apparently this executes in the following order:

1. Disables movement (ok)
2. zoom
3. offset

Which seems not correct, any reason this could be happening?

apparently setting offset to 100 also locks the camera and it stops moving

and "removing the -10 it does the zoom then offsets +10"

(apparently +10 also locks the acmera)

so they aer trying to zoom to this point and it just kinda doesn't work? (it's in the room)
that's like the basic issue of this cutscene

[cinder wave]

isn't it supposed to run like that?

player.ForceCameraUpdate = true;

[cinder wave]

this constantly updates the camera

also im psure you have to have "local engine = require("#monocle.engine")" at the top of the file

[slate narwhal]

Would i put this at the top of the file ?

[cinder wave]

yes

?

wait

only near the camera thing?

or just in a function

[slate narwhal]

Ok

[cinder wave]

set the offset back to 0,0

[slate narwhal]

Right it’s a set not a yeah

I’m stupid

[cinder wave]

(technically you can put this anywhere as long as its before you use engine.scene but it works well in the global tray)

[slate narwhal]

Yeah it works now

Tysm

[cinder wave]

also lua cutscene works pog

(i don't think anyone knows how it works)