Taku86

You can use a NDS and a flashcard with this tool.

Oh, great article! It’s a shame that no player is willing to preserve those Pokémon...

So... we know for sure that someone has a legitimate copy of this Pichu but no one has dumped it? EDIT: it seems there’s a tweet from 2014 where a user shows an Absol with OT カイチョウ and TID 31031. At this point, I believe your assumptions are correct and that this Absol could indeed be the genuine one. Source: https://pokemonhistorian.com/heroic-hoenn/stamp-absol/

On my Pokémon Sapphire cartridge (live battery), the two bytes generated for Mirage Island don’t seem to match the progression of the RTC. According to my save file, 8965 days should have passed, and based on this list, Mirage Island should show the value FD00. However, I’m seeing D98D instead. In the past, I used this save file on an emulator, and I think that may have desynchronized the RTC-related data on the cartridge (cartridge's RTC is currently set to today's/thread date, by the way). In fact, I know for certain that I started this playthrough on September 9, 2023, and I shouldn't be seeing 8965 days. Is it possible to resync the RTC values to reflect the actual passage of time and make it so that, as of today (the date of writing this post) exactly 680 days have passed (from September 9, 2023) and the correct Mirage Island value appears?

@autofire372Yes, I have, but it's such a minor problem that I've never looked into it to be honest.

@Alex_Tanuki That doesn't seem to be the full log

@Kaworu Considering that Winetricks installs first the 32 bit version and then the 64 bit version of .NET, if Fedora doesn't have the 32 bit libraries the process probably gets stuck there at the beginning. PKHeX only needs the 64 bit version. Try to manually install it, it's also in the OP

Could you be more specific? What error do you get? Post the logs.

Thanks, I've added this to the OP. If anyone else can confirm this fixes the problem, that would be great.

I'm using PKHeX on two machines, one with LXQt+OpenBox (running on X) and one with KDE Plasma (running on Wayland). I've never experienced this issue and I'm unable to reproduce. I've also tried to move them to different desktops, but it still works. Wine version 10.2 and .NET 9.0.2 here.

@Blood-PawWerewolfThread updated with the latest version! And yes, it works indeed

@ErFuyl What new version are you referring to? If you mean the development build then you need to install the 9.0 version of .NET Desktop Runtime, as it looks like PKHeX has been ported to it (I'll update the OP only when the stable version will be out).

9.17 is higher. In the third log file there's a line which shows the path of an Arabic font. My question is: did the installation of .NET work? Was it on a clean Wine prefix? Also, post a screen of the empty title bar please.

You don't need Wine 9.3 in particular, it can be a newer version too. 9.3 is only the version that first included the patch needed to run PKHeX. Quoting the OP: be at least on version 9.3 (or higher). I'm on 9.16 for example. You should use whatever version is shipped by your distribution as long as it's ≥9.3. Post the terminal output. EDIT: saw the logs you attached. I don't see anything wrong with Wine. Did the .NET installation run fine? Are you perhaps using an Arabic font on your system (saw that on the logs)? There might be something wrong with your fonts configuration and this is preventing PKHeX to load. EDIT2: @hongtm77 sorry, I forgot to reply to you as I haven't been home for a while. Did you solve your problem?