Blue CEA Possible New Rules.

Aug 6th, 2018 (edited)
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. CATEGORY SHOULD BE RENAMED TO "Catch 'Em All (No Mass Farming Glitches)".
  2. (Also, selfish request: add "Catch 'Em All (With Mass Farming Glitches)" I'll route out CEA with MFGs for Yellow if so).
  4. General Rules
  5. - Video proof is required for all submissions.
  6. - Timing is by RTA, where timer starts at New Game and ends when screen fully fades to white after Hall of Fame in game time is shown and 151 Pokemon are displayed in the Pokedex.
  7. - Saving and quitting (S + Q) is allowed.
  8. - Runs must be done on English version.
  9. - Having a save file present on the cart/emulator when you start the run is not allowed. You can use Up+B+Select on the title screen to clear your save data. As of [Date], runs should clear save data for every attempt so that all runs start on the same SRAM state.
  11. Glitch Rules
  12. - Modifying or corrupting Pokédex flags manually is not allowed, as it would completely invalidate the entire category.
  13. - Party Overflow is not allowed (i.e. Party Count can only be between 0 and 6), due to its unintuitive mechanics for routing and running and its ability to modify a very large amount of memory (albeit not all).
  14. - Save Corruption that does not overflow the Party is allowed.
  15. - Any glitch that generates a Pokémon directly from an item quantity is not allowed. This rule may be generalized in the future to include generic "value offset" sources, such as the inventory's cursor location.
  16. - The "CoolTrainer" glitch is not allowed, due to the RNG element of it.
  17. - Other glitches not covered by the Technical Rules are allowed.
  19. Platform Rules
  20. - The Super Game Boy peripheral for the SNES runs at an inaccurate framerate, and is therefore banned. Super Game Boy 2 is allowed, however.
  21. - All variants of Game Boy Tower have inaccurate emulation, and are therefore banned.
  22. - The 3DS Virtual Console version is not allowed due to poor emulation of certain glitches.
  23. - The only allowed emulator is the latest release of GambatteSpeedrun (Currently r614) with a GBC bios image.
  24. - All other emulators are banned.
  25. - If using emulator, using save states and speedup for any reason (including reaching the New Game screen faster) is not allowed.
  26. - Using emulator to create custom palettes that are not usable on any kind of official console is not allowed.
  27. - If using emulator, you must do ONE OF (not both) the following to prove your run is using the correct emulator:
  28. - 1. Hard reset the emulator using Ctrl-R or the menu option before the start of or during the first 10 minutes of every individual attempt, and include the footage of that reset in your run submission video
  29. - 2. Capture the entire emulator including the window border for the submitted video. An example can be seen here:
  31. Technical Rules
  32. If you don't understand what any of the Technical Rules mean, you probably aren't in any danger of breaking them. These are intended for people who understand GBZ80 programming to let them know what they can and can't do in terms of developing new strategies/glitches for the category.
  33. - Arbitrary Code Execution (ACE), execution of code in RAM, is not allowed. More specifically, program counter cannot be in $8000-$ff7f, and $ff8a-$ffff, and memory at $ff80-$ff89 cannot be modified.
  34. - Arbitrary ROM Execution (ARE) (formerly AJMP/Arbitrary Jump Pointer Manipulation), the ability to execute any (16-bit) address in ROM, is not allowed.
  35. - Arbitrary Memory Corruption (AMC) (formerly ARM/Arbitrary RAM Modification), the ability to write to any (16-bit) address, is not allowed.
  36. - Out of Bounds RAM Pointer Modification (OOBRPM) is not allowed. This rule is in place to ban other Mass Farming Glitches that do not rely on Item Quantities. Some examples to clarify this rule are:
  37. - Modifying the map text pointer or the resulting sprite's text pointer to point to RAM.
  38. - Modifying the top left block pointer to point to RAM and be out of its intended area.
  39. - Modifying the Brock Through Walls source pointer to point to RAM.
  40. - In general, having a pointer not be one of its valid values and point to RAM. [sort of vague]
  41. - Note that the pointer has to be used for it to be considered OOBRPM. For example, modifying connection pointers are allowed as long as a connection isn't crossed.
  42. - This rule may be reworded in the future to be more general.
  44. Possible Holes:
  45. - Gift LG abuse: Unfortunately, I don't have enough knowledge of the route (or motivation) to determine whether this poses a real problem. I will be willing to assist someone to try to figure out a setup using this strat.
RAW Paste Data