Leaderboard
.thumb.png.383b25a8dfff428119c1f5570d88cce6.png)
Popular Content
Showing content with the highest reputation on 04/16/21 in all areas
-
Version 1.0.13
18672 downloads
Pre-HOME HOME Non Shiny Living Dex | Shiny Living Dex Switch Core Living Dex (Regular and Shiny) Pokémon GO Transfers Key description This page hosts Pokémon that were obtained from direct GO -> HOME transfers. This page was previously online, but has been brought offline for maintenance. Available files at the moment (includes Alolan, Galarian, Hisuian, and Paldean forms, when available in GO. Exclude held item forms and battle forms, such as Megas) Living Dex Exceptions Kanto Ash Cap Pikachu - while it exists in main series, not transferable from GO Johto No exceptions Hoenn Spinda - released in GO, but not transferable. Due to Spinda patterns in GO not adhering to patterns in main series, unsure if it will ever be transferable Sinnoh Rotom (Fan) - not released in GO at time of writing Manaphy - not released in GO at time of writing Phione - not released in GO at time of writing. Given no breeding mechanic in GO, not sure how it would work too Arceus - not released in GO at time of writing Unova Lilligant & Zorua & Zoroark (Hisuian) - not released in GO at time of writing Kalos Vivillon (Fancy and Poke Ball) - not released in GO at time of writing Honedge, Doublade, Aegislash - not released in GO at time of writing Sliggoo, Goodra (Hisuian) - not released in GO at time of writing Zygarde - released in GO, but not transferable at time of writing. Volcanion - not released in GO at time of writing. Note that it is planned to be released in GO as part of the paid ticket for GO FEST 2025 Legendary Zygarde - released in GO, but not transferable at time of writing. Kubfu and Urshifu - released in GO, but not transferable at time of writing. Presumably related to current research of the season. Enamorus (Incarnate) - released in GO, have yet to be added to the archive. Enamorus (Therian) - not released in GO at time of writing To be updated Mythicals To be updated Description table last updated - 3rd May 2025 Usage This page contains archives that has files, which that extension(format) are: ph3 (HOME), pk8 (SWSH), pb8 (BDSP), pa8 (PLA) and pk9 (SV). They can be imported into various games via PKHeX. Example of usage, would be to fill up the GO's dex in HOME. Other Notes For this file to be transferable across games (via HOME) without any stats oddities, you cannot modify any immutable values. Read here: Relevance of HOME tracker Last Word: Despite these Pokemon being legal, I still need to say this: ProjectPokemon.org is not liable, if you somehow managed to get yourself banned with these Pokemon. Also, don't be stupid or don't do stupid things. I can't possibly give every directive or comment on every possibility. Be reasonable, alright :31 point -
I think most fans who've played Stadium know that nicknamed Pokemon can have different colors. But why? How? After a lot of time and effort, I've worked it out - well, mostly! Since PKHeX was critical to my success, this seems like an appropriate place to share my results. My research was thorough and I made sure to explain things in a lot of detail, so the full write-up is in a Google Doc here. But if that's TL;DR (I get it, life is short and the internet is full of content) here's a summary: The ASCII values of a Pokemon's OT name and nickname are added together, along with the values for the two bytes of its TID. The last byte of the result in hex is what I call it's name value (NV). This is converted into a hue adjustment based on a Pokemon's specifically programmed hue range - an NV of 0 is its minimum hue, and FF is its maximum. It'd take a hacker (I'm not - can't program my way out of a paper bag) to get the exact formula, but I've worked out an approximation that gives results that are at least super-close. Like, closer than the human eye can probably distinguish. I put my formulas into this spreadsheet which can be downloaded or copied to your own Google Drive to find the hue of your own nicknamed Pokemon, but to make use of it you'll need to read at least some of the document. I've also worked out how Smeargle's DVs effects its colors and why shiny Pokemon can look so different in Stadium 2. It turns out almost all shiny textures are modified using the HSL (hue, saturation and lightness) colorspace, just like the nickname palettes (which only use hue). I wrote down each Pokemon's hue range for nicknames and the HSL values for its shiny in Stadium 2 here. I got these using jrra's patch to re-enable the debug menu in Stadium 2, which has all this info and more. Finally, I've taken screencaps of every Pokemon's minimum and maximum colors, plus some in-between if there's a big range. For fun, I also took a handful of art, sprites and models and altered them using GIMP's HSL editor to create Stadium-style nickname colors and shinies. My gallery of screencaps and modified art can be found here. I'm open to comments, questions, and any other feedback. Hopefully some of you will find this interesting, and if you like what I've done, I welcome you to pass it on to anybody else who might like it! I'm also totally cool with my research and pics being freely distributed and used to edit stuff like Wikis so long as credit is given when possible.1 point
-
At that point, the question becomes "y tho"; most edits don't need the time investment / bloat that a GUI requires, if they're just simple one-off edits that not many people use.1 point
-
@BlueGold Based on what you linked, let's take a look: It shows that the Trainer's House Trainer's mon isn't even full data, it's just some bytes. In otherwise, it doesn't contain the full Pokemon data, unlike box or PC data. As such, I see your suggestion as infeasible/pointless, in terms of data extraction. If your goal is merely to edit the mons you get to battle, then maybe that makes sense.
1 point -
Sorry for the necropost, but I think I won't be the only one stumbling into this problem and searching got me to this thread, which doesn't have a clear (user friendly) answer to the issue. Problem is that project64 (and probably other n64 emulators) don't round up savefiles to full n64 savetype filesize. In the case of pokémon stadium 2, as Kaphotics stated, project64 creates a 0x1FF00 file (130816 bytes) while PkHex expects a 0x20000 file for (USA/INT) stadium 1 and 2 savefiles (131072 bytes). One can manually solve this manually with any hex editor or file padder. I went ahead and coded a simple app that will pad n64 savegames to the nearest savetype (depending on the input savefile). Originally I only intended to make it pad the stadium savegames, then I saw Japanese Stadium 1 (or stadium 0) uses a different savetype, so I went ahead and made a more general app that can work with any n64 savegames. Just drag and drop a savefile onto the .exe file and you will get a file with the "_pad" suffix added to it. n64savepad.zip1 point