Since the movie contents are very similar to the published Pokémon Crystal movie, this movie is going to obsolete it. Anyway, please remember to avoid wiping the save data for future submissions, unless that is required for performing a faster glitch. Though, this isn't always the case, as rules may change and judgement precedents may not always reflect them when in doubt, always ask directly to the judges. Additionally, the previous publications are also making use of this in-game feature, so it's understandable that the author decided to follow the trend set by movies that have been accepted in the past, in order to make sure that the new submission would comply with the rules. However, the time lost is not considered as suboptimal play, but rather as a personal choice from the author. Additionally, this movie does also write a proper save file once, before performing the save glitch, so there wouldn't be much of controversial even if we wanted to see it that way. For this reason, it shouldn't be considered as a requirement to wipe the save data by using in-game functionalities, like this movie does. After some discussion with the other judges, as well as the precedent set with this submission, we decided that using glitches that are affected by uninitialized SRAM bytes is considered fair. There is just one special note I need to make. ThunderAxe31: All right, the movie looks optimized and it correctly beats the game. Auto input takes over after ACE, going down and pressing A through Red's textboxes.
Type 0xD0 is viewed and manipulated to place the player's name at the right spot for ACE to happen.Boxes 4 and 5 are named for the initial ACE payload.This also happens to make autoinput taken from 00:0000 to work, so all I need to do is enable autoinput and it'll just work. Silver (and in front of Red) and I move myself next to the map connection, so taking 1 step down triggers it. Instead of creating a warp, I just change the map connection so it goes to Mt. Here is a paste of the tracelog and the values set from the input to opcode payload: To note, movie does something a bit differently to get to Mt. Loop back to right before Box 4 carry will never be set Write difference will be executed as opcode later in the next cycleĮxecute opcode written earlier this cycle There were some minor modifications done to work around character limitations.ĭ stores last joypad input: find out differences to current input
This uses yet again MrWint's box code for input to opcode.