Piexplode

RBY Desyncs Information

May 29th, 2020
150
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.26 KB | None | 0 0
  1. ----------------------
  2. Known desyncs in RBY
  3. ----------------------
  4.  
  5. Bide - If a Pokemon is using Bide, and the opponent faints due to burn or poison, this causes a desync. For more information, see this video by Crystal_: https://www.youtube.com/watch?v=IVxHGyNDW4g
  6.  
  7. Counter - Using Counter against a paralyzed opponent who has selected or used a Normal- or Fighting-type move, but fully paralyzed, can cause a desync. For further details, see this post by Enigami: https://www.smogon.com/forums/threads/past-gens-research-thread.3506992/page-8#post-8342135
  8.  
  9. Mirror Move - Using Mirror Move when the opposing has started a partial trapping sequence causes a desync.
  10.  
  11. Psywave - 1 in 151 chance of causing a desync at level 100 in a link battle.
  12.  
  13. Thawing - If a Pokemon is frozen, does not switch out, and is thawed out by a faster Pokemon, this causes a desync. Any move that burns and Haze can thaw a Pokemon, and only Ice Beam and Blizzard can freeze a Pokemon. For more information, see this video by Crystal_: https://www.youtube.com/watch?v=iSSf4XaqGAU
  14.  
  15. ------------------------------------
  16. Dealing with Desyncs - Pros & Cons
  17. ------------------------------------
  18.  
  19. ================================================================
  20. Whenever link battles would desync, patch it in the simulator.
  21. ================================================================
  22.  
  23. Pros:
  24.  
  25. - It allows major game elements like Counter to stay (unlike the banning approach) and is a smooth experience for players unfamiliar with RBY's intricate mechanics (unlike the warning approach).
  26. - Largely the status quo. If this approach was taken, the only change that would be made to the standard ruleset is that Psywave would be allowed.
  27.  
  28. Cons:
  29.  
  30. - Not strictly adherent to what's possible on cartridge (with the exception of using viral ACE [arbitary code execution] patching).
  31. - "Slippery slope" argument - if we can patch the game to deal with desyncs, and to limit freezes, it gives more ammunition to people who want to patch out other aspects of the game.
  32. - When a desync occurs, there are by definition two different ways the game could go, as each player sees a different scenario playing out. In patching the game, we would have to decide which option we go with.
  33.  
  34. ============================================================================================================
  35. Any move that can in any way cause a desync should be banned, even if it is a competitively relevant move.
  36. ============================================================================================================
  37.  
  38. Pros:
  39.  
  40. - Cartridge faithful
  41.  
  42. Cons:
  43.  
  44. - There would be a quite drastic competitive impact to prevent the thaw desync, thereby eliminating most Fire- or Ice-type moves from the game.
  45. - Would lead to a significant number of move bans.
  46.  
  47. =======================================================================================================================================
  48. If a move could cause a desync, that is the player's risk. They should be warned that they could cause a desync, but if they do cause a desync they lose the battle.
  49. =======================================================================================================================================
  50.  
  51. Pros:
  52.  
  53. - Remains faithful to cartridge while leaving as many options available as possible.
  54.  
  55. Cons:
  56.  
  57. - Could easily be very confusing for newer players to get to grips with.
  58. - Lot of effort to implement on the simulators.
  59. - Creates alternative win conditions (i.e. if you cause your opponent to cause a desync, then they lose the battle).
  60.  
  61. =======================================================================================================================================
  62. If a single move is responsible for a desync, then it should be banned, but if multiple moves could cause a desync it should be patched.
  63. =======================================================================================================================================
  64.  
  65. Pros:
  66.  
  67. - Depending on your interpretation, this is either the status quo, or the status quo with perhaps Counter or Mirror Move banned. This makes implementation easy.
  68.  
  69. Cons:
  70.  
  71. - Inconsistent. If you can patch in some instances, why not patch in all instances?
  72. - Not cartridge faithful
Add Comment
Please, Sign In to add comment