theSLAYER

Same PID bruh. (0x5551B96C in decimal is 1431419244) So yup, PID is static. IVs for these are dynamic.

No worries. I've made a few edits, not sure if you've seen them. The Lv 1 Party Hat Raichu just narrowed the time frame down further. (assuming both mechanics changed at the same time, they existed till Jun 24/Jun 25 [variant date due to timezone differences]) Either the Lapras image was pre-trading official images and that the mechanic of bumping up was never implemented (tho I do doubt that; [a] an easy reverse image search should prove that and [b] commenters vouching for it), or that the change occurred super early into trading (first 3 days), or some kind of requirement was necessary (maybe trading low level mons between 2 lv >20 accounts?) I'm under the impression that everyone just guessed, but there has to be someone who argued against it right? Just need one person on silph road. Someone with images. Anyone. XD

As I previously said (but I may not have been super clear, sorry bout that), if low level Pokemon were traded and unable to retain low level status (a silphroad post from Jun 22, 2018 shows how it gets bumped up to level 20), I have no reason to think that mons could go below 20 when trading. (This signifies that Level 20 is a hard limit in any direction) However, based on your Beedrill (in August 2018) and the Chansey I did prior to this post (used low->low and low->high), Lv 1 mons can be traded. Thus, breaking the hard limit level 20 limitation I was testing. While the trainer level + 2 claim doesn't seem entirely founded (at least I've yet to find any media to back up that claim), the image of the Lapras being bumped to Lv 20 seems to be real (doesn't help that the commenters seem to be sure of that claim, tho the lack of media is always concerning). Assuming that both of these things are real, the noted time frame of both phenomenon seems to overlap. If so, that seems to indicate that a change in trading mechanic possibly occurred within the first few weeks of trading being initiated (end of June, start of July, 2018).

Scratch that, I just tested, and proved that low level mons can be traded. Unsure if it's a limited only to low level accounts, but huzzah. (my level 1 chansey remained level 1) [once again, either limited to low level accounts, or a recent change or (the bumping up to 20) limited to first week of trading] So I guess the next thing you can be sure of, is to check CP+Traded+Premier Ball. If the mon was traded in 2018 and has premier ball, it logically has to be caught at lv 20. That may help, since as you said, you can't reliably tell what levels other mons are. Yeah, I think my 2016 entries have their dates messed up too. edit: Your Lv Beedrill is from August you say? You got anything from July, since that's the date range I was curious about.

Is this the lv 1 beedrill you're proud about? What's the new hatch date or present trade day?

The initial trade don't have to be from a high level mon from a high level companion. From what I can tell, low levels gets bumped up to lv 20 (Jun 22, 2018, appears to be pretty much from the beginning). So all we need to do is to sort by low CP + traded, and see if anything appears to be below lv 20. I'm basically just checking if any lower level exists from trade. It appears the minimum from trade is 20 (regardless of what level they're trading you; bumped up to 20 if mon level is lower, bumped down to 20 is recipient's level is lower, level remains if trainer and mon is higher than 20) So technically I'm checking two things, but they easily could roll into one. 1. Whether low level trades can even occur 2. Whether mons can downlevel below 20. If low level trades can't even occur, then I have no reason to believe mons can downlevel below 20. edit: Granted, your point on stardust is valid, however I want to know the limits of trade mechanics itself. One could always get an Articuno via raid and not have to do the 1mil stardust.. I have caught legendaries on low level accounts to test, it was just way after this initial trade phase. Presently the only limiting factor to the +2 theory is the initial phase of trading.

Yeah a before and after would be tough. The main thing I wanna know is if the +2 bs was ever real (for trades), within the first 2-3 weeks they rolled out GO trading. So any proof of it, would be showing the CP + traded date in summary (any lower than lv 20 CP, and the mon was traded). Because as that video + CP calculation shows, by Jul 11 2018, the supposed +2 was already not a thing then (if it was ever a thing). One thing I'm unsure about, is when they implemented this "date" function for traded stuff, and whether it is retroactively applied to stuff traded prior.

if you still have access to those low level accounts, and could show a few screenshots of a mon traded in the first month, and its CP, that would probably help to solidify the case. I'm unsure about mons acquired a while ago, but right now in Pokémon GO mons have the "date caught" and "date traded" at the bottom of the summary. I've been trying to track down any confirmations to the trade cap being the same as the level cap, and so far the earliest trade media with a low level recipient is this video: https://youtu.be/WyNebQJZfY4?t=883 [Video uploaded Jul 13, 2018, about 2-3 weeks after trading implemented in GO; Appears to be recorded on Jul 11, 2018.] (Screenshot of trade, in case anything ever happens to the video): As you can see, Gligar traded to a low level account (not level 10, but being low enough from 20). Took me a while to find the Level of Gligar (old calculations maybe?), but it's level range and HP range indicates it is at level 20. (https://thesilphroad.com/iv-rater) If it was +2, the level would have been 18, not 20. Based on that finding, my current belief is that either the trainer level +2 never existed [for trades, if below lv 20], or Niantic changed it in less than a month

But the experimentation you're referring to is post dec 2018 right? I think that was the time I did the tests previously, cause back then this was what you said. (and my tests were inspired by what you said :3 ) Was there any information that led you to believe that back then? I know I've seen silph road posts that mentions a + 2 level, but I've seen no associated images to back up that claim

no worries, probably takes time to get used to all the weird settings/fields. Happy holidays to you too

Typically, when you haphazardly change the origin game, the Met Location gets blanked out. For example, "(none)" is obviously an incorrect location. If you take time looking at the image, you may have figured out that your edits were the problem Just read through the details and ensure they're all accurate first, okay? :3 Look, I just imported the same event, and it was just fine..

Perhaps the error on PKHeX will give you clue?

Yeah you'll probably need a lot of mixes, to purge the old one out of memory. After all, the save doesn't have infinite memory. Alternatively, if you know which save blocks the data is imported into, you can just replace it with a save block that has yet to mix records.

Event has been officially released, seen people online doing redemptions. Our upload is now unhidden, and this thread is unlocked. https://projectpokemon.org/home/files/file/4389-japanese-release-movie-dada-zarude/

Which event did you download? Gen 4 shiny beast do have preset PID. For Gen 4, any shiny events have preset PID (if I don't recall incorrectly), because they don't have multiple PID options yet. Example here: PID-IV being tied doesn't apply to wonder card mons.

Lol, you replied just as I was locking the thread. Zarude Dada was distributed with multiple OTs. Don't know why you quoted me tho, cause that isn't my file. Anyhow, news thread ain't help thread. While discussions on a news thread is generally fine, this thread looks like it has devolved into a help thread. I guess I shall brace myself for all the "Zarude Dada where, trade me etc" threads. Anyhow, this shall be locked.

@SpringtraP-MasK please don't multipost anymore. I've merged your posts the last few times. You could always do multiquotes in the same post. In the meantime, I've removed the pk8 file, as people only get the codes in the movie theater. As it's only 3.57am in Japan, I doubt anyone has watched the movie. (unless they previewed it or something) I'll probably post it when I see a large amount of people redeeming it, or 10am JST, whichever is earlier. :3

I got the wonder card, but no point having the Zarude before people can officially redeem it

This gift will be given to players to commemorate the viewing of Pokémon M23: Coco. The serial code card will be given away to the moviegoers at various Japanese movie theaters. The movie starts airing in Japanese cinemas from December 25, 2020. It is unknown if Zarude Dada will later be distributed for non-Japanese audiences. (In high likelihood it would be, but there is no official confirmation thus far). Given the Switch is region free, this event will be redeemable across the world, if you manage to get a hold of the serial code. [Yes, I know this is old news. I just wanted to document the URL] Source: https://www.pokemon-movie.jp/present/index.php

I've never encountered that before. Maybe it's a thing on the new Luma versions, or perhaps I was lucky. In any case, good note, hopefully that helps people that also encounters it :3

I don't think it's implemented in PKHeX, simply because record mixing stuff it thoroughly not documented. As SpringtraP-MasK said, you can just keep mixing records until the trainer is gone.

Simple, play the game on a 3DS. (tho for real tho, honestly no idea what that's occurring to you. You not providing a save also won't help you either. We aren't psychic.)

That isn't the problem. PIKACHU/EEVEE that can Gigantamax, are unable to evolve. Heck, the game cannot recognize it as being from Let's Go. That isn't the problem. If you want it to evolve, you gotta remove it being able to Gigantamax. Let it drink Max soup at Isle of Armor.

It's possible the save you used (or the save you trimmed) weren't a proper save and were of the wrong size, hence the option wasn't there, and PKHeX wouldn't open it. As long as the importing and exporting option continue to work properly, you shouldn't have any problems. No worries :3

Sigh, I frankly do not know what is right or wrong with your system anymore. For now, try importing this into your game. then save in-game. <file removed due to file name> then use the export and import steps in the future.