#Agdq 2017 game list code

This is the most representative demonstration of Robotrek speedrunning I can imagine. Sub-3:20 is definitely possible (probably even a 3:15 or so, given enough time and good enough luck), but IвЂ™m happy with this run. I spent several months in late 2018 reverse-engineering the gameвЂ™s mechanics and did a super aggressive reroute to cut out the crab grab. This Robotrek category is technically single-segment we do not allow resets due to the impact it has on RNG. I believe the SRC page is updated regularly, so I would recommend checking there. There are several other runners, but I am not terribly involved with this community anymore so I donвЂ™t know who is active. The current best time is a whopping 32:29 by mmmmalcome, but dice_ta is very close behind! Other runners: For your daily dose of SGnG content, I highly recommend the two top Japanese runners, mmmmalcome and dice_ta! They have been grinding this game daily for YEARS. I will not be returning to runs of this game, due to ongoing harassment stemming from rumormongers. Even by 2014 standards, this run was 2 minutes slower than вЂњgoodвЂќ. This run is the result of that very, very short grind. After spending close to 2 years routing this game with every weapon from scratch, and spending several months running this game with the torch without finishing a single run, I decided to spend a week using the dagger just to improve the existing runs. For additional reading, I would recommend reading the TAS submission notes and TAS discussion thread.Дagger run.

#Agdq 2017 game list code

Khaz dumped a perfect map from the gameвЂ™s code in addition to sharing some optimizations, glitches, and route considerations and making an incredible GMC TAS of this game. There are no other real-time runners of this game, but I need to give a special shoutout to Omnigamer for looking into the glitch at my request and providing me with loads of fun info, and to Khaz, the TASer.

This run was done in real time, single-segment, on console.

The outcome of the crazy nonsense is dependent on the values of every single byte in RAM, and usually crashes the game in super rare circumstances, it will call the credits. If the player doesnвЂ™t reset the game at some point after killing the first boss, the Grand Memory Clobber will do all kinds of crazy nonsense when you reach the dragon cutscene in Ortah. The Grand Memory Clobber is a glitch in Dragon View resulting from uncleared memory that is set after killing the first boss of the game.