Even though it would have been easier to include an exception for Shedinja. But well...They actually had to revert this feature because it was deleting Shedinja that inherited the same tracker value from Nincada.
Even though it would have been easier to include an exception for Shedinja. But well...They actually had to revert this feature because it was deleting Shedinja that inherited the same tracker value from Nincada.
They are, the note about it after they announced it was for all the games i believeSince at some places the servers for Home already function, I want to ask if the moves get revriten if you transfer mon from Sw/Sh to BDSP. I mean, I know they are revritten when transfering to/from PLA, but what about Sw/Sh to BDSP and vice-versa?
Thank you. So that means do not transfer pokemon with event-exclusive moves, like the Pika with Sing, if you don´t wanna lose it. Gotcha.They are, the note about it after they announced it was for all the games i believe
The way it was described they'd retain the moveset when brought back to their home game (the example given was a SWSH Pikachu taken to BDSP or LA, would return to SWSH with the moves it had to begin with), though I'll admit I'm less sure of how something like Sing Pikachu would work if you brought it directly from Home to BDSP without ever touching SWSHThank you. So that means do not transfer pokemon with event-exclusive moves, like the Pika with Sing, if you don´t wanna lose it. Gotcha.
Tecnically easiest way to test it without compromising potentially rare movesets would be take any pokemon from gen 7 that is available in BDSP (or LA) that has a tutored move it can't get in gen 8, and transfer it directly to these games, and then to swsh.The way it was described they'd retain the moveset when brought back to their home game (the example given was a SWSH Pikachu taken to BDSP or LA, would return to SWSH with the moves it had to begin with), though I'll admit I'm less sure of how something like Sing Pikachu would work if you brought it directly from Home to BDSP without ever touching SWSH
This was moderately expected but also mostly confirms my theory that they only wanted to limit the move compatibility with BDSP and LA to not have to deal with potential constant "btw this move is fucked" - "btw this move shouldnt be in this game" etc.Scenario: What happens if you bring a pokemon with weird event stuff directly into BDSP touching a different game first? I am sacrificing my FEB2012 Mewtwo that had Electro Ball on it. In this scenario it went Home -> BDSP -> Back to Home -> SWSH
Answer: It gave the usual warning about it when moving it to BDSP. After shuffling it back into Home then SWSH, the original moveset (with electroball and everything) is reinstated. To my knwoeldge I never brought the Mewtwo from Home to SWSH even back when Home first went live. I'd test out my TRU Arceus with the trio moves but without a "normal" game to relate to uhhhh.....Kinda hard to really verify anything.
If mons can't retain their moveset upon entering BDSP, then what even is the point of transferring to BDSP? It feels pointless.This was moderately expected but also mostly confirms my theory that they only wanted to limit the move compatibility with BDSP and LA to not have to deal with potential constant "btw this move is fucked" - "btw this move shouldnt be in this game" etc.
I feel a bit better now about my fears from some days ago.
R_N if you end up being bored enough, would you try to confirm my theory (heck i can even help you with it) about what would happen if a pokemon with custom moveset in bdsp and swsh (say, TMs, or just various moves that aren't in level up order) is moved to a game, traded *via that game*, then on the new switch moved to the other game?
That would definitely require a second person, and i would take you on that offer, but trading pokemon in gen 8 is the worst most miserable experience gamefreak has ever mustered and kills my drive to experiment like that.This was moderately expected but also mostly confirms my theory that they only wanted to limit the move compatibility with BDSP and LA to not have to deal with potential constant "btw this move is fucked" - "btw this move shouldnt be in this game" etc.
I feel a bit better now about my fears from some days ago.
R_N if you end up being bored enough, would you try to confirm my theory (heck i can even help you with it) about what would happen if a pokemon with custom moveset in bdsp and swsh (say, TMs, or just various moves that aren't in level up order) is moved to a game, traded *via that game*, then on the new switch moved to the other game?
When you first send the Pokemon to BDSP or LA, it fully changes to the moveset corresponding to that game's level up movelist. Doesn't matter what it knew originally.I may have understood it incorrectly, but I think the moveset changes were on level-up or Legends-only moves, and everything else was just fine.
Yes but also not.We all know the REAL reason for this change is so they don't have to update SWSH with a patch that only adds a few tweaks to the legality checker and some new moves that'll just be unusable anyway.
Its been a while but i think the gist is that while native nincada are able to work around the clone check, the non-native nincada start (not) flipping flags for whatever reason.What's the reasoning behind blocking Nincada from being transferred from HOME to BDSP specifically, and not the other way around? I know it has something to do with clone detection and old versions of BDSP having rampant cloning glitches, but I don't know more details.
It feels like the situation GF/ILCA's trying to prevent is "player cloned and evolved a bunch of Nincada in BDSP before the patch, now we can't tell which ones are clones because our clone checker has to ignore Ninjask and Shedinja". But then wouldn't you want some kind of BDSP -> HOME block? A one-way HOME -> BDSP block for Nincada specifically doesn't seem to serve any purpose.
Do you remember which source this came from? According to Kaphotics' twitter, BDSP's clone checker automatically ignores all Ninjask, Shedinja, and all Pokemon without the BDSP origin mark. But cloning isn't possible in BDSP anymore (and you need to update to connect to Home). I'm still baffled by what purpose the block serves.Its been a while but i think the gist is that while native nincada are able to work around the clone check, the non-native nincada start (not) flipping flags for whatever reason.
Also I think this is like the third damn time the Nincada line has caused some sort of issue in gen 8 so I would not be surprised if Nincada is just coincidentally not in Gen 9.
There is an exception. That's what confuses me, because if anything it should block Ninjask and Shedinja from leaving BDSP, instead of blocking Nincada from entering, which is like exactly the opposite of what would make the most sense.To think it would be as simple as making the Nincada line an exception to the clone check...
Unfortunately no, and it's possible I'm conflating with other, earlier nincada nonsense.Do you remember which source this came from? According to Kaphotics' twitter, BDSP's clone checker automatically ignores all Ninjask, Shedinja, and all Pokemon without the BDSP origin mark. But cloning isn't possible in BDSP anymore (and you need to update to connect to Home). I'm still baffled by what purpose the block serves.
There is an exception. That's what confuses me, because if anything it should block Ninjask and Shedinja from leaving BDSP, instead of blocking Nincada from entering, which is like exactly the opposite of what would make the most sense.
That reminds me of the broken HOME clone checker, which is entirely separate from the BDSP one, uses different metrics (so raids don't get flagged en masse), and at some point used to delete Shedinja. As far as I know BDSP has never deleted Shedinja.Unfortunately no, and it's possible I'm conflating with other, earlier nincada nonsense.
I just distinctly remember someone clarifying later that the code had weird things that it SHOULD have checked, but didn't, in relation to nincada.
I did find this tweetThat reminds me of the broken HOME clone checker, which is entirely separate from the BDSP one, uses different metrics (so raids don't get flagged en masse), and at some point used to delete Shedinja. As far as I know BDSP has never deleted Shedinja.
Another way I'm thinking about this is: The only way something bad can happen is if
The restriction is on transferring into BDSP, so only BDSP's clone checker matters. But then:
- Non-clones are falsely flagged as clones
- Or clones fail to get flagged
I wonder if I have a fundamental misunderstanding about how something works.
- BDSP will never flag Pokemon without the BDSP origin mark, so there's no risk of false flags
- What bad thing could possibly happen by having a SwSh Nincada in BDSP, that would not happen by having the same SwSh Ninjask and SwSh Shedinja in BDSP? (If Nincada evolves inside BDSP then something bad allegedly happens, but if Nincada evolves outside BDSP then it doesn't happen?)
I have no idea how HOME works internally, but my theory is that it's because of the new game-specific-moveset saving mechanic and how it's stored on HOME servers + tied to the HOME tracker value, as that's the only relevant thing I can think of to why you aren't allowed to cross Nincada between games according to the tweet above. I can't picture an exact scenario on how this would work though if depositing Ninjask and Shedinja really does just reassign one tracker, but maybe you could possibly lose an egg move or something depending on how it works, while there would be no problem in the past because they could just keep the learned moveset the same.What bad thing could possibly happen by having a SwSh Nincada in BDSP, that would not happen by having the same SwSh Ninjask and SwSh Shedinja in BDSP? (If Nincada evolves inside BDSP then something bad allegedly happens, but if Nincada evolves outside BDSP then it doesn't happen?)