Teleporting more than I'm not sure ~1500 ticks? into a recording leads to internal server stopping and a crash.

Thanks for the screenshot of the dirt background. Can you post your crash log maybe? And don't post a screenshot of it.

Oh! My bad lol
Here you go:

crash-2023-08-01_12.36.48-client.txt

Thanks, I will have a look at it

After a bit of testing, I've found that the issue in my specific case has something to do with loading chunks that were unloaded after having stopped recording the actor's path and been teleported back. But even if I do successfully teleport at cursor and record from cursor (don't load unloaded chunks during recording), the recording starts from the starting position of the actor's path from the recording that came before recording from cursor. Additionally, other actors that had actions recorded happening at the same time as the actor being recorded to don't play during the recording of the actor being affected by the "record from cursor" function. This makes timing actions that must happen on specific ticks difficult because the other actors can't be seen during recording.