• Our software update is now concluded. You will need to reset your password to log in. In order to do this, you will have to click "Log in" in the top right corner and then "Forgot your password?".
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

Recent content by Chaotix

  1. C

    Code: Complete FireRed Upgrade

    make.py is the file you would edit for that. Is the default not fine for you? It should have been like "OFFSET_TO_PUT = 0x900000" originally. If you want to put it somewhere else then make the 0x900000 an offset that has a decent amount of free space.
  2. C

    Code: Complete FireRed Upgrade

    1. You're changing the wrong file. Edit the offset in make.py for where you want to insert the CFRU. 2. Still haven't tried that stuff myself yet so I can't comment on it. 3. https://pastebin.com/QpnHyQpJ this has information on setting up Advancemap to work with expanded Pokemon. Edit: For #2...
  3. C

    Heya Spherical! I was playing though Gaia for the first time today and I noticed you had working...

    Heya Spherical! I was playing though Gaia for the first time today and I noticed you had working grass animations for more than just regular grass. Like your snow grass anim was perfect and not just green like the regular grass. Do you have any information on how that was done?
  4. C

    Code: Complete FireRed Upgrade

    I have not actively tried to exclude pokemon from being added with DPE. I just re-ordered the pokedex for the ones I wanted to use in a regional dex and left the others alone. I imagine if you want to actually exclude species you'll probably have to edit a lot of files and remove the front and...
  5. C

    Code: Complete FireRed Upgrade

    The build two Roms, one DPE and one CFRU and copy the bits of data over is a good idea and all for actual hack work. It lets you modify that base file with things before building the CFRU on top of it to test changes; but for just making sure stuff is working to start I'd instead recommend...
  6. C

    Code: Complete FireRed Upgrade

    No you should have the national dex size as the last regular dex entry. Like if Melmetal is the last one it would be 809.
  7. C

    Code: Complete FireRed Upgrade

    Buggy in what way? For me movesets and abilties are usually wrong among other things in G3T; thats because G3T wasn't made to handle longer ability names and expanded movesets. If your evolutions are wrong then the EVOS_PER_MON in CFRUs config.h don't match DPE causing some problems. By default...
  8. C

    Code: Complete FireRed Upgrade

    You have to create these items or change what they evolve with. By default it looks like everything needing a new evolution item has it listed as ????? to start so you just have to change it to a different item.
  9. C

    Code: Complete FireRed Upgrade

    From what I've tried HTE is actually better than G3T for editing trainers with CFRU. I didn't need to change any offsets that HTE reads to make it work; just open the BPRE.ini file and changed the number of pokemon (1102) and number of moves (810) and it was good to go. Uhh whats up with the...
  10. C

    Code: Complete FireRed Upgrade

    I just did a search of the CFRU for Sandstorm and I found in src/damage_calc.c a section for Sandstorm sp. def increase. Also I checked the official information on sandstorm since I didn't know about the sp. def increase and it only increases the sp. defense on Rock types, Steel and Ground do...
  11. C

    Code: Complete FireRed Upgrade

    Do you have BPRE0.gba in the main section of the project? Thats the file it uses to do the changes; its just a base Fire Red 1.0 that you re-name to BPRE0. If you have one there and it is giving you that message you probably have it named BPRE0.gba.gba or something like that.
  12. C

    Code: Complete FireRed Upgrade

    The 'code' is just referring to all the data that the CFRU inserts. It's saying you can open scripts/make.py and change the line: OFFSET_TO_PUT = 0x900000 - if you want to change where it will put everything. By default there is nothing there in Fire Red so it is safe to use; but if you had...
  13. C

    Code: Complete FireRed Upgrade

    I haven't personally messed with Z-moves or anything like that but the types are in include/constants/pokemon.h. For example normal is 0x0, Fighting is 0x1, Flying is 0x2, etc. Just match the numbers there for making type Z-Crystals. Not sure about the specials ones still though, not enough time...
  14. C

    Code: Complete FireRed Upgrade

    They are in assembly/data/type_tables.s. I haven't tried to edit it myself yet but should be fine. In offsets.ini the repointed table is the label "gTypeEffectiveness".
  15. C

    Code: Complete FireRed Upgrade

    Look at the file config.h for CRFU, in there is a define for FLAG_SYS_DEXNAV. That is the flag you need to set with a setflag script to give Dexnav.
Back
Top