theSLAYER

same junk. are you sure you got a real cart?

You uploaded the same file, just renamed. Also, what you said also makes no sense. Anyhow, it's the same junk data. how did you obtain it?

why is the new save named that way? It looks almost as though it was generated from my fake cart program. edit: It's not a save. Did you extract it right? Just to be sure, for the real cart, you didn't dump the ROM then run it through my program, right?

Send me the save from the cart (from flashboy), and also send me the save from your bootleg cart. You can just attach it here, on your next reply.

Is it possible that you just.. state what proposed solution you have? After all, this is a forum. The post you leave behind might be up for years, and there's no guarantee you'll be around for years. By the time someone reaches out to you, you may not even be browsing our forum anymore..

Before we go ahead and restore the save to your retail cart, let's try something else first. Create save on the retail cart, then save in-game twice, then dump said save with the flashboy reader. Can the dumped save from the flashboy reader be opened in PKHeX?

how far did you progress into the game? did you save multiple times inbetween? edit: your save is effectively screwed. There's a repeating pattern of this more or less across the entire save. That pervasive pattern eats up even Pokémon. Given Pokémon is encrypted, having any change in the bytes make decryption practically impossible, and I can't even salvage Pokémon

Chances are, your save file isn't really a save file. Anyhow, so far you're just having issues loading your save to PKHeX for *any* use, unrelated to Cute Charm Abuse. Start a new thread and upload your save there.

This is the unedited save, right?

Disclaimer This guide would require some way of playing edited ROMs (such as a flash cart, NDS emulator etc). This guide assumes you already know how to dump your own ROM legally, and how to play the edited ROMs. As such, this guide will not entertain such questions, as it is not the point of this guide. This method works for any language'd variant of Diamond, Pearl, Platinum, HeartGold, SoulSilver, Black, White, Black 2, and White 2. Note: the shinies obtained via this guide will only appear shiny. When the save is viewed in PKHeX, and when shiny Pokémon (resultant of this modification) is transferred forward, chances are they will not be shiny. Additionally, this guide will not give you 100% shiny encounters. However, the shiny odds for these fake/temporary shinies are still higher than base rate, and may interest people that do not intend to transfer forward nor trade to vanilla games. Anyhow, we will not be providing any arm9.bin or modified ROMs, as linking to or providing data files extracted from ROMs are against our forum's rules. However do not fear, as the steps regarding how to extract the arm9.bin from your own dump and then re-injecting them, are included in this guide. The 3 easy steps: 1. Extracting the decompressed version of the arm9.bin 2. Performing the edit 3. Injecting the edited arm9.bin back into your game Extracting the decompressed version of the arm9.bin Performing the edit Injecting the edited arm9.bin back into your game Extra: Testing whether the modification works FAQs and Explanations: Sources (that I remember): Bond697's original work to increase the shiny xor threshold on Pokemon Black 2 Me expanding on Bond697's work to find a working offset for Black/White My explanation for why the shiny is fake/temporary Bulbapedia's page on Shiny Pokémon View full tutorial

So here's an answer I got from a dev: Sysbot doesn't write memories, however receiving a mon via trade does update it's memories. So the memory you got is probably due to you receiving it via trade.. edit: I was told how trading updates memories is how the game behaves normally. So if you want a specific memory, you gotta save edit.

If you uploaded the correct file, then it is probably sysbot that messed up memory. I'm unsure if it's limited to the server you are using, or the issue is present in all current versions of sysbot. In any case, this isn't a PKHeX issue..

I injected the Charmander you sent me, and the memory correctly says it grinned. Try receiving another one from Sysbot.

perchance could your next response contain the pk8? :3

Just a few lines of questions that needs to be answer: What is the origin game of that mon? Did you set the edits into the PC? Did you export the edited save from PKHeX? Did you restore the edited save into your game? Are you using EmuMMC/Emunand?

No worries. I made another minor edit. You can refresh the page and read it if you want

Hi, I guess I was editing my post while you were typing this. Refresh the page and read the edit I made, thanks

The latest version of PKHeX already supports GO Shiny Dialga. Your GO Dialga must have the correct date. PKHeX verifies dates. The range is literally in the error message. Make sure dates and levels and other details match the encounter details. Also, rather than make things from scratch, import from the encounter database. Also ensure you're at the latest version. edit: I reread your post, and it appears the issue you have is with Sysbot, not PKHeX (as in NOT issues related to making a legal shiny Dialga on PKHeX), my bad. I'm keeping my old content up for context (maybe it'll help others) Anyway, we have no control over the various copies of Sysbot out there, after it was downloaded by server owners. The server owner has to update their own version of PKHeX.Core (and various DLLs) that Sys-botbase relies on, to get the updated legality checks. So your file is legal, and PKHeX is working fine. It is just that the server owners need to update their system that runs legality checks. Alternatively, find a server that turns off legality checks.

@flaming.brockoli Same junk. Are you perhaps launching the game through another app or something? If one were playing the game normally, it should not be this sized, and that's the only explanation I can come up with..

Based on what you said, and a look at the garbage data, I doubt you ripped the save out properly. Read:

I find it hard to imagine that the game would randomly edit that data into your block. Are you absolutely sure only you played the game? Maybe someone claimed it in your absence? Yeah if you could get PKHeX load the save, and dump the block, I could help with its removal.

No worries. I know how to do it. Dump the Mystery Gift Block, then hex edit it, to remove the entry. I then asked you why do you want to do it.

well what we said handles the file you uploaded specifically. for anything else it may need different solutions. Anyway for other stuff just import from Encounter Database, then mess with the stuff from there. Don't create stuff from scratch

that wasn't the file you uploaded don't know what you are trying to imply. What we referred to is the file you uploaded.