Leaderboard
Popular Content
Showing content with the highest reputation on 11/28/24 in all areas
-
Hello, this is my first contribution and post here in this community, I hope it is the beginning of something wonderful for everyone. I guess this can't be the right section, I've been looking at the sections for a while, and where contributions like this ``create --> file download --> in-game series --> generation 9´´ are, where there is a post of SWSH Fashion Block under generation 8. I hope the administrators of the site change the category of my post or contact me before deleting my post, and please tell me where to do it correctly to add my contribution, or how i post in download section (I think maybe i need more rank first in the forum). This data block contains the 151 unlocked sandwich recipes for pokemon violet or scarlet. You just have to import the .bin file inside the data block. File name: ---->29B4AED2.bin<---- Block data name: ---->Object KSandwiches<---- A fast screenshot where you import the block data: Also you have detailed guide on this web. You can follow any block importing guide but always remember your block data name and file name dont do with the guide block data and file names! ---->https://projectpokemon.org/home/tutorials/save-editing/gen-9/<---- And if this is useful for you and worked like you expect, please post your feedback, thanks, if you have any trouble with it, post your feedback too to see how i can help. 29B4AED2.bin
1 point -
Experimenting with trading again, here's my guess (until proven otherwise) I reckon there's 3 rules: Light blue - SM Origin <-trade-> SM receiver = OT reflects origin, based on origin language Light green - USUM Origin <-trade-> USUM receiver = OT reflects origin, based on origin language Pink - SM <-trade-> USUM [or vice versa] = OT Sun variant, based on origin language The way rule 3 (or what I'll like to call crossing the Ultra/Non-ultra OTxReceiver barrier) acts is though both sets of games are different generations... Also, it appears the 'Korean' interaction is real, however I personally reckon that the report from the Redditor came from them observing rule 2 jumping to rule 3 (if you take a look at my table, the last 3 trades were the same Mew, and the OT changed when it crossed the Ultra -> Non-ultra OTxReceiver barrier. ) That means there's likely yet another invalid character or combination in Korean OTs (lol) I think there's enough trades here for you to test and prove/disprove. (And before anyone jumps in, yes, some origins are not possible for the events. I'm testing what happens to a mon with said origin with invalid OTs.)
1 point -
Sorry, don't know where else to put this information: The "unkown" value under trainer info is actually a bit array (where a combination of 2^n values, or digits in binary, determine different properties) which impacts how smart the trainer's AI is, probably things like whether or not it can switch out in poor matchups. Found out the hard way that 128 (1000 0000) NEEDS to be raised in double battles, otherwise the trainer's pokemon attack each other. Many difficult trainers have a value of 7 (0000 0111) and a few have a value of 135 (1000 0111, which is 7+128), so it makes sense that 135 is the maximum intelligence setting.1 point -
Version 1.0.0
1417 downloads
Hi, guys if some one want's to have a complete curry dex in couple of minutes, here is how. Open your save in PKHeX, go to SAV/Block Data, choose "*Object KCurryDex", and import the correct .bin file to your game: "151 Charizard Class Curry Dex - Sword Cinderace and Dottler 12.13.2019 Hammerlocke Hills.bin" "151 Charizard Class Curry Dex - Shield Inteleon and Dottler 11.18.2019 East Lake Axewell.bin" You also need to edit the "campin" and "cooking" under Trainer Info of PKHeX, to make it legit, for my Data Blocks it should be: Sword - 2 times "campin" and 302 times "cooking". (cooked with 2 Pokemon all 151 curries twice). Shield - 2 times "campin", and 302 times "cooking". (cooked with 2 Pokemon all 151 curries twice). And also for your LEAGUE CARD "Curry Dex" entry, edit the "recipe" value to 151, and update it in a pokemon center. Save, and restore the save file back to your game. If you want to personalize your curry dex then, open the .bin file in a HEX editor and use this as a guide: In my opinion just edit: 1st Pokemon you Cooked with. 2nd Pokemon you Cooked with (But leaving Dottler is fine because you need to cook with a small pokemon to unlock the Small size). 1st and 2nd Place and Date of Cooking (Best solution to make them the same place and date for all 151 curries). In order to get your pokemon, place and date of cooking, just cook one curry with the chosen pokemon in your chosen place, or choose from existing one in your original "*Object KCurryDex", and replace all entries in my file (Use the "Replace" function in your HEX editor, to make it faster). And that's it enjoy. PS. For those who want to change the date here is an example: The date code is "77 13 0C 0D" (12/13/2019) in the "1st and 2nd Place and Date of Cooking" strings: HEX 77 = 119 (the game reads it like the 20 from 2019, for some reason, maybe it's like 1+19=20). HEX 13 = 19 (from 2019). HEX 0C = 12 (month). HEX 0D = 13 (day).1 point
