(Link to video)
Submission Text Full Submission Page Publication Page

Categories

  • 100% completion
  • Heavy luck manipulation
  • Forgoes save data corruption
  • Corrupts memory
  • Major skip glitch
  • Heavy glitch abuse

Game Objectives

  • Emulator used: BizHawk 2.2.2
  • Aims for fastest completion time.
  • Catches all 151 Pokémon as quickly as possible.
  • ...like, really, really quickly.
  • Does not modify Pokédex flags
  • Does not use arbitrary code execution.
  • Is really boring.

About the run

Some terms or concepts used in the TAS (such as Cooltrainer) have been explained in the previous submission by MrWint. The justification for platform choice and version choice, and explanation of luck manipulation are mostly the same as the current "warp glitch" submission by gifvex, except that Blue version is used over Red version as it manipulates the required trainer ID faster than Red version, factoring in time lost from Blue version's slower preset player name.

Intro

  • Soft reset is pressed 15 times. 16 inputs are required to perform a soft reset and each delays 1 frame. The delays are used to manipulate the trainer ID and allow a soft reset later with just 1 input.
  • A trainer ID of 0xbe05 is manipulated. The bytes are aligned in memory in the expanded item pack where 0xbe is the quantity of some Master Balls and 0x05 is a Town Map item.
  • The player is named the preset BLUE name. The name does not appear enough times before fastest text speed (0 frames per character) is acquired to be worth naming 1 character.
  • The rival is named ",./xox". Each pair of characters corresponds to an item and its quantity in the expanded item pack. The items are TM44 x242, TM43 x183, and BLUE x183. TM44 x242 is merely filler to reduce lag caused by glitched item names, but the TM43 item and BLUE x183 are necessary for the main farming glitch.

Pallet Town

  • Charmander is chosen as the starter Pokemon. DVs (values used to calculate stats) of exactly 0x1024 are manipulated. Charmander has a fast battle for both rival and Weedle.
  • The rival battle is lost because the rewards are not needed. Four 1/256 growl fails from Charmander and three 1/39 damage roll Tackles (+ one non-1/39) from Squirtle are manipulated.
  • Battle animation is ON and saves 30 frames over OFF. The Poke Ball animation costs 10 frames, but each Tackle animation saves 10 frames over a fixed delay when animations are off.

Viridian Forest

  • Options are set in the gate before the forest. Menu speed varies by map and the gate is the best available before Weedle. The menu also skips a 2 frame delay in movement.
  • Weedle is defeated with a combination of four 1/39 damage rolls and four critical hits. Charmander wins the battle with 40/40 Growl PP and 30/35 Scratch PP in order.
  • The cursor is moved to SAVE now because directional inputs are disabled later.

Pewter City

  • An antidote was picked up in Viridian Forest and 5 more items are bought to reach 6 items. Three Poke Balls are used to catch Pokemon and an Escape Rope ends up in slot 6.
  • A trigger causes dialogue with the Brock fan, but the start menu is able to be buffered before the cutscene movement begins. The game is saved and soft reset.
  • After more dialogue, movement is able to be buffered before the trigger catches the player again, and allows the player to pass the Brock Fan before Brock is defeated.
  • The Brock Fan is talked to from the right and invalid cutscene movement data is read that enables walk through walls. The game attempts to find the player's coordinates in memory and load the appropriate data, but (y:16, x:36) is not defined by the game. It finds 0x1024 in Charmander's DVs and loads data from 0x1E28 due to Charmander's move PP.

Cerulean Cave

  • A Ditto is caught and swapped to slot 1. When a transformed Pokemon swaps its first move with a slot it does not have, it will swap move ID 0x00 into the first slot, known as "Cooltrainer".
  • Cooltrainer's invalid name can cause a buffer overflow that copies saved screen data over enemy Pokemon data. This is done to turn a wild Pokemon into MissingNo. and catch it using the screen data saved when opening the party menu. The buffer overflow also sets an audio fade-out value that causes MissingNo.'s Pokedex jingle to be skipped.
  • MissingNo.'s invalid seen flag sets bit 7 of the item quantity in slot 6. The Escape Ropes went from a quantity of 1 to a quantity of 129 and 2 are tossed to unset bit 7.
  • MissingNo.'s Pokedex entry never unsets the flag to flip sprites horizontally. This affects Cooltrainer, so Ditto's summary is viewed because the page unsets the flag.
  • Cooltrainer is activated again with screen data saved when opening the item menu. This MissingNo. catch sets bit 7 again and the Escape Ropes now have a quantity of 255.

Obtaining Item Underflow

Note that the remaining sections make heavy use of the pokered disassembly labels. Each time a new label is mentioned or referenced much later than previous references, the address in square brackets will be listed next to it.
  • Item Underflow is obtained via the "Dry Underflow" method. Escape Rope x43 is created as a side effect to save a quantity toss later.
  • The Use/Toss Menu is brought up to fix the item menu's cursor bounds (set to 1 during Item Underflow), which is currently set so that the cursor can move to at most the second item before scrolling the menu. Not resetting this value would cause the game to render more of item 0x00 (referred to as []j.) which the name lookup causes enough lag to be slower than bringing up the Use/Toss Menu.
  • Escape Rope x43 is swapped into the 9th slot. The 43 (0x2b) represents the lower byte of a pointer used for the main farming glitch.
  • The []j. item below is swapped with a TM43 in the Rival Name Underflow memory section. This forms the pointer 0xf32b, which points to the quantity of the third and last 0xff item (CANCEL).
  • The Options item ([]j. x129) is swapped with the Palette item (Old Amber x0), setting the delay between printing letters to zero.
  • One Master Ball is tossed from Master Ball x3, setting the Last Outside Map warp location to 2, the internal ID of Pewter City.
  • Full Restore x77 is swapped with item 0x7d to reduce lag later on. Item 0x7d belongs to a family of items known as TMTRAINER items, which their names are not properly terminated and read from a backup of the screen tiles, causing considerable lag.
  • []j. x255 is swapped with Moon Stone x10. This sets the source of the value copied to wWalkCounter [0xcfc5] to 0 during the buffer overflow used in the main farming glitch.
  • []j. x1 is tossed from the []j. x255 stack so that the buffer overflow, terminated by 0xff, does not end prematurely.
  • An HM03 is swapped with item 0x9e (4 8 4 8). This does two things: preserves an HM03 for later to be swapped with an unavoidable HM03 x255 that appears when warping to Pewter City, and removes an undesirable TMTRAINER item which would have to be swapped out later anyway to avoid generating lag during the main farming glitch.
  • A Master Ball x4 is swapped out from the game's warp entries and placed in a location that would cause the internal ID of Master Ball (0x01) to be copied to wIsInBattle [0xd057] during the main farming glitch.
  • []j. x1 is tossed from a []j. x0 (corresponding to wEnemyBattleStatus3 [0xd069] for the buffer overflow) to get []j. x255, which sets the end terminator of the buffer overflow.
  • The inventory is wrapped around to reach the start of the inventory, which happens due to the game using 8-bit addition to determine offsets for scrolling menus. Tossing a []j. x0 to reset the cursor to the start of the inventory was found to be slower due to additional lookups of the []j.'s item name.
  • CANCEL x2 is tossed from the third CANCEL's quantity to set it to 0xfe, representing a mart for the game's text ID engine.
  • Exiting Cerulean Cave wrong warps us to Pewter City.
  • Escape Rope x255 is swapped into the map's text pointer. Escape Rope x12 is tossed from Escape Rope x255, giving us Escape Rope x243 which points to 0xf31d.
  • Town Map x255 is swapped with the Town Map generated from the trainer ID to get rid of the 0xff quantity value.
  • The Current Map item is swapped with item 0xae (BLUE), corresponding to Indigo Plateau's Pokémon Center. This allows us to access a PC to change boxes during the main farming glitch, while not generating 0xff bytes upon loading a new map due to a lack of South and East Connections. If the setup was done in an indoor map with no connections, then we would have to toss CANCEL items which is slower as it resets the inventory to the top of the menu.
  • Master Ball x190 (quantity generated from TID) is swapped with Town Map (item ID generated from TID). The item ID of Master Ball corresponds to flags handling print delays, which the whole value requires bit 0 set and bit 1 reset for faster text delay. If bit 0 is reset, then text is forced to display at one frame per character, while if bit 1 is set, then text placed through the "text string" engine (e.g. PC menu options) would be delayed.
  • Master Ball x190 is swapped into a location where its quantity corresponds to wEnemyMonSpecies2 [0xcfd8] for the buffer overflow.
  • The bottom HM03 is swapped with the top HM03 to get rid of the 255 quantities.
  • The player moves to (y:9, x:16), to be able to interact with the now (invisible) sign-turned-mart vendor.
  • With the aforementioned item manipulation, the mart list overflows into other memory regions, allowing us to efficiently catch the remaining 148 Pokémon. Pokémon Storage System boxes are changed every 20 Pokémon (22 for the first round) using the Indigo Plateau PC at (y:07, x:15).
  • Once all remaining 148 Pokémon are captured, all party Pokémon except Ditto are deposited into the PC to save time on the Hall of Fame cutscene.
  • The player walks two steps down to prepare for a fast Hall of Fame warp.
  • TM40 x198 is swapped with Town Map (quantity representing the map ID for the map's north connected map).
  • TM40 x80 is tossed from TM40 x198, giving us TM40 x118, which the quantity corresponds to the Hall of Fame map ID.
  • Parlyz Heal x0 is swapped with HM05, setting the player's y-coordinate to 0 (quantity representing the player's y-coordinate).
  • The player walks up into the Hall of Fame. The two steps down taken earlier were necessary to put the player in a location where the player could walk upwards.

Major Terminology/Concepts

Quantity 255

When the game has to completely remove an item from the inventory, it shifts the items below in order to fill up the empty item slot, until it reaches the end of list terminator (marked as CANCEL). If an item with a quantity of 255 is below the tossed item, then the game mistakes the quantity of 255 for the end of list terminator and stops shifting the remaining items upwards. This leads to interesting side effects such as duplicating the 255 quantity item, or having another item represent the cancel button (despite not actually being the 0xff item). While the former effect makes obtaining the farming setup faster, the latter effect is relevant in obtaining Item Underflow.

Item Underflow/Dry Underflow

When the game merges two same items via swapping, it checks if the on-screen menu needs to be resized (note that this only refers to the current four items shown on screen). If the resulting list length is one, then the menu should be resized to 01 (only being able to use the first item). However, if a merge was somehow accomplished so that the resulting list length is zero (or any other value), then the menu is not resized. In normal gameplay, this does not matter as it is impossible to merge two items with only one item in the inventory. However, by having a non-CANCEL item act as the cancel button, we can merge two items together while having only one item in the inventory. By doing this twice, we can underflow the number of items in the inventory to 255.

LWA (Lucky Wins Again)

LWA, or "Lucky Wins Again" (poking fun at my successful attempts of finding new ways to break the Gen 1/2 glitched speedruns) is the main farming glitch used to catch the remaining 148 Pokémon in the game. The glitch abuses the capability for a mart to create a buffer overflow. When a mart is loaded, the game copies the list to wItemList [0xcf7b], terminated by 0xff. Therefore if we were to create a mart that has a terminator much later than expected, the copied data would overflow into unrelated memory. By controlling the buffer overflow, we can overwrite five main variables allowing us to catch Pokémon at a very fast rate. These variables are:
  • wEnemyMonSpecies2 [0xcfd8]: Read from when catching enemy Pokémon and is used to determine the resulting Pokémon caught, regardless of other similar variables.
  • wIsInBattle [0xd057]: Writing a value of 1 to this address allows throwing Poké Balls outside of battle.
  • wCurOpponent [0xd059]: Starts a battle if this value is non-zero. Must be kept as zero to prevent battles from being generated.
  • wBattleType [0xd05a]: Indicates if this is a non-standard battle (Old Man battle or Safari Zone battle). Must be kept as zero to prevent thrown Poké Balls from glitching out.
  • wEnemyBattleStatus3 [0xd069]: When a Pokémon is captured, the game sets a flag to indicate not to generate new DVs for the Pokémon. This is done in a very weird way, by setting a flag corresponding to whether the Pokémon has transformed or not, and has a side effect of causing subsequent out-of-battle captures to become Dittos (referred to as "Dittoization", and caused due to an assumption made by the programmers that a transformed Pokémon is a Ditto). Therefore, we want to clear this flag. This was the limiting factor for the efficiency of previous glitches, as the buffer overflow method used could not manage to clear this variable, requiring a battle to be completed (by running away) or a save and reset to happen. As this variable is cleared with the corruption, we do not need to do any additional steps to be able to capture more Pokémon.
Other relevant variables that are affected as a side effect of the buffer overflow:
  • wFontLoaded [0xcfc4]: Bit 0 determines whether font is loaded over the VRAM space for sprite walking patterns. Coincidentally, bit 0 is reset during the corruption, and in normal gameplay this would mean the player is transitioning to a different map via a warp, so the game assumes the LCD is disabled (allowing unrestricted access to VRAM) and directly copies the sprite walking patterns to VRAM. This saves time over if bit 0 was set, as the function to copy to VRAM while the screen is enabled would be called instead, thus wasting 5 frames (1 per sprite) every time the mart is closed.
  • wWalkCounter [0xcfc5]: Stores the remaining about of player sprite advances to perform. Longer values mean waiting more, so naturally we want to set this to zero.
  • wAudioFadeOutControl, wAudioFadeOutCounterReloadValue, and wAudioFadeOutCounter [0xcfc7-0xcfc9]: Writing a non-zero value to wAudioFadeOutControl will cause the game to start fading out audio, from the internal volume of 0x77 to 0x00 (in decrements of 0x11). This has a side effect of skipping sound effects, allowing us to bypass forced waits for certain sound effects, such as Pokémon cries. wAudioFadeOutCounterReloadValue, which reloads wAudioFadeOutCounter whenever it hits zero, is coincidentally loaded with 246 allowing for a fadeout long enough to keep the music playing until a cry is played (which sets volume to 0x33, then to 0x77).
To create this custom mart, text pointer manipulation is used. Firstly, the base text pointer is replaced to be 0xf31d (echo RAM copy of wNumBagItems [0xd31d]). From there, 0xf32f, the location where the Pewter Museum sign would read its text using pointer lookup, is manipulated to 0xf32b, which points to the earliest possible address that we can set up this glitch (anything earlier would require tossing the "CANCEL" item which requires too much preparation). At 0xf32b, we set its value to 0xfe. This causes the game to call the mart code instead, as in the text ID engine the game checks the first byte of the text to see if it matches specific values and does alternate functions based on them. In this case, 0xfe will treat the NPC (or sign) as a mart. By removing any early instances of 0xff, setting the actual terminator much later, and manipulating the expanded inventory pack to align correctly with the destination, we can create a buffer overflow that will desirably corrupt memory according to the above values to efficiently catch Pokémon.

Alternatives considered

  • Setting up another text pointer to bring up Bill's PC: The first iteration of the route had slightly better swaps and less movement, however creating a "fake" PC doesn't work out, as changing boxes from a PC that isn't accessed through the game's "hidden object" code (which also handles PCs) will result in the base text pointer being erroneously overwritten.
  • Using a single ROM based pointer to create the glitched mart: While only requiring the preparation of one pointer instead of two, there are no values in ROM that can represent a suitable pointer for the glitched mart without needing to toss the three CANCEL items at the start of the inventory for the buffer overflow to be successful.

Reasons for rejection

LWA isn't very interesting to watch and becomes boring pretty quickly, but the overall goal (catching all Pokémon) is considered 100% and is thus Vault-able. However, it could be deemed rejectable for not being entertaining enough for Moons and using somewhat arbitrary restrictions for Vault, which aims to go as fast as possible. These restrictions are in particular:
  • Does not modify Pokédex flags.
  • Does not execute arbitrary code.
Other restrictions were self-imposed during the routing of this TAS. These restrictions might not even matter towards fastest completion time as LWA may be the fastest setup anyway, although other setups that do not follow the other self-imposed have not been looked into.
  • Does not use glitches that allow executing arbitrary ROM addresses. Modifying the map script pointer (called every overworld frame) comes close to this as it allows specifying an arbitrary ROM address, but fails to completely cover the entire ROM space as only ROM banks that are used by maps can be executed. It is still not used for this TAS.
  • Does not use glitches that allow writing to an arbitrary destination. The text engine has capability to do this, using the unused command 0x03 to repoint the destination to theoretically any address, then by using the string engine to print text to the specified destination. However, it is unable to write completely arbitrary values as some values are used as "control codes" which do alternate functions that do not result in the byte being written. The invalid mart used in LWA does not fall under this as the destination address of the corruption is fixed, while the source is arbitrarily specifiable.
  • Does not use "mass corruption" glitches. Perhaps the most subjective of the self-imposed restrictions, the TAS forgoes glitches that can cause "mass corruption" (which isn't even well defined) such as party overflow (used in previous RTA speedruns of Pokémon Blue Any% No Save Corruption) or out-of-bounds Pokémon Storage System boxes, which can theoretically be used to write a massive amount of data to WRAM, albeit not entirely chosen arbitrarily. These glitches are forgone because of the general unstability of them, as well as the two mentioned "mass corruption" glitches are not easily manipulable.

Credits:

  • luckytyphlosion: Coming up with the route for the TAS and creating the LWA strategy.
  • gifvex: Botting the entire TAS and suggesting minor route improvements. He chose not to be listed as an author here, because Pokémon is primarily routing-based and LWA is [luckytyphlosion's] creation.
  • Chivu93: While he didn't participate in the making of the TAS, he improved the LWA strategy by using the Master Ball's quantity for the caught Pokémon instead of originally needing to toss a separate item for each Pokémon.
  • MrWint: Faster menuing techinique used in his "SRAM Glitch" TAS.
  • the pokered disassembly: General massive help in documenting the game's code allowing numerous tricks, including the LWA strategy, to be discovered.
  • BGB: Game Boy emulator with an amazing debugger that helped with routing out the TAS.
Noxxa: Judging.
Noxxa: This TAS spawned an interesting discussion on exactly what levels of glitchiness a run can contain while still being considered a legitimate full completion (catch 'em all) movie. Essentially, this movie sets a quite good example: arbitrary code execution and such glitches are not used, as they would break the point of being full completion, setting Pokémon capture flags through memory corruption is not counted (and isn't done), and the movie does run through the game to collect all Pokémon one by one before going to the ending, just like other runs of this category; it just does so more efficiently, cutting out gameplay time between captures and trimming down the capture sequence to its most basic form. Ultimately, it's just full completion to a highly optimized form. As such, this movie is acceptable for the Vault. The rules of the Vault have also been updated as a result of the discussion surrounding this movie, in order to define what levels of glitches are (not) allowed for full completion movies.
Since this movie is much more repetitive in achieving its goal, only relying on one major glitch to collect all Pokémon in one chain, it also can only be accepted in the Vault tier based on entertainment grounds. As such, accepting to the Vault as an improvement to the published "Gotta Catch 'Em All!" movie.
Spikestuff: Gotta Break 'Em All! PUBLISHING!... Wait... that's not how the song goes.

Show more

Hide
1 2 3
Posted: 4/1/2018 8:49 PM
Quote
TASVideoAgent
They/Them
Moderator
Joined: 8/3/2004
Posts: 15561
Location: 127.0.0.1
This topic is for the purpose of discussing #5910: luckytyphlosion's GB Pokémon: Blue Version "Gotta Catch 'Em All!" in 37:55.33
Posted: 4/1/2018 10:36 PM
(Edited: 4/2/2018 7:31 AM)
Quote
Patashu
He/Him
Joined: 10/2/2005
Posts: 4042
With the unfathomable brokenness of Pokemon and the constant advancement of speedrunning knowledge, it was inevitable that an arbitrary pokemon catching glitch would be found that's so fast it even beats catching pokemon normally and the category boils down to demonstration of this glitch, but this still exceeds my wildest expectations. Yes vote, and time to come up with a new even more arbitrary category to make 2018 on more interesting :D EDIT: Also, while I'm thinking about it. If an additional restriction was added, disallowing catching pokemon outside of starting a battle (and thus banning the glitch used in this TAS), would the run still be trivial?
My Chiptune music, made in Famitracker: http://soundcloud.com/patashu My twitch. I stream mostly shmups & rhythm games http://twitch.tv/patashu My youtube, again shmups and rhythm games and misc stuff: http://youtube.com/user/patashu
Posted: 4/2/2018 5:54 AM
Quote
Meerkov
Active player (410)
Joined: 10/4/2015
Posts: 99
I found the glitches neat, but I am always on the fence when it comes to accepting a run that uses heavy memory corruption glitches, but stops short of just jumping to the credit sequence. Probably wouldn't create a whole category for it.
Posted: 4/2/2018 7:32 AM
Quote
FatRatKnight
Editor, Skilled player (1199)
Joined: 9/27/2008
Posts: 1085
Let's first pull out a few movies that catches 'em all: [1860] GBC Pokémon: Yellow Version "save glitch" by p4wn3r in 01:09.63 Gets 152, as a side-effect of winning quick [2653] GB Pokémon: Red Version "Gotta Catch 'Em All!" by MrWint in 1:54:56.62 Glitches are involved [3134] GB Pokémon: Blue and Red Version "Coop Diploma" by MrWint in 3:48:04.10 Two games cooperate without glitches If we're defining 100% as filling out that pokédex regardless of arbitrary corruption or code execution, then the first movie has already beaten this run, and is itself already obsoleted anyway as its primary goal is actually any%. The fact it has 152 shouldn't really matter as, rest assured, it has the other 151 necessary for the 100% criteria. Then again, if everyone agrees that level of corruption shouldn't count for 100%, then we can disregard the first one, and the goals set out in this submission may well be the closest possible practical definition for Vault 100%, while that first movie isn't. Clearly, since the third movie I listed is glitchless, and does interesting routing stuff to get the 150 available without special one-time events or glitches, it is clearly out of the question to obsolete that with this movie. The goals are vastly different, giving a vastly different experience viewing either run. This leaves the second movie, with a curious route and catches exactly 151, which the other movies either overshot with 152 or undershot with 150. If a movie is to become obsolete, the second listed movie would be the most likely candidate, although I'm not sure if it should. If the goal is to fill out the 'dex with all 151 Pokémon, using the usual catching routine to do so, this submission broke apart the game and distilled the actions down to exactly that one function over and over again, bypassing even the usual combat entry to get to the function. It did not bypass the normal collection routines, just the normal sense of encountering stuff to then move on to the normal collection routines. Just wanted to point out previous movies that have filled out the Pokédex, with three different methods.
Posted: 4/2/2018 9:35 AM
Quote
Bisqwit
Editor, Active player (297)
Joined: 3/8/2004
Posts: 7469
Location: Arzareth
I love the fact that you actually caught all the Pokémon instead of just writing all-ones directly into the memory area that lists which Pokémon you have caught — even if the distinction is as subtle as just the Pokéball animation being shown for every ‘mon.
Posted: 4/2/2018 10:08 AM
Quote
MrWint
Skilled player (1039)
Joined: 7/24/2013
Posts: 175
TAS of 2017 Glitchy TAS of 2017 Gameboy TAS of 2017 Gameboy TASer of 2016 Gameboy TAS of 2016 Gameboy TASer of 2014 Lucky TAS of 2014 Gameboy TAS of 2014 Lucky TAS of 2013
When creating my TAS back in 2014, I was lucky the game was just broken enough to complete this objective in a reasonable time while still being somewhat varied and showing multiple facets of the game. Of course, the rules had always been somewhat arbitrary to begin with, disallowing certain glitches to make aiming for the fastest time still look interesting in the end, and this run clearly demonstrates that arbitrariness. I'm very interested to see what happens with this submission. It's clearly an improvement time-wise to the current run, which uses very outdated techniques at this point. But at the same time, it lost all its variety and may not be able to justify its arbitrary ruleset anymore due to being highly repetitive despite the restrictions. In the submission text of my 2014 TAS, I made a point about whether this is even a sound category still with how broken this game is, and at that point luckily it still was, but since the discovery of LWA it was clearly not anymore, and it was not easily fixable without getting even more arbitrary in the ruleset to a point where you can not really call it a speed-focused TAS anymore but rather a glitch exhibition. Anyway, thanks for making this, to put the finger on this problem. In my opinion, it should probably obsolete my current run, given that it's hard to justify its existence anymore unless you want to re-brand it as some kind of entertainment-focused glitch showcase run, but beyond that it's hard to recommend where to go with this category from here.
Posted: 4/2/2018 2:56 PM
Quote
luckytyphlosion
Player (27)
Joined: 3/2/2014
Posts: 34
Location: Canada
Patashu wrote:
EDIT: Also, while I'm thinking about it. If an additional restriction was added, disallowing catching pokemon outside of starting a battle (and thus banning the glitch used in this TAS), would the run still be trivial?
Off the top of my head, no. Even by using "out of battle" glitch items, the item cursor would still be reset and you'd have to scroll down to the item quantity which corresponds to the caught Pokémon, which would probably be slower than catching wild Pokémon (although it would still beat out some other catch methods).
Meerkov wrote:
The human element of the run is far more entertaining than the game itself. If it wasn't for someone lying about their record 40 years ago, I don't think we'd take a second look at this run/game. Meh vote.
Posted: 4/2/2018 4:48 PM
(Edited: 4/22/2018 4:19 PM)
Quote
Spikestuff
They/Them
Editor, Publisher, Expert player (2633)
Joined: 10/12/2011
Posts: 6437
Location: The land down under.
Flash TASer of 2022 PSX TASer of 2016
Oh so that's what they meant by Gotta Catch 'Em All being obsolete... Jesus. I'm going to have to watch this back to gather my thoughts on it, as well as my vote. The vote is leaning towards Yes on entertainment. Nope, scratch that. It dropped to Meh. (Obvious shotgun for Publication here on the off chance of it being accepted, cause Pokemon.)
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account. Something better for yourself and also others.
Posted: 4/3/2018 9:49 AM
Quote
ais523
Editor, Player (44)
Joined: 7/11/2010
Posts: 1029
I'm interested in how you managed to get a different Pokémon to be caught each time with the glitch. Where's the species number being read from? Anyway, this reminds me of previous April 1 submissions in which the player has edited a cheat engine into the game using Arbitrary Code Execution and used it to complete a non-any% goal. In this case, the glitch family used is Arbitrary Memory Corruption, not Arbitrary Code Execution, but the end result is fairly similar. These sorts of glitches are often looked for to exploit non-game programs, and so quite a lot of effort has been put into mitigating them; in particular, most modern home computers now ban executing RAM altogether by default. However, it turned out not to stop ACE-like bugs, because AMC is normally just as powerful (just harder to use). This run is a demonstration of that general principle. At this point, I don't think the category is meaningful unless you ban memory corruption altogether (i.e. buffer overflows and similar effects that can cause a RAM address to be written to by code that isn't meant to write to it). I'm not sure if the goal is still possible under those circumstances, but it might be, e.g. the Old Man glitch would probably still be legal (as although the memory addresses involved are being written with one purpose and interpreted as another, they're still being used for their intended purpose in both cases).
Posted: 4/3/2018 8:40 PM
Quote
luckytyphlosion
Player (27)
Joined: 3/2/2014
Posts: 34
Location: Canada
ais523 wrote:
I'm interested in how you managed to get a different Pokémon to be caught each time with the glitch. Where's the species number being read from?
Species number is read from the Master Ball count, and the custom mart buffer overflow copies it to wEnemyMonSpecies2.
ais523 wrote:
Anyway, this reminds me of previous April 1 submissions in which the player has edited a cheat engine into the game using Arbitrary Code Execution and used it to complete a non-any% goal. In this case, the glitch family used is Arbitrary Memory Corruption, not Arbitrary Code Execution, but the end result is fairly similar. These sorts of glitches are often looked for to exploit non-game programs, and so quite a lot of effort has been put into mitigating them; in particular, most modern home computers now ban executing RAM altogether by default. However, it turned out not to stop ACE-like bugs, because AMC is normally just as powerful (just harder to use). This run is a demonstration of that general principle.
This actually isn't an instance of AMC, as the destination of the buffer overflow is fixed (although the source is arbitrarily specifiable, making it a lot easier to utilize unlike earlier capture glitches such as Cooltrainer which use a screen tile buffer as its source). There are indeed ways to obtain AMC without ACE using Item Underflow, though.
ais523 wrote:
At this point, I don't think the category is meaningful unless you ban memory corruption altogether (i.e. buffer overflows and similar effects that can cause a RAM address to be written to by code that isn't meant to write to it). I'm not sure if the goal is still possible under those circumstances, but it might be, e.g. the Old Man glitch would probably still be legal (as although the memory addresses involved are being written with one purpose and interpreted as another, they're still being used for their intended purpose in both cases).
It is possible, but the amount of glitches allowed would be very minimal. Off the top of my head, the only glitches you'd be able to use would be Trainer-Fly, Safari Zone WTW, and Old Man glitch. You wouldn't even be able to encounter Missingno., as its sprite overflows into Hall of Fame data, and its seen Pokédex flag erroneously sets the 7th bit of the 6th item's quantity in the inventory (causing the well-known item duplication).
Meerkov wrote:
The human element of the run is far more entertaining than the game itself. If it wasn't for someone lying about their record 40 years ago, I don't think we'd take a second look at this run/game. Meh vote.
Posted: 4/3/2018 8:44 PM
Quote
thatguy
Editor
Joined: 11/3/2013
Posts: 506
I think "Lucky Wins Again" is possibly the best-named glitch ever. On whether this is entertaining - well, the submission notes are very honest here, it is really boring (at least after about 12 minutes, when you get to LWA). I voted no but that doesn't mean it's not a well-made TAS. Not sure whether this is publishable either - it would be a shame if we couldn't showcase such brokenness, but such is life. And it was definitely one of the stronger April Fools' Day showings this year.
Posted: 4/6/2018 10:57 PM
Quote
KusogeMan
Experienced player (689)
Joined: 2/5/2012
Posts: 1794
Location: Brasil
Lucky, do it in GEN2 next please!
I want all good TAS inside TASvideos, it's my motto. TAS i'm interested: Megaman series, specially the RPGs! Where is the mmbn1 all chips TAS we deserve? Where is the Command Mission TAS? i'm slowly moving away from TASing fighting games for speed, maybe it's time to start finding some entertainment value in TASing.
Posted: 4/7/2018 4:52 AM
Quote
Fortranm
He/Him
Editor, Experienced player (878)
Joined: 10/19/2013
Posts: 1121
I am totally amused by the glitch at first, but then, well, it gets old very, very quick. If this movie gets rejected, it's probably better to make the coop diploma run obsolete the Gotta Catch 'Em All branch, as it has lost its meaning at this point.
Posted: 4/7/2018 7:07 PM
Quote
luckytyphlosion
Player (27)
Joined: 3/2/2014
Posts: 34
Location: Canada
grassini wrote:
Lucky, do it in GEN2 next please!
Gen 2 would be slightly more substantial and would require actual routing, although it would still make heavy use of this mass farming glitch (although not as fast as LWA), which obtains four Pokémon Eggs with internal IDs that do not correspond to key items or mail (which can be found here). Pokémon that correspond to key items or mail would use a slower setup that shifts move IDs into the species byte. As the glitch isn't as fast, some Pokémon would still be obtained through normal catching means, although it's unknown which Pokémon would be caught over farmed. Regardless, there are many more "unobtainables" in Gen 2 than Gen 1, thus requiring more mandatory farming. Note that the video does not go over some preparation, including getting and duplicating the hybrid Egg/Sentrets, and hatching the Eggs. Also, while I did do the majority of the routing for this TAS, gifvex was the one that implemented the TAS into an input file, using his scripting TAS setup for Pokémon Red/Blue. As mentioned in the submission comments, gifvex chose not to be listed as an author "because Pokémon is primarily routing-based and LWA is [luckytyphlosion's] creation".
Fortranm wrote:
If this movie gets rejected, it's probably better to make the coop diploma run obsolete the Gotta Catch 'Em All branch, as it has lost its meaning at this point.
This is probably the best outcome for this submission (although this still might qualify for Vault). The TAS was mainly made to highlight the absurdity of Catch 'Em All as a speedrun. MrWint had said it well in his response to this TAS.
Meerkov wrote:
The human element of the run is far more entertaining than the game itself. If it wasn't for someone lying about their record 40 years ago, I don't think we'd take a second look at this run/game. Meh vote.
Posted: 4/8/2018 1:25 PM
Quote
ais523
Editor, Player (44)
Joined: 7/11/2010
Posts: 1029
For what it's worth, I simply skipped from the near the start of the repetitive bit to near the end. I enjoyed the rest of the movie.
Posted: 4/9/2018 4:37 PM
Quote
andypanther
Any
Former player
Joined: 6/30/2010
Posts: 1107
Location: Zurich, Switzerland
I voted no, this has to be the least enjoyable Pokémon TAS to me so far. The majority of the running time is completely repetitive and uninteresting. Since most viewers probably feel this way, I'm wondering if this run can even be published in the vault, given its arbitrary ruleset. I'm not exactly sure how the current rules for vault publications deal with games like this one, where we have clear definitions for both any% (reach the credits) and 100% (reach the credits while completing the Pokédex), but the any% just happens to also fulfill the 100% definition. Do the rules need to be modified for cases like this one, to allow for a single arbitrary restriction, just so that some form of 100% can be published in the vault? Even with such a rule in place, this particular TAS would most likely still be considered to have too many arbitrary restrictions. So at best, we could maybe have some other run published that uses any trick in the book minus save corruption. At this point, would it even be possible to create a "Gotta Catch 'Em All!" that is closer to MrWint's published run, but without having to write entire books about the ruleset?
Current project: Gex 3 any% Paused: Gex 64 any% There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
Posted: 4/9/2018 5:25 PM
Quote
Noxxa
They/Them
Moderator, Expert player (4110)
Joined: 8/14/2009
Posts: 4089
Location: The Netherlands
Exotic platforms TASer of 2018 Exotic platforms TAS of 2018 Exotic platforms TASer of 2017 Exotic platforms TAS of 2017 Exotic platforms TAS of 2017 Exotic platforms TASer of 2016 Exotic platforms TAS of 2016 Gameboy TASer of 2013
andypanther wrote:
Since most viewers probably feel this way, I'm wondering if this run can even be published in the vault, given its arbitrary ruleset. I'm not exactly sure how the current rules for vault publications deal with games like this one, where we have clear definitions for both any% (reach the credits) and 100% (reach the credits while completing the Pokédex), but the any% just happens to also fulfill the 100% definition. Do the rules need to be modified for cases like this one, to allow for a single arbitrary restriction, just so that some form of 100% can be published in the vault? Even with such a rule in place, this particular TAS would most likely still be considered to have too many arbitrary restrictions. So at best, we could maybe have some other run published that uses any trick in the book minus save corruption.
I've always taken full completion (in the sense of 100% item completion, etc.) to mean having the movie going through the motions to collect each particular item, instead of just requiring that the relevant completion flags are set. For example, I could take a Super Metroid ACE movie, take some cycles to write in 100% for the completion counter, and submit it as an improvement to the 100% run - but that would not really satisfy anyone, would it? So essentially, in a broader sense, I always consider ACE off-limits for any sort of full completion category, because once a run enters ACE, any sort of concept around completion is rendered trivial. Going to the ending is done in an instant, going to the ending with all completion flags set is done in an instant, even proceeding through the game with the normal route is rendered trivial. Likewise, memory corruption to set the completion flags (even if as a side effect) renders the actual collection objective moot, and I don't think anybody would be satisfied if I unobsoleted the previous SRAM glitch run as "full completion/catch-em-all". So what that leaves for a full completion goal is to force the movie to go through the motions to collect all items or whatever and have them processed in more or less the intended way. Obviously, Pokémon runs already go all over the place catching Pokémon in unintended areas or normally-impossible methods, so I can't really ban getting Pokémon outside of their intended encounter areas etc. (not to mention catch-em-all is impossible that way without an extra player and excluding Mew), so I'd say the basic requirement of a run here is really just to obtain the Pokémon through any of the normal in-game methods (encounters, give-aways, trades, evolution, etc.) regardless of exactly where or how. The previous catch-em-all runs did exactly that, and this movie also does the same thing, it just takes it to its logical extreme. Memory corruption and glitches are used to eliminate plot and filler between encounters, and every Pokémon is basically put in a row and processed one at a time at optimal speed. Then the movie skips directly to the end-game sequence, because no part of the goal requires such things as plot or battles to be done. Since the movie does not do the things that would invalidate it as full completion by above criteria (ACE, or memory-corrupting completion flags) and does fulfill its basic full completion goals (get all Pokémon and reach the ending) by obtaining its Pokémon through in-game encounter mechanisms (if highly glitched and optimized) using other methods of glitches available, I would consider this movie Vaultable. EDIT: The submission mentions other forms of (arbitrary) memory corruption that were not used in this TAS - I think some of these (like arbitrary ROM execution) could be banned from full completion runs in the same vein as ACE, or be considered a part of it. This is where the distinctions (for eligibility purposes) get really messy, however.
http://www.youtube.com/Noxxa <dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects. <Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits <adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.
Posted: 4/9/2018 6:18 PM
Quote
andypanther
Any
Former player
Joined: 6/30/2010
Posts: 1107
Location: Zurich, Switzerland
Mothrayas wrote:
I've always taken full completion (in the sense of 100% item completion, etc.) to mean having the movie going through the motions to collect each particular item, instead of just requiring that the relevant completion flags are set. For example, I could take a Super Metroid ACE movie, take some cycles to write in 100% for the completion counter, and submit it as an improvement to the 100% run - but that would not really satisfy anyone, would it? So essentially, in a broader sense, I always consider ACE off-limits for any sort of full completion category, because once a run enters ACE, any sort of concept around completion is rendered trivial. Going to the ending is done in an instant, going to the ending with all completion flags set is done in an instant, even proceeding through the game with the normal route is rendered trivial. Likewise, memory corruption to set the completion flags (even if as a side effect) renders the actual collection objective moot, and I don't think anybody would be satisfied if I unobsoleted the previous SRAM glitch run as "full completion/catch-em-all".
Thank you for clearing this up! The vault rules do not really make it clear that things like ACE are ignored when judging 100% goals.
Current project: Gex 3 any% Paused: Gex 64 any% There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
Posted: 4/9/2018 10:41 PM
Post subject: I stand with Mothrayas
Quote
Nach
Emulator Coder
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
Mothrayas wrote:
So essentially, in a broader sense, I always consider ACE off-limits for any sort of full completion category, because once a run enters ACE, any sort of concept around completion is rendered trivial. Going to the ending is done in an instant, going to the ending with all completion flags set is done in an instant
This idea is key. If you're doing ACE, obviously we want the best ACE possible, but ACE itself renders all other criteria moot. ACE is just ACE, it's not "ACE 100%", nor "ACE min%", nor "ACE unlocked Mew", nor "ACE I managed to rename the opponent into Nach and beat him 151 times in a row". Now obviously there can be different kinds of payloads, such as jumping to game completion, play a movie, add on cool features to the game and play it and other stuff, but any inherent built-in game play criteria and mechanism no longer matters.
Mothrayas wrote:
I've always taken full completion (in the sense of 100% item completion, etc.) to mean having the movie going through the motions to collect each particular item, instead of just requiring that the relevant completion flags are set. For example, I could take a Super Metroid ACE movie, take some cycles to write in 100% for the completion counter, and submit it as an improvement to the 100% run - but that would not really satisfy anyone, would it?
Yes, full completion means you actually had to do something to get whatever it is. Although there's ways to expedite it by glitching the game to skip all the prior criteria for each collectable/objective, and then just perform the actual last step for collectable/objective and then getting the desired 100%.
Mothrayas wrote:
Since the movie does not do the things that would invalidate it as full completion by above criteria (ACE, or memory-corrupting completion flags) and does fulfill its basic full completion goals (get all Pokémon and reach the ending) by obtaining its Pokémon through in-game encounter mechanisms (if highly glitched and optimized) using other methods of glitches available, I would consider this movie Vaultable. EDIT: The submission mentions other forms of (arbitrary) memory corruption that were not used in this TAS - I think some of these (like arbitrary ROM execution) could be banned from full completion runs in the same vein as ACE, or be considered a part of it. This is where the distinctions (for eligibility purposes) get really messy, however.
It is indeed messy, but what you're saying all makes sense to me.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
Posted: 4/10/2018 12:15 AM
Post subject: Re: I stand with Mothrayas
Quote
Fortranm
He/Him
Editor, Experienced player (878)
Joined: 10/19/2013
Posts: 1121
Nach wrote:
Mothrayas wrote:
So essentially, in a broader sense, I always consider ACE off-limits for any sort of full completion category, because once a run enters ACE, any sort of concept around completion is rendered trivial. Going to the ending is done in an instant, going to the ending with all completion flags set is done in an instant
This idea is key. If you're doing ACE, obviously we want the best ACE possible, but ACE itself renders all other criteria moot. ACE is just ACE, it's not "ACE 100%", nor "ACE min%", nor "ACE unlocked Mew", nor "ACE I managed to rename the opponent into Nach and beat him 151 times in a row".
Not really related to this game, but how about the games in which ACE doesn't give you full control so that you might only be able to set part of the flags needed?
Posted: 4/10/2018 8:53 PM
Quote
Extrems
Joined: 4/10/2018
Posts: 4
Location: Quebec, Canada
Link to video Console-verified using Game Boy Interface.
Posted: 4/11/2018 2:57 PM
Quote
ruadath
Active player (261)
Joined: 12/13/2016
Posts: 352
This one is console verified too!?!? :)
Posted: 4/11/2018 4:47 PM
Post subject: By quoting this, I affirm I also stand with Mothrayas
Quote
Noxxa
They/Them
Moderator, Expert player (4110)
Joined: 8/14/2009
Posts: 4089
Location: The Netherlands
Exotic platforms TASer of 2018 Exotic platforms TAS of 2018 Exotic platforms TASer of 2017 Exotic platforms TAS of 2017 Exotic platforms TAS of 2017 Exotic platforms TASer of 2016 Exotic platforms TAS of 2016 Gameboy TASer of 2013
Fortranm wrote:
Nach wrote:
Mothrayas wrote:
So essentially, in a broader sense, I always consider ACE off-limits for any sort of full completion category, because once a run enters ACE, any sort of concept around completion is rendered trivial. Going to the ending is done in an instant, going to the ending with all completion flags set is done in an instant
This idea is key. If you're doing ACE, obviously we want the best ACE possible, but ACE itself renders all other criteria moot. ACE is just ACE, it's not "ACE 100%", nor "ACE min%", nor "ACE unlocked Mew", nor "ACE I managed to rename the opponent into Nach and beat him 151 times in a row".
Not really related to this game, but how about the games in which ACE doesn't give you full control so that you might only be able to set part of the flags needed?
Any sort of completion flag modification (outside of the intended ways) is cheating itself out of performing a full completion, even if done only partially. This goes for any sort of memory corruption or partial-ACE trick, as I described in my previous post. The requirement for full completion is to go through the motions of collecting items, setting completion flags and so on through in-game actions/mechanisms, and that goes for every item/object/flag that counts towards full completion. Skipping any of them ruins the point of full completion to begin with.
http://www.youtube.com/Noxxa <dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects. <Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits <adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.
Posted: 4/11/2018 4:49 PM
Post subject: I like subjects.
Quote
Nach
Emulator Coder
Joined: 3/9/2004
Posts: 4588
Location: In his lab studying psychology to find new ways to torture TASers and forumers
I continue to stand with Mothrayas.
Warning: Opinions expressed by Nach or others in this post do not necessarily reflect the views, opinions, or position of Nach himself on the matter(s) being discussed therein.
Posted: 4/11/2018 5:04 PM
Quote
andypanther
Any
Former player
Joined: 6/30/2010
Posts: 1107
Location: Zurich, Switzerland
Just out of curiosity, Mothrayas: If someone submitted an Ocarina of Time 100% under the alternative ruleset, would you consider it legit?
Current project: Gex 3 any% Paused: Gex 64 any% There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
1 2 3