Jump to content

Kaphotics

Helpful Member
  • Posts

    6897
  • Joined

  • Last visited

  • Days Won

    323

Everything posted by Kaphotics

  1. So long as you're resetting on the first encounter, you should be ok. The way it works is that the game randomly generates the Opposing Trainer's ID/SID and uses that for shininess rather than your own. So if it appears shiny when you battle it, it's shiny for the opposing trainer and not you. Only when you capture it will your ID/SID be applied, and then you'll see if it's shiny or not -> reset. If you kept this up you would eventually find a shiny shadow pokemon.
  2. All gen V events are checked against a contributed Wonder Card. This event's wondercard data has not been contributed, so it's left to the user to check.
  3. PikaSav doesn't export gameshark codes, but it just edits save files.
  4. OmegaDonut plans to contribute once the event is over. Yes, he has every language ROM on a flashcart
  5. Download PWTE 2.1 by Prof.9 == So far there have been 4 download tournaments and one secret relic tournament locked away in the ROM; I might as well explain where it's at and how most of the important stuff is stored. I spent a little bit of time figuring out enough to get meaningful data out like text and teams, nothing more than that... so here's what I've found so far. PWT download events are set into the save file in the latter half along with all of the other downloadable content like mystery gifts. The tournament region is 0x7A000-0x7DFFF, for 0x1400 bytes for each tournament * 3 tournaments. By just looking at a downloaded tournament, it's hard to visually see the general structure via a hex viewer because it doesn't display Japanese characters... for visual help, you can use /a/2/5/8 from B2/W2's files, as this was their hard-coded test tournament that has a bit of English text (and wasn't removed for retail release). 0xA-0x54: Tournament Name ~afterwards, there's text for describing the tournament PKMs are set up to be as compact as possible, skipping nonessential stuff kinda like battle pkms. 52 bytes per PKM (0x34), one after another to make 6. Structure of PWT-DLC PKMs: 0x0-0x1: Species 0x2-0x17: 11 character namefield (after names, they are usually 0xFFFF aka terminators, not characters) 0x18-0x19: Held Item 0x1A: Shiny Flag (00 or 01) ~ unconfirmed, hasn't been used except for the ROM tournament 0x1B: Ability 0x1C: HP EV 0x1D: ATK EV 0x1E: DEF EV 0x1F: SPE EV 0x20: SPA EV 0x21: SPD EV 0x22-0x23: Move 1 0x24-0x25: Move 2 0x26-0x27: Move 3 0x28-0x29: Move 4 0x2A: gender? ~ unconfirmed. may just be bitflags for stuff 0x2B: Nature 0x2C-0x2F: IVs (stored same way as pkms) 0x30: ??? always 0. might be secondary sparkle like N's 0x31: Ball 0x32: Current Level 0x33: Happiness 0x270: Start of Trainer 1 PKM1: 0x274-0x2A7 PKM2: 0x2A8-0x2DB PKM3: 0x2DC-0x30F PKM4: 0x310-0x343 PKM5: 0x344-0x377 PKM6: 0x378-0x3AB 0x3AC-0x3C1 - Trainer Name ~ not sure on the lengths of these 0x3CC-0x3DD - Trainer Class ~ as I haven't seen longer name/classes Trainer win messages or something afterwards, didn't care enough to determine how they worked. Next trainer: 0x650: start of trainer 2 0x654: pkm data.... 0x3E0 between each trainer block, always 4 trainer blocks (0x270, 0x650, 0xA30, 0xE10) 0x1400 next tournament... repeats... 0x1670 trainer 1... 0x1A50 trainer 2... etc. that's all I know, however there's certain bytes somewhere which make the game use other stuff in the ROM instead of the programmed PKMs or trainer name/class. I just wanted to get the important team sets out so I didn't bother figuring out the entire structure. === resources~ Excel Parser ~ paste in tabulated data strings into the proper cells. PKM related lookup tables from Bulbapedia & pkmcodedepo and character tables from here. Ripped Tournament from the region I mentioned above (7A000-7BFFF). "PWT Download" for the file extension naming example results from parsing stuff & (rom example)
  6. yes pretty much every wondercard gift mon (not manaphy) has xFFFF trash after the terminator to fill up the rest of the nickname
  7. spinda spots are variant based on PID so I'd assume the images display the spots as they would be in the game ComeMst2 is the Hometown lookup (game originated in) ~ なし = None, usually implies its hacked ~ 不明 = Unknown, as these ones weren't used to ID any game.
  8. Kaphotics

    Pokemon "STAR"

    0x87: 250 <= x < 256 135d
  9. NARC file order (CLICK THIS FOR HUGE LIST OF NARC LOCATIONS): Notable files for ROM Hacks: /a/0/0/3 - Story Text /a/0/0/8 - Maps /a/0/1/1 - battle backgrounds /a/0/1/2 - ZoneData /a/0/1/6 - personal.narc (pokemon editing) /a/0/1/8 - level up moves /a/0/1/9 - evolutions /a/0/2/1 - Move data (type, bp, etc) /a/0/2/6 - title screen /a/0/3/0 - Start Menu Sprite /a/0/5/6 - Ingame Scripts /a/0/6/5 - Move Animations /a/0/7/1 - Animated Trainer Sprites (front, vs) /a/0/7/2 - Animated Trainer Sprites (back, send out) /a/0/9/1 - Trainer Data /a/0/9/2 - Trainer Pokemon /a/1/2/4 - Egg Moves /a/1/2/6 - Overworlds /a/1/2/7 - Encounter Tables /a/1/6/3 - In Game Trades /a/2/6/7 - Trainer Mugshots /a/2/7/3 - Hidden Hollow Encounter Table /a/2/8/2 - PokeMart Data /a/2/9/1 - PWT Board Trainer Sprites /a/2/9/6 - Pokedex Ingame Locations /a/0/1/6 indices and structure (personal.narc): Encounter Table: Now has 135 locations. Here's their entry->ingame location: Poké Mart Locations: Credits & Thanks To: personal.narc identification and structure: Codr and magical Location Map of encounter slots: xfr File identification: Kaphotics, magical, Bond697, Codr, veekun, Sanky, Jerry, Andibad
  10. Swarms are currently unsupported at this time. We're waiting on the possibility of that data being found in the ROM rather than just adding by hand.
  11. it's probably checked by the ingame script without referring to the text file then.
  12. the same shiny prevention is still in place from BW; since it could be shiny in BW1, kyurem can be shiny in B2W2
  13. This is not a "why are my hacks failing" thread. It's to report legitimate Pokemon failing the check; not for hacks.
  14. We can see every private Pokemon. Found it anyways, it's a hack. Pokecheck only displays the PP amount that is dictated by the PP ups, not the current amount of PP (which is 35).
  15. met locations are shared between the two games it is telling you that you loaded a B/W or B2/W2 save, as opposed to DPPtHGSS
  16. (B2W2 Keldeo skin) pokecgear doesn't display it (different format) do not try to add this in to a BW game or B2W2 -- there are no editors that will do it right now. keldeo2..zip
  17. Again, Pokecheck uses wondercards to check events. Since Gen 3 didn't have wondercards, it is up to the person checking to verify that their moves are legal. Making a table with all the special moves for gen 3 for exceptions is an annoyance and instead should be evaluated on a case by case basis by the user, not the server.
  18. No. Event checks are against valid Wonder Cards, not a handmade database. It's up to the person checking to make sure it's a valid move. edit: But seriously, that thing is hacked. 31/31/31/31/31/31 unknown GBA PID + 508 EVs you can't fool me.
  19. It's an event with a special event move, but Hacked / Event only (298) doesn't suffice? nah.
×
×
  • Create New...