Jump to content

SciresM

Innovator
  • Content Count

    214
  • Joined

  • Last visited

Community Reputation

43 Excellent

About SciresM

  • Rank
    Researcher - ROM
  • Birthday 09/09/1990

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. please join in my club

     

     

  2. hey man how is it going

  3. Pretty sure you should be able to just swap the entries around if you're using a CFW that has RO's hash check patched. Pretty sure luma does this by default? Also you can replace the CRO pretty readily with luma's layeredFS thing nowadays.
  4. I am pretty sure it's possible. Also..."compile it using a compiler" -- this is....pretty irrelevant to the process of making a tool. The compiler is literally an afterthought, as is the IDE used to write it. The code itself is all that you should really consider. (And PKHeX already has C-Gear code, I think, as I said.)
  5. Pretty sure PKHeX supports C-Gear stuff nowadays, doesn't it? (Also, not sure why the IDE matters, or why we'd not just use VS..)
  6. I used your Gen I editing program Rhydon to edit my Pokemon's DVs, level, moves, etc. on my Pokemon Yellow Version for the 3DS Virtual Console. Pikachu does not follow behind me anymore. Any help?

  7. PKHex's sun/moon support already includes support for Gen VII mystery gifts.
  8. I added support for editing Battle Revolution save files to PKHeX last week.
  9. ...did nobody read my post that said they're Big Endian PK4s? That's a well-documented format....there's no need to research how they're stored, I already said that.
  10. Hey, there. I've started the process of implementing Gen II support in PKHeX, following my just adding Gen I support. I'm currently working on implementing save file loading/reading for GSC saves -- this is easy for English games, because bulbapedia documents save offsets well for those here. However, Japanese offsets are not so well-documented; I'd like to ask, then, if people could help out by documenting them while I work on implementing the other features required for PKHeX's Gen II support. The Japanese offsets that need documentation for full PKHeX support (both GS and C need offsets): -TID -OT Name -Daylight Savings -Time Played -Player Palette -Money -Johto Badges -TM Pocket -Item Pocket -Key Item Pocket -Ball Pocket -PC Item list -Current Box Number -Pokedex Owned -Pokedex Seen -Player Gender (Crystal only) Strictly speaking, Checksums also need their offset located, but I can take care of that when the time comes.
  11. Someone just has to make an editor, really. As I commented on reddit, Pokemon are just 140-byte unshuffled, Big Endian PK4s. Also their checksums are different, but you could surely reverse that with dolphin if you were so dedicated.
  12. That was, indeed, the case, but then I also wasn't interested in adding Gen 1 support to PKHeX
  13. I wouldn't bother -- I will be adding Gen II support to PKHeX following my finishing Gen I support. I'd also like PKHeX to be "the tool" -- and so the more people wanting to improve it the better
  14. I mean I'm not opposed to updating it, but I'm also not really sure what there is to add? I'm pretty satisfied with Rhydon. Behind the scenes, PKHeX may or may not get Gen I/II support, but I'd bet against it.
  15. Yeah...I'd be happy to implement it, but I can't think of any sane way to differentiate them?
×
×
  • Create New...