This is a collection of GD TAS runs. You can click the table headers to sort. Click on macro to get more information.
Macros not from the latest update are probably broken, but kept here for history.
Please DO NOT run these on the actual levels, make a copy/use safe mode so your time doesn't save on the leaderboard.
This website is made for TAS runs, not showcases. Showcases are meant to model how a human might play a level, and show it off in a straightforward way. TAS runs need a superhuman (or close to superhuman) level of play, and they save time wherever possible to create an "almost perfect" completion.
For a run to be added here, it must fulfill these criteria:
Platformer: The run must be faster than the world record of the level, and not contain any major mistakes.
Classic: The run must either save time somewhere in the level via a skip, OR show off swag routes in the level that are very hard/impossible for a human to perform.
The run must have a working macro file in either .ybot or .gdr format. A video is preferred, but not recommended.
FAQ
What is TAS?
Basically, using botting tools trying to push GD levels to their theoretical limit in order to create a hypothetical speedrun that goes as fast as possible, and/or does otherwise humanly impossible tricks. See Wikipedia for more info.
Why are classic levels here?
Many classic levels have big timesaves in the run due to skipping speed portals or just cool tricks to show off, and there is a subgroup of the GD speedrunning community that runs these levels.
Why not convert all the replays to both bots?
Because kepe, the creator of ybot, made the ybot to plaintext converter (which I need to convert from ybot to gdr) an exe program you have to run, I can't convert on the website via code. I have to do each macro manually, which takes a long time. I'm not willing to go through 60 old macros and convert them all at the moment, so if you want just one converted, just DM me (shadowyzephyr on discord) and I'll see if I can do it that day.
A macro I downloaded broke, why?
Here are some reasons this could happen:
If the macro is not from the most recent version (2.204), it is almost certainly broken. I am keeping those here for history of what time was possible on a level, but they will probably be removed eventually.
Bots don't always playback the first frame of input into a level, what you start off holding. This can cause issues where you need to hold left or right while entering the level, or use frame stepper to pause the level on frame 0, and then hold left or right. It's especially finnicky with MegaHack. If the macro has an alignment issue, it should be in the description of that macro, but it's possible that I made a mistake or forgot to write that in.
The contributor who submitted it to me submitted a broken macro and I didn't notice (if that happens and it comes to my attention I will remove it)
Why can't I get the infobox for macros on mobile?
Just because of the way I made the website. I'll probably fix this later.
I want you/a contributor to make a TAS of a level, how can I request one?
If you want me to TAS a level, either DM me on discord (shadowyzephyr) or request one here. If you're looking for macros of levels, you may want to join the GD TAS, Mega Hack, yBot, or Macro Sharing Plaza servers.
How do I create a Geometry Dash TAS?
First, you will need to choose a bot. xdbot is free (requires Geode), but can't be used for true platformer TAS runs because the frame fix option changes the physics of the game. It's still a good option for estimating the time of a level, though. The other two bots, yBot and MegaHack, each cost money, and have different pros/cons.
yBot
MegaHack Replay
Most accurate (almost 100% accuracy)
Has Show Trajectory and autoclicker in the pro version.
Automatically saves recording while you're making it
Unstable, prone to crashing (crashes a lot more if you don't have 4gb patch)
Doesn't show precise X/Y position and velocity
Doesn't work with Geode/MegaHack
Doesn't handle RNG/random triggers (you need to make a copy of the level and edit the triggers yourself)
SFX is disabled (if you have both you can record in ybot, convert to megahack and replay it there to get around this)
Shows precise X/Y position, velocity, and has the option to show triggers
Integrated with Geode and MegaHack
Open .gdr and .gdr.json format
Handles RNG/random triggers
Requires manual saving of recorded macros
Macros often break, especially on harder levels
Has some bugs that make it more annoying to bot with
Alex has a good tutorial on TAS (he is using ybot) here.
If you're worried about the SFX being disabled for playing regular GD, you can install ybot on a separate GD executable. Here's how to do this:
1. Copy your Geometry Dash folder from C:/Program Files (x86)/Steam/steamapps/common into another directory, like Desktop.
2. In that folder, rename the application GeometryDash.exe to something else.
3. Add a file in the new GD folder called "steam_appid.txt" with the content just being the number '322170'. (no quotes, no period)
4. Install yBot (or whatever you want) in that folder.
Some GD TAS tips:
Always keep show hitboxes on. There is no reason not to have it on, unless it's crashing your game, and it's a useful tool.
Learn to use frame stepper to your advantage. I would also recommend speedhack, but that comes down to personal preference.
Try to keep as much momentum toward your goal as possible, whether it be getting as far to the right or as far up as possible. Don't bonk on platforms sideways unless you want to slow down, hit your head on platforms strategically to fall faster if necessary, and hold for as long or as little as possible, whatever will maximize your momentum.
Usually, turning around by not pressing anything for many frames to slow down is quicker than just switching from right to left or vice versa. If you're using megahack replay, you can see the X velocity. Generally, you want to stop holding, and start holding in the reverse direction once the difference in X velocity between frames is less than 0.18.
The cube jumps slightly higher on the second or later jump while holding the button down. If you want to land faster, wait until the frame that you see particles from landing and then click again. The ball goes down slightly faster if you wait for particles.
Orbs set your Y velocity to a constant number. They have no cooldown in platformer, so it may be useful at times to spam them. The same applies to UFO jumps (spam them if you need to go up!)
There is a bug with the robot in platformer: if you jump into an orb, keep holding down the input you used, and then when you get to the orb, press another input instead of letting go of the first one (for example, jumping with up arrow and then holding space for the orb), you will jump much higher. This can be abused in some levels.