Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/02/23 in all areas

  1. Sorry to burst your bubble, but it is likely illegal. At first glance, the name looks legal: However if you go into the trash bytes of the name (trash bytes -> bytes in data after the name is terminated. After the 0x00, in this case the 0x00 is from $08 to $09): there's extra characters at the end, after the Korean name! If you convert all the hex to UTF16 string: You see te from Omanyte. It is normal for Pokemon to have trash bytes in their nickname. However, IIRC, it isn't normal for Korean unevolved Pokémon to have English trash bytes in their name, especially from the English species name. In this case, I reckon someone hatched/genned a English Omanyte, then changed the language in PKHeX, not realizing the trash bytes would remain. And to preempt the 'why PKHeX doesn't validate trash bytes?', I think it tried but what happens is that there are many many scenarios that trash bytes can exist. And they vary from game to game. And some transfers removed trash bytes. I remember PKHeX used to validate basic trash bytes for a while but no idea what happened to it. In any case I don't think Switch games check them for trades, but HOME clearly does.
    2 points
  2. You could try nicknaming it something very long (so that any trash bytes will be overwritten) and seeing if it still happens. If that does the trick, you'll have a legal Omanyte and you'll have pinpointed the cause with no room for doubt.
    1 point
  3. To begin with, trash bytes don't serve any purpose (hence the word trash in the name) One example of it happening in some games (maybe for all, I don't recall) is when something with a longer name, evolves into something with a shorter name. So for example, Chikorita -> Bayleef In reality, the name is now Bayleef/a, where / is the terminator in this example. The game just replaces the minimum amount of the name, then tags on a terminator. everything else isn't erased, but not visible in game, effectively becoming 'trash'. In older games, you could trade a Pokemon to another language'd game and evolve it there, and it'll get that nickname upon evolution. So in Chikorita's case, it becomes 베이리프/rita HOME may not necessarily be checking specifically the trash bytes, but rather making sure the entire nickname region doesn't have a mix of impossible characters, and the trash byte being part of the region, got detected. I can't say for sure. But yeah, while trash bytes wasn't generated by the game on purpose, and isn't used, as per anything else in a Pokémon's data, it can be used for hack checking
    1 point
  4. Yup made officially but not public. Just speculation, but the SV and BDSP icons look like these, so chances are they've all been made and waiting for use case, such as in-games, for visuals in live competitions, any other official way they would want to display them, etc. I don't know for sure how the personal_info is dealt with in SV, but SWSH had them all wiped out. So the data may or may not be there. It also may just be remnants from older games (like SWSH), and not indicative of whether it'll be back (DLC or otherwise).
    1 point
  5. The file size looks too small. I have yet to look at it but I assume that’s not an actual save. so it’s not that it’s corrupted, it’s that it’s the wrong file
    0 points
×
×
  • Create New...