Codr

You now get a closed thread. Edit: I have to say that it's utterly appalling that people like you, whose only concern is with getting what they want, exist.

Are you going to pay me? Then I'll take the time to spoon feed you information, since I'll be getting something out of it. No? Great, spend some time and figure it out. Do you get it now? You're probably beyond clueless as to how much time has been spent on PokeGen, and are seemingly unappreciative as quite a few are. You just want more and more done for you. Clearly I'm the one doing something wrong.

I could've said nothing at all and left you wondering if you were missing out on some feature that PokeGen doesn't even have. With some time of your own, you could actually use PokeGen to FIGURE OUT how to copy the save file data yourself. It's not my responsibility or obligation to explain this to you though.

Not with PokeGen itself, but manual save file editing, yes. No, I'm not going to explain how.

So you're saying that the problem apparently occurs if the Pokemon are put into a(n) HG/SS save file and that save file is loaded/saved a few times with no modifications whatsoever? That's very, very hard to believe with the current design. If you can find a way to reproduce the problem, and provide the steps you took to do so, I'll look into it.

Yes. It'll infest all of your data files and rewrite the same data to those files, making them identical, but you'll know that the data was changed. Therefore all of those files become worthless and need to be deleted. After that, it hops out of your hard drive and into your Pokemon game catridge's ROM and removes all code related to PID randomness. All following PIDs will be written as 0xBADBAD. Code will also be injected to overwrite all existing PIDs in the save file with that value. Finally, it changes your character's name to "CARESABOUTPIDS", by modifying the game code to allow that length of a name. Edit: I feel pathetic typing this because it shouldn't be necessary. There is nothing in PokeGen that could possibly affect your computer or DS in a negative way.

3.0.0b30 FIXED: Dragging multiple .pkm files onto the program would only set the modified flag for the slot under the mouse pointer upon completion of the drag. Any slots without the flag set don't get written to the save file. (Found by Domokun.) FIXED: Dragging multiple .pkm files onto the program would only update the icon for the slot under the mouse pointer upon completion of the drag. FIXED: Box count/selected count wasn't being updated properly when dragging Pokémon around. FIXED: Delete All wasn't setting the modified flag on deleted Pokemon, resulting in them not being written as deleted to the save file upon saving. (Found by DiscordDave.) FIXED: The update system was still capable of failing to download files, resulting in a download dialog box with a blank progress bar. (Found by Delta Blast Burn.) FIXED: Loading a non-generation-5 save file on startup resulted in the PID Finder and Code Generator windows containing generation 5 data. (Found by Delta Blast Burn.) FIXED: Switching target games to anything but Black/White would cause the Pokédex dialog to gain focus.

What settings did you use?

Ok, that did it for me too. I'm looking into it. Edit: It's fixed for the next release.

From program startup to the PID problem, I'll need exact steps of what you're doing. As for the language file, which language? Edit: I've verified and fixed the update problem, but I still need detail on the supposed PID Finder issue.

Then I'm left to assume you're using an older version, despite the fact that this was never reported with older versions, and the fact that it's not happening for me. The update issue WAS reported with older versions.

The PID Finder doesn't automatically set the species unless you click the "F" button next to the PID editbox. It doesn't do anything to the species upon clicking "OK".

Yet again it attacks. Verified and fixed. Thanks.

As much as I'd like to give you an answer to that, I don't want these topics being discussed in this section anymore.

A quick look seemingly verifies this. It figures that this damn value would be forgotten yet again. (One that indicates whether or not a Pokemon has been modified and therefore gets written to the save file.) Thanks for the report. Edit: It's fixed for the next release.

Ignoring the awkwardness of your post... I sure hope you're not asking for more discussion on "legality" topics.

This can now serve as an example to others of why myself and some others are always so negative and don't want to help.

There's no reason to do this, but it isn't the problem. You're doing absolutely NOTHING between saving in-game and loading the battery folder's .dsv file in PokeGen? Because I don't believe you. Convert it with what? Why? Aside from you doing something you shouldn't be that you conveniently aren't providing information about, the only other option I can think of is that you have a modified ROM. The kind of modification necessary to change save offsets is something I've never heard of anyone doing.

If you go in-game, save, then immediately try loading the .dsv file with PokeGen, does this problem still occur? Better yet, does this exact save file you uploaded work perfectly in-game? Edit: Because Desmume treats it as non-existent for me. Examination of the party data within the file shows that it's all in the wrong spot as well. I'd imagine other data is also misaligned. Desmume wouldn't do this alone.

That's exactly the size it's supposed to be. Desmume has no settings that I've ever seen to modify the file format. The save file works in PokeGen, so I have no idea what you could possibly be complaining about. You could also try posting the file in the event that there's somehow something wrong with PokeGen.

Check the file properties and post the exact byte size of the file.

Why bother when Desmume puts out a compatible file automatically...? Regardless, CobraKill should have searched first, because this has been answered MANY TIMES. Edit: CobraKill, what's the file size of the .dsv file in the battery folder?

Yes, there's a fix. It involves actually looking at the information available to you on the Pokedex dialog.

It's possible, but I wouldn't expect it any time soon.

It's intentional. The games don't care about what exists after the first \FFFF.