ReddestDream 0 Posted May 25, 2015 Share Posted May 25, 2015 This is a minor issue, but I noticed that when my Nincada evolved into Ninjask and learned Baton Pass at level 35, the Shedinja that formed also knew Baton Pass. Shedinja should only know the moves Nincada had at level 35, not including any new moves learned upon evolution. This oversight was corrected in the Official Games in Gen V. "Prior to Generation V, if Nincada learns a move upon evolving into Ninjask, Shedinja will also know this move. This means that Shedinja can learn any of Ninjask's level up moves starting at level 20, but only the ones learned at the same level. In Generation V, Shedinja starts with the moves Nincada knew prior to evolution." http://bulbapedia.bulbagarden.net/wiki/Shedinja_(Pokémon) Thanks! Link to post Share on other sites
Vinny 27 Posted May 25, 2015 Share Posted May 25, 2015 This was reported a long time ago actually. http://www.pokemonreborn.com/forum/index.php?showtopic=7809 I don't know if it's an "pokémon essentials" issue, or if the dev team simply forgot, but yeah. Let's wait for Ame/Dan/Jericho i guess. Link to post Share on other sites
Jericho 114 Posted May 25, 2015 Share Posted May 25, 2015 The text file shows it correctly. I'll see if I can recreate it later, or if someone beats me to it. I'd like to know. Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 This was reported a long time ago actually. http://www.pokemonreborn.com/forum/index.php?showtopic=7809 I don't know if it's an "pokémon essentials" issue, or if the dev team simply forgot, but yeah. Let's wait for Ame/Dan/Jericho i guess. So, I looked into this and, yes, the Shedinja and the Ninjask still "share" the same pool of PP for their moves as of 14.6, just as was reported a year ago on that thread. Depositing one of them into the PC and then withdrawing it again does not fix it. Moving them around in the party does not fix it. These two pokemon apparently are sharing the same exact variables for their moves and PP for whatever reason. Moving the order of the moves also moves it for the other pokemon and vice versa! Even more bizarrely, teaching a move to one of the two automatically gives it to the other one as well. It's like, you can have a move set for Shedinja or Ninjask, but whatever you do to one will also happen to the other . . . Okay. Yeah. This is a more significant issue than the one I initially intended to report. I've attached my save file in case anyone wants to play around with these "linked" pokemon. The only thing I haven't tired yet is nicknaming Shedinja. Maybe that will break the link? Edit: No. Nicknaming Shedinja does not break the link between their moves. Also, putting one into the DayCare Center and then taking it out does not break the link. Thanks! Game.rxdata Link to post Share on other sites
Jericho 114 Posted May 25, 2015 Share Posted May 25, 2015 Oh then it must have to do with the Pokemon ID somehow being the same when the pokemon was generated. Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 Oh then it must have to do with the Pokemon ID somehow being the same when the pokemon was generated. They can be nicknamed differently, and they do have different stats. Only the moves appear to be linked. It's like they are reading from and writing to the same set of move variables, but everything else is independent. Link to post Share on other sites
Jericho 114 Posted May 25, 2015 Share Posted May 25, 2015 Yeah but teach one of them a different move and then look at the other. It means the game is reading them as the same pokemon in a sense, yes they can be different levels though. Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 Yeah but teach one of them a different move and then look at the other. It means the game is reading them as the same pokemon in a sense, yes they can be different levels though. Okay. I did. They always both have the same moves in the same order with the same PP values no matter what you do. Any idea on how to fix this? Thanks! Link to post Share on other sites
Jericho 114 Posted May 25, 2015 Share Posted May 25, 2015 This specific instance? I can give you a new Shedinja that's identical to how it should be. But the issue would be seeing what specifically caused the issue. I'll try it myself and then I'll also check the save file and look into why it's like that. Probably tomorrow though. Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 This specific instance? I can give you a new Shedinja that's identical to how it should be. But the issue would be seeing what specifically caused the issue. I'll try it myself and then I'll also check the save file and look into why it's like that. Probably tomorrow though. Okay. Thank you! Link to post Share on other sites
AuthorReborn 8 Posted May 25, 2015 Share Posted May 25, 2015 Out of curiosity, what would happen if you released one and kept the other? Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 Out of curiosity, what would happen if you released one and kept the other? Nothing, other than the fact that now one of them is gone. Well, it fixes the problem of two pokemon sharing the same move-variables, but I would hardly call that an optimal solution . . . Link to post Share on other sites
AuthorReborn 8 Posted May 25, 2015 Share Posted May 25, 2015 Nothing, other than the fact that now one of them is gone. Well, it fixes the problem of two pokemon sharing the same move-variables, but I would hardly call that an optimal solution . . . True, okay, well at least my curiosity is no longer shouting at me "what if..." Thanks for your time. Link to post Share on other sites
ReddestDream 0 Posted May 25, 2015 Author Share Posted May 25, 2015 True, okay, well at least my curiosity is no longer shouting at me "what if..." Thanks for your time. My save is posted above if you want to try playing around with it yourself. Thanks! I'm thinking this was caused by the fact that the original Nincada evolved into Ninjask at the same level where Ninjask also learned a new move (Baton Pass; level 35). Both Ninjask and Shedinja were created at the same time. Somehow, when Ninjask learned Baton Pass right after evolving, Shedinja's move-variables got linked to the same data. I'll bet if I evolved Nincada at a level where it didn't learn a move as Ninjask, this wouldn't happen . . . In case you are wondering how I got Dig, I leveled up Nincada to level 37 while it was holding an Everstone, then Common Candy-ed it back down to Level 34 so that it could also learn Baton Pass at level 35 when it evolved into Ninjask. I don't have access to the Move Relearner yet, so this was the fastest way for me to get both Dig and Baton Pass on the same Pokemon. Edit: I used Debug Mode to change the pID of both Ninjask and Shedinja, which was initially the same. This did not unlink them, even after saving, reloading, and depositing one into the PC. Their moves continued to be linked even though their pIDs were now different. The Duplicate option also does not fix anything. The duplicates are still linked to the originals' moves . . . I couldn't think of anything else to try, so I just deleted the linked Shedinja and generated a whole new Shedinja and gave it all the moves (including False Swipe instead of Baton Pass), IVs, EVs and Nature the old one had. This new Shedinja is no longer linked to the original Ninjask. Link to post Share on other sites
Administrators Amethyst 2467 Posted May 26, 2015 Administrators Share Posted May 26, 2015 We chanced upon and tested this a few days before beta actually. It's been recorded, but don't expect it to be fixed soon. This error does come from base Essentials so there doesn't seem to be a fix ready. Link to post Share on other sites
ReddestDream 0 Posted May 26, 2015 Author Share Posted May 26, 2015 We chanced upon and tested this a few days before beta actually. It's been recorded, but don't expect it to be fixed soon. This error does come from base Essentials so there doesn't seem to be a fix ready. Ah, I see. Thank you for the explanation! Link to post Share on other sites
Recommended Posts
Archived
This topic is now archived and is closed to further replies.