theSLAYER

Nice! The legendary beast with stats being stored in memory was something I was interested in a while back. Context: Someone used an anti-shiny locked cheat to SR for a shiny Zoroark. An oddity happened, where the legendary appeared shiny, while the Zoroark did not. I thus theorized that it must have had stats and appeared in memory, hence why one PID was shiny and one wasn't. I mentioned it here, a few years back. Tho I lack the technical skills (when I first theorized it), so I never thought I'll live the day to see it confirmed. What offset in the RAM dump are these mons located at? Glad to see it finally proven :3 Thanks for the hard work! edit: Until I find a different video, this one shows how the Beast could be non-shiny, but the Zoroark be shiny: https://youtu.be/WGILBbMUFvU?t=164 edit 2: found a video with what I was talking about: https://youtu.be/6u5qsjRDj_g?t=127

at what point of the journey did you first use PKHeX?

no problems :3

I'm asumming the ROM is your own backup. Yes. to keep it legal, make sure they do not have weird characters in the nickname and OT. PKHeX presently has issues translating those to different gens, and is working on it. So one way around it is to use plain simple names. Yes. Gen 3 and Gen 4 have a known PIDIV(etc) relationship, and Gen 5 have certain PID to OT gender relationship. However, with current model of PKHeX, it would flag you if it's illegal.

did you restore the edited save back into your game after you edited it?

they probably want it for Sysbot.

Probably. I can say for a fact that Flashcart G4 Pokemon can receive mons from retail G3 carts, because I've done that very thing myself in the past. Pal Park works, and Dongle Method would activate. However, I cannot guarantee that it would occur for you, since there may be some factor on your end we don't know about. So all I can say is "it'll work as long as all is as you claim." One good way to determine if it will work, is: does Dongle Method (Slot-2 wild spawns) appear for you? Also, is your G4 game and G3 game both of the same language?

G4 can be on R4. G3 has to be actual retail cart or very very specific flashcart. (this probably won't work with G3 repros, cause their save is somewhere else the G4 game isn't expecting)

To think I was nice to you and didn't warn you or anything (yet). User sent me an intentionally offensive DM. User is now banned.

Piracy. Don’t ask again.

Most of the ones I've vetted based on the ones that were seen and previously on-site. They were vetted for encounter slot and PIDIV, route info, nature, level etc. So only the named three didn't hit that requirement. But yeah, debug-ROM forced encounters would make sense. Still, I'm perplexed to why people want in-game mons..

Even in that sense, I'm not sure if PKHeX into other data associated. For me, I have an excel spreadsheet with some PIDs we've came across, so I would know right away whether we've seen them before. XD

Oh sorry, I missed that part about the trade. Well the thing is, the upside is that the Shellder matches the correlation of an in-game mon, so it *could* potentially be a Jeremy mon. But the downside is, given it matches the correlation of an in-game mon, anyone could have caught a Shellder that matches the known details, then just swapped on the correct OT, TID, SID. So it's usually a good sign if it's a Jeremy mon that matched the details + was on a site/link like, for the past 10-15 years.

I'm not going to look at all of those, because chances are we've already vetted them. The ones that we have available, are here: So if your copy differs from these, not the real deal. As for Slowpoke, Shellder and Sandshrew, I would take another look at them. Tho chances are, they are not the real deal. Jeremy's mon are all in-game mons, and to simplify the technical aspects, they have certain characteristics that one can tell that the copies in circulation were hacked. It's possible those 3 are of a similar situation, since we've browsed the net for such files. Edit: We've seen this Sandshrew and Slowpoke before, they were dismissed as fake. Looking into Shellder again. Edit2: What's the original link for your Shellder?

It's a server based game. For most server based games, all you have control over is clicking respective buttons, which the action would then be sent to the server, then the server returns the result. So unless the server accepts any command, or that the API the phone uses and the server uses has been leaked, then; the game cannot be hacked. (Basically, it is not as if a save is stored on your phone. Cannot perform save hacking like mainline games) Also, as a matter of warning, do not "share" the place where you 'paid for an injection service'.

I'll advise against that. You might have faulty event flags to begin with. I'm under the impression that in order to do what you want, I want to import back the old save flags.. Which might be faulty, and may cause other crashes down the line.

@Moonlight seems reasonable enough. Since it's not you thinking "oh my mon was only legal on older copies, so my save has to go through an older version to be legal bs", I don't mind showing you where. (if it was for one of those misunderstandings, I would try to clear it up..)

Mind telling me why you need an older version?

So I got info regarding this. It's not that Wiimmfi's wonder card is special or anything. What is important is the act of receiving it. (or alternatively, injecting it into the correct spot, which can be done with BlackShark's code) The person who shared these screenshots with me used the premade Lock Capsule above (instead of the Wiimmfi one), then received it via Slot-2 Distribution. Despite it being a regular looking card in code, it still became the fancy looking card, with the View Lock Capsule status text being there. edit: For the record, the PCD above didn't do anything special. Didn't utilize a special type or anything. Just switched the type to item mode and set the distributed item to Lock Capsule.

I'm guessing you missed my edits in the previous post. (to be fair, I think I was editing when you replied.) Anyhow, it appears I was right: PKHeX was trying to assign it an encounter/gift that uses no PID type, due to your Pikachu having no PID type. (Based on your Pikachu, it appears you broke PIDIV because you edited all the Pikachu IVs to 30) The issue goes away when I make the PIDIV valid. (this was done on your Pikachu)

upload the file. Tho looking at your screenshot only first one treats it as a Pichu (the levelled up one). The second one treats it as a Pikachu (the non-levelled up one). Anyhow, I'm under the impression that this is due to your PIDIVs being incorrect (PID Mismatch), and PKHeX is trying to assign a proper encounter/gift to it. (look at the underlined encounter type. only one is pichu. And look at PID type, it should not be None) Perhaps report back if it still reports this, after the PIDIVs issue is fixed.

Consider using this plugin with your PKHeX.

yeah that happens when you turn too much codes on at the same time. I had something somewhat similar happen to me in FRLG a long while back. I think all my items became balls, including key items. It's nice to have infinite items in Key Items bag, but it replaced some crucial key items, which were a pain. Beyond what was already said about using PKHeX, if you can't get your save to use it (tho most older ARs should have a save dumping feature?), consider looking for a code to wipe your bag.

That error message covers a lot of different user issues. It generally means 'you're using the wrong file with PKHeX'. That's the only thing in common between you and the OP. In the OP's case, it's because they were trying to extract a save the mainstream route while using a repro cart. (Repro cart needs different ways to extract saves). In your case, it is because your save size isn't configured properly in your emulator settings. Your solution would not work for the OP, and the solution to OP's problem would not work for you. Still, this is rather out there, but I hope people with MyBoy settings issues similar to yours would see your post and resolve the issue on their own. :3