[Open Assets] Chronotron v1.2

What permissions do you give others to modify and/or maintain your submission?
Modify: YES - Maintain: YES - I give permission for my entire submission to be modified by others or used in their own work. I give permission for my entire submission to be maintained by others as well.
* Requires SRB2 2.2.13 or higher.
* Probably also requires good memory/RAM on your PC
* You may experience minor jittering when playing above 35 FPS. Players with epilepsy should take caution.

The Chronotron is a majestic device of ambiguous appearance. It can do a lot of things, but its defining feature is the ability to record all of your past attempts and play them back in the present.


If you ever need to review these, most of them are in the F1 menu in-game.
The Chronotron can record past attempts and play them back in the present as clones of yourself. For the sake of simplicity, they are officially named "iterations".

Iterations only appear after you die and respawn. You can't interact with them, and all of their movements and actions are based on the world they were in. For example, if you recorded an iteration jumping onto a platform, and then the platform is gone when you respawn, the iteration will stand in the air as if the platform were still there.

You are constantly recording a new iteration, from the instant you step foot in a map. When you die and respawn, you start recording the next iteration right away, while previous iterations play out before you.

Want to review a specific iteration but don't want to be cluttered by having to follow it? Use the command chrono_relive to "relive" past iterations and view their movements from their camera perspective.

Want to clear out the iterations you already have? Well, your iterations are cleared automatically when you move between maps, but if you want to do it right here right now, use chrono_erase! Note that you'll restart at the last checkpoint you hit if you use it...
Invalidated iterations are iterations the Chronotron doesn't consider to be legitimate. They aren't recorded or saved, essentially being erased once you die. Dying in an invalid iteration doesn't move you to the next iteration, it just revalidates the current one. Invalid iterations cannot place events on the Timeline.
Stuck in a rut, got bored with how things are going, or just want to move on to the next iteration already? Holding Toss Flag will allow you to, well, self-destruct. Self-destructing is basically the same as dying, save for a slightly different event appearing on the Timeline.
The Timeline is a bar at the bottom of the screen that details things you and/or your iterations are doing. It tracks most things, with more to be added in the future, but here are some things I know for a fact that it tracks:
  • Iterations dying (through SELF-DESTRUCTing or other means)
  • Going Super
  • Losing Super
  • 1-minute intervals up to 10 minutes
  • When the drowning timer starts (and how it ends)
  • Bosses fucking dying
Don't like how it looks? Use chrono_timeline to turn it off or on, or instead use chrono_timeline_simple to switch to a more compact version.
If you want the timeline to move faster, use chrono_timescale, though keep in mind this will also speed up the iterations, to prevent desynchronization.
When an iteration reaches the point where it dies, it will leave behind a Chronoblock. Chronoblocks are small, grey stone blocks that you can use to sorta hoist yourself to other places. They can't stack, but in certain situations, the tiny boost of height they give can be pretty useful.

Just try not to get caught underneath one during the initial fall... If you don't want to worry about Chronoblocks potentially ruining your day, use chrono_blocks to turn 'em off.
chrono_timescale - Adjusts the speed of the Timeline and of iterations. There are 6 values: Stopped, Quarter, Half, Normal, Double, and Triple. Any value other than Normal will invalidate an iteration.

chrono_indicators - Toggles the orange indicators appearing over iterations' heads.

chrono_blocks - Toggles the appearance of Chronoblocks when iterations die.

chrono_timeline - Toggles the Timeline appearing onscreen.

chrono_timeline_simple - Toggles the Timeline's compacted appearance.

chrono_relive - Allows you to view an individual iteration. Certain iterations cannot be viewed.

chrono_erase - Erases all iterations and has you restart from the last checkpoint/the beginning of the stage, at iteration 1.
  • You can't relive iterations that start from checkpoints. Obsolete as of v1.1
  • When reliving iterations, camera bugs out if iteration goes firstperson. Obsolete as of v1.2
Ghost rendering code: Bloops' Tape Recorder
Extension type
File size
867.3 KB
MD5 Hash
First release
Last update
5.00 star(s) 5 ratings

More resources from LionOte

Share this resource

Latest updates

  1. The Second Update That I Couldn't Think Of A Cool Name For

    v1.2 Changelog Added a new command: chrono_erase: Erases all of your recorded iterations and...
  2. All Iterations Are Now Relivable! Hopefully!

    v1.1 Changelog * A few more sounds should be tracked * You can now relive iterations that start...

Latest reviews

This is brilliant
I actually unironically look forward to dying with this addon enabled, and find entertainment watching my previous attempts play out and seeing the silly ways they die or the unintentional feats I did in the past unfold in a different perspective

The only things I can really suggest is making the addon save your settings for it (Tiresome having to disable the things I don't want every time I use it)
And perhaps make the player's ghosts transparent. Having a lot of them around can make it a little hard to see past'em.

Also, this DOESN'T require a lot of RAM. I play SRB2 on a toaster of a laptop, and the mod's given me zero problems with performance, even when I had like 32 ghosts in a level.

Edit: Oh yeah. When reliving an iteration, if the iteration happens to switch to firstperson, the camera breaks and just remains where the iteration stood at the point of switching perspective
I think I've fixed the issues you talked about. Thanks for letting me know!

Also, the RAM thing was because the script has to store the individual data for each frame of each iteration, and I thought that would quickly become a huge amount of data to store. Thanks for clarifying!
Upvote 0
Combining this with a hardcore map would be very interesting
Upvote 0
very cool but i wish there was a option to stop a attempt without dieing
Upvote 0
this takes me WAY back to coolmath games, thanks for making this
Upvote 0
I love the chronotron flash game so much I love making my army of clones have an insane dance party literally peak srb2 modding
Upvote 0