Jump to content

theSLAYER

Administrator
  • Posts

    22828
  • Joined

  • Last visited

  • Days Won

    991

Everything posted by theSLAYER

  1. I got the wonder card, but no point having the Zarude before people can officially redeem it
  2. 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
  3. 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
  4. 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.
  5. 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.)
  6. 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.
  7. 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
  8. 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.
  9. The usage of trimmed here is slightly concerning. It makes it sound like you took the oversized DSV, edited it (downsized it), and renamed it .sav. when the game is running normally, and a save is loaded, you're supposed to export via this.
  10. Just to be clear, did that save come from your game play, or did it come from the start of the game (possibly prior to saving in-game?)
  11. Few things come to mind, so I'll just address the points 1. Probably something off with your Desmume settings. It shouldn't just ignore your previous save and start over. Is your auto save type Internal (as I showed a few posts prior) As double check your Path Settings to ensure it's reading and write to and from the right place. 2. PKHeX would not ignore the save, as long as (i) it's the right size and (ii) properly initialized. You could upload the save here, but I'm guessing it's probably not properly initialized. Make sure you save in-game, not just use state saves.
  12. you're at the start of the game. can you at least reach the first saving point, then saving, then trying again?
  13. There's probably something wrong with your settings. Desmume can open PKHeX edited DSVs directly. Maybe you're editing the dsv in a dupe battery folder or something. who knows. An alternative, would be to save the game, export battery file as .sav, import the .sav into PKHeX, then save the progress from PKHeX as a .sav (when done editing), then import battery file into the emulator, then soft reset. When you import battery file, make sure to go with this option:
  14. maybe you're importing it wrong? Close the emulator. Load the DSV in PKHeX Save the DSV Open the emulator, play the game. You don't have to "import" the DSV into the game every time, it just loads from the battery folder.
  15. Dude look at what I highighted on the left of my image. Go to that value in your file. Think of that as the address for the row of data. (it increases at every row: 0x0, 0x10, 0x20, 0x30, so on and so forth) Your address is much larger, which shows your file is much larger.
  16. For Pokemon Platinum: Regular DSVs end here. Anything past here should be removed. Nothing fancy, that's all I did to your previous file.
  17. I'm presently inclined to believe that as well: someone proposed that the level follows the wild encounter cap (trainer level + 2), and everyone else just took it as fact without checking for themselves. [Most people don't have low level accounts anyway] Do you happen to have seen any old video or photos that may help to prove this point? Just for verification, so that we can confirm whether to add downlevelling to PKHeX
  18. We're aware, and dealt with. Read: https://projectpokemon.org/home/forums/topic/58329-pokemon-go-level-15-shiny-legends/
  19. use a hex editor, and compare file sizes/hex offsets, and delete the extra data. (I use HxD) Then make sure your settings are correct. I feel like it should be this:
  20. Batch error? What you talking about. Luma error? PK3DS error?
  21. Sorry for the bump, but I needed to ask you about the previous method of trading for low level legend (or any raid boss, really). Can you recall when was the last time it worked for you, and you got any screenshots of date + ball on the mon? (just wanted to figure out when they changed the mechanic >< )
  22. No idea why your save file size changed. Could be related to your emulator settings. Anyhow, all I had to do is cut away the excess data. <file removed due to file name>
  23. you should load a gen 7 save first, or set the Option for default blank save to be gen 7.
  24. If I'm not mistaken, PKHeX checks date caught in, ball caught in, met level. So if you're sure those are correct, then it's legal.
  25. In relation to AR->sav conversion, it's merely about how AR saves may be hard to convert to a usable save, or the conversion process isn't direct. I don't think there's any risk in any other sense, as long as you can get a few proper stable dumps. (restoring a corrupted dump will corrupt your save, so make a few stable dumps beforehand)
×
×
  • Create New...