Jump to content

Leaderboard

  1. RetroAli

    RetroAli

    New Member


    • Points

      3

    • Posts

      15


  2. Kaphotics

    Kaphotics

    Helpful Member


    • Points

      1

    • Posts

      8105


  3. Blue587

    Blue587

    Member


    • Points

      1

    • Posts

      27


  4. XxPhoenix1996xX

    XxPhoenix1996xX

    Moderator


    • Points

      1

    • Posts

      35


Popular Content

Showing content with the highest reputation on 03/09/20 in Posts

  1. Was talking about this Mew to Gridelin the other day and we realized that the existing scans of this issue of Pokemon Power literally disappeared from the internet. (or at least from what we could find lol) I managed to find someone with this specific Pokemon Power issue and they provided scans for the cover & Mew information. Thanks to @doeiqts on Twitter for the help. https://imgur.com/a/bbrK16r
    3 points
  2. Introduced in the middle of February 2020, Pokémon HOME allows for importing from Bank and Let's Go Pikachu / Eevee, and bi-directional connectivity to Sword & Shield & future titles. When a Pokémon is transferred from Bank or Let's Go Pikachu / Eevee or their games of origin into HOME, the Pokémon is assigned a unique 64 bit number by the official cloud server to differentiate it from other uploads stored on the cloud server. Pokémon that have not yet visited HOME do not yet have a HOME tracker. Pokémon that are traded in-game (online/local trades) do not get assigned a tracker. Pokémon that must travel thru HOME to reach the game it resides on must have a HOME tracker (origin->current). Pokémon that are uploaded in the same batch are not guaranteed to have a similar tracker (sometimes incremental). Pokémon that are missing a HOME tracker that should have one, or have a fake one, are rejected for upload (error 10015). Trackers are only a concern in PK8+ formats. Pokémon that aren't yet in the PK8+ (2019) do not have a field for this data. What exactly is this value be used for? Storing data for each game visited outside of HOME (ex. SW/SH, PLA, BD/SP, S/V...) Tracking how Pokémon are traded between users. Detecting if a Pokémon has been modified/cloned from the original upload. Detecting if a Pokémon is newly entered into the HOME system (having a value of zero). HOME trackers will be changed each upload, so a tracker value is not a permanent value. Only HOME can determine if a tracker value is valid. Only HOME can create valid trackers. Best practice is to let the server assign you a tracker, rather than assigning a blatantly wrong tracker. For local/online gameplay, GameFreak does not check this metadata, so having arbitrary/lacking tracker values does not matter. Validating a HOME tracker requires API access to HOME, and is not something the hacking community will ever have access to. GameFreak does not validate HOME trackers for online play, but for officially sanctioned VGC events, they do -- you shouldn't be using hacked Pokémon in tournaments anyway (against our rules). Due to the described behavior, here are our recommendations: When creating new Pokémon that are from generations prior to Sword & Shield, transfer into HOME via Bank first. When Bank closes, see below. When creating new Pokémon that can be uploaded from their game of origin, leave the tracker blank. When creating new Pokémon that will reside in a game different from their origin, generate and transfer them from their game of origin. When modifying any (that have already visited HOME) immutable values (PID, IVs, etc), zero out the tracker then transfer starting from their origin games. Why not create a random tracker value? Again, only HOME can determine if a tracker value is valid. HOME will check tracker values to see if the details match the original upload (modified data). HOME will check tracker values to see if the details are on another user's account (cloned data). HOME will disallow uploads if the tracker doesn't match the data on their server (error code 10015). Uploading to HOME without a tracker value will automatically assign a new one (note: only when entering from their native games). You can receive Pokémon that lack a tracker value from other players via trade (in addition to a game's natives). Using an invalid tracker may fool checking tools (like PKHeX) that do not have access to HOME's API, but can still be checked by trying to upload to HOME manually. Do not be deceitful. What happens when Bank shuts down? Any Pokémon that must have traveled from Bank->HOME will not be able to receive a tracker from the HOME servers, and thus will never be able to enter even if manually injected into a Switch game. Even if some side games like SW/SH currently allow skipping Bank and directly injecting to HOME, it is expected that this "loophole" will no longer exist once the transfer route from Bank->HOME is removed when HOME is updated. Additionally, this has never been an advised path to "inject" Pokémon, as a past-generation Pokémon entering via SW/SH instead of Bank is detectable by the server (athough not currently actioned). If it does persist, it is an easy way to get your Switch banned if they ever decide to swing the ban hammer at the obvious hack. You'll still be able to use PKHeX and other community applications to move Pokémon between your save data, but you must accept the fact that they will never be able to enter HOME (or online-only connected games like Champions) or be considered legitimate. What happens if someone clones my Pokémon with a tracker? When uploading to the server: The server fetches the existing details of that tracker. The server checks for cheating: if any property that is impossible to be legitimately changed has been changed, the server then rejects the upload. The server creates a new entry on the server with the revised data and assigned a new tracker for that revised entry. The upload now has this "new" tracker. The original tracker and its data are retained by the server. The clone is essentially diverged from the original; by retaining the original data, the original Pokémon (or any other clones) can still be uploaded by anyone who possesses a copy, undergoing the same divergence process. PKHeX's default settings are to require tracker values (should be on every non-Gen8 origin Pokémon that is residing in Gen8+, etc), but has a toggle setting to opt-out of strict checking. This is to allow users to create the most-legal data without forging an INVALID tracker value, for in-game play.
    1 point
  3. suloku was able to correctly dump the Mew from the corrupted save, and so now I present the legit Danish Mew, obtained from a Mew Machine in Odense, Denmark. 151 - MEW - ECDB.pk1
    1 point
  4. I personally received Italian AURA Mew in 2007 on Pokémon Leaf Green and Emerald, I confirm that "Origin Game" is Ruby for both.
    1 point
  5. I just want to thank everyone involved in this project. Is always amazing to find, recover and preserve events that we thought lost, but this is something special. From finding this hardware we've learned tons about the mechanics of the distribution machine itself and the code making possible to recreate even more events/campaigns. I hope that with this kind of discoveries and videos makes people know and get even more interest in this world. Some of us thought this would never be possible, now I think that everything can be. Probably we'll find the Mew/Celebi Machine too! Thanks to the owner of the device for letting us preserve the information about this. Thanks to RetroAli and Hard4Games - Tony for your effort and dedication to make people know about this. Flood the market! Thanks to our amazing event research team for their time and love for preservation. @Sabresite @Deoxyz @ajxpk @Gridelin And thanks everyone in this community for supporting this project.
    1 point
  6. Glad a web browser version exists now, it's much more convenient like this! I'm wondering though, does nobody read the GtI/Super research thread anymore? I posted my Python script 9 months ago and it went unnoticed until it was discussed elsewhere a few days ago. I'm not bothered by this, I just realized the thread is going unnoticed and I'm wondering why that is Since this is getting some attention, I'll take this opportunity to talk about QR codes. Does anyone have any experience working with them? I only managed to take a look at the decoded binary data and it didn't seem to be too complicated. If I remember correctly, a section was completely different, but I don't know what that data is, it might not even be important or required. There was another section that looked very similar to the password, with only some bytes or bits being swapped around. If that's all we need to change, converting QR codes should be just as easy. Additionally, I noticed I didn't mention this in my original post, but here's some more info about the Japanese version. The passwords are one line shorter than the western versions. Also notice how this last extra line is the same in both regions. As I have explained, I can't compare the Japanese version the same way I compared the western versions because Japanese save files are different. Finding out what the differences between save files are might help. I wonder what the extra line in the western versions is for, I don't see why western passwords would need more data
    1 point
  7. Having the ID at the end helps to chain over the dolls + item trader. If I'm Not mistaken, if your main cart doesn't have the item trader, it's okay. just soft reset a dummy cart until you get the ID with the item trader, then mix records to get the item trader onto your mix cart
    1 point
×
×
  • Create New...