Augury Red Code is a short speedrun based puzzle platformer. You play as a female android called C-1 as you platform your way out of ALS Tech Facility. Open locked doors and eliminate monster creatures known as BUGS to pave your path to the exit with the lowest time possible.

C-1 uses a scythe as her weapon. She can attack with it when it's equipped, and throw it to be used as a platform. She cannot attack while the weapon is thrown, as she needs to recall it first to do so.

C-1 has a bug in her system that poorly detects when the scythe has been thrown, but cannot be recalled. This can be fixed by using the SYSTEM RESET function, resetting the room with the scythe in hand.

C-1's speed instantly goes to 400 in 1 frame, and then increases by 300 each frame until it caps at 2500. However, when the scythe is thrown and stops moving, her speed cap increases to 3900. This speed cap is lowered again when the scythe returns to C-1. This is a 56% speed increase, so she tries to keep the scythe out for as long as possible.

The main glitch this run uses is the "early scythe stop". Normally, the scythe will only stop when it hits a wall or spikes. But she can stop it earlier by facing right on one frame, left on the first/third frame the scythe leaves, then right on the next frame, or vice versa. This way she can get the speed boost without waiting for it to reach a wall. It's also useful to get the scythe's collision directly under her.

The bug that prevents the scythe from being thrown is avoided entirely by recalling it the frame that she enter a door transition. This 1-2 frame loss is better than the 36 extra frames needed to sysreset. It's better to do it this way than run into a door with it still on the wall. The game recalls it automatically, however there is extra wait time this way (and you might have to sysreset after entering the next room anyway).

Better scythe management, a potential cutscene skip.

Frame 2184

DrD2k9: Claiming for judging.

DrD2k9: Firstly, sorry it took me so long to get to this. Secondly, the run had a few areas that looked slow to me upon first watching through. Just by more efficiently using the already known speed tech which was mentioned in the submission notes, I was able to improve the second and third rooms by 32 and 27 frames respectively for a total of 59 frames over the first three rooms. Even these improvements may not be optimal as I didn't spend a ton of time on it. I'm guessing that remaining rooms may be improvable as well. Unfortunately, I don't currently have time to dig further into this game myself. I'd encourage inconsistent to revisit this run and submit a more optimized full run in the future. Feel free to use my improvements, but don't take them as optimal; they maybe improvable yet.

Rejecting.