Search the Community
Showing results for tags 'mystery event'.
Found 1 result
-
Hey there! Thank you for all the help from you guys especially @lostaddict, @BlackShark, @suloku and everyone who contributed their Mystery Events and Mystery Gifts. Now it's about time to share everything we have learned from the research. Mystery Event Activation RS: Section 2 - 0x03A9 - bit 5 RS: Section 2 - 0x05C0 - bit 1 (Flag for the NPC?) E: Section 2 - 0x0405 - bit 5 Notes: In Ruby & Sapphire Mystery Event can be activated by the NPC at the 1F of the Pokemon Centerin Petalburg City, right next to the PC. The requirement for the activation is beating the Gym Leader Norman and getting the Balance Badge from the Petalburg Gym. To activate it you have to tell him a specific phrase using the easy chat system. In Emerald Mystery Event can be activated by answer the questionnaire in the Pokemon Market. The only requirement is that you have received the PokeDex. The phrase that activates the Mystery Event feature is: Japanese: ふしぎ できごと わくわく ドキドキ English: MYSTERY EVENT IS EXCITING French: EVENEMENT MYSTERE EST PASSIONNANT German: GEHEIM GESCHEHEN IST JIPP!JIPP! Spanish: EVENTO MISTERIOSO ES DEMASIADO Italian: EVENTO SEGRETO È FANTASTICO e-Berry Data Structure RS: Section 4 - 0x02E0 E: Section 4 - 0x0378? 0x000 - 0x006 berry name + 0xFF string terminator 0x007 firmness 0x008 - 0x009 size (in mm) 0x00A max yield 0x00B min yield 0x00C - 0x00F berry tag line 1 RAM offset 0x02028D50 (US) / 0x02028AB0 (JP) 0x010 - 0x013 berry tag line 2 RAM offset 0x02028D7D (US) / 0x02028ADD (JP) 0x014 growth time per stage (in hours) 0x015 - 0x019 flavor 0x01A smoothness 0x01B 0 0x01C - 0x49B berry sprite (4bpp) (48 x 48 px) 0x49C - 0x4BB palette (16x2 Bytes / 5 bits per color) 0x4BC - 0x4E8 berry tag line 1 0x4E9 - 0x515 berry tag line 2 0x516 - 0x519 effect in bag 0x520 - 0x527 filled with 0 0x528 - 0x529 effect as held item 0x52A - 0x52B filled with 0 0x52C - 0x52F checksum Effects as held item 0x00 no effect 0x04 cures poison 0x05 cures burn 0x06 cures freeze 0x08 cures confusion 0x17 restores a lowered stat 0x1C cures infatuation The size is 1328 bytes. Berry Checksum unsigned long berryChecksum(char* berry) { int x; unsigned long checksum = 0; for(x = 0; x < 0x52C; x++) if(x < 0xC || x >= 0x14) checksum += (berry[x] & 0xFF); return checksum; } Mystery Event Data Structure RS: Section 4 - 0x0810 E: Section 4 - 0x08A8 Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Mystery Event Space 1000 bytes Note: Total size is 1004 bytes. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 - 0x3EB. (1000 bytes) Eon Ticket Event E: Section 2 - 0x049A - bit 0 Note: Unlike in Ruby & Sapphire the Eon Ticket Mystery Event is hardcoded and activated by a flag. Officially this was only used in Japan but the flag exists in all localized versions as well. When it's set the delivery guy appears at the 2F of the Pokemon Center, when you talk to him he will give you the Eon Ticket. Sending Item via Record Mixing RS: Section 4 - 0x0BFC E: Section 4 - 0x0C94 Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Distribution Limit word 0x5 How many times word 0x6 Item Index Number word Notes: Total size is 8 bytes. 0x0 appears to be the checksum. The number at 0x4 is the Distribution limit, the number of times you can send the Ticket at 0x5 increases even if you don't send the item. The Eon Tickets from the Official Events could be exchanged 151 times, while in case of the e-Card version 30 times. If the sent item is an Eon Ticket the activation flag for the Event is automatically set by the receiving game. e-Trainer Data Structure RS: Section 0 - 0x0498 FRLG: Section 0 - 0x04A0 E: Section 0 - 0x0BEC 0x00 - Battle Tower Type 0x01 - Trainerclass sprite indexes differ between the game versions 0x02 - Battle Tower Lv 0x00 => Lv 50; 0x01 => Lv 100 0x03 - 0x00 0x04 - Trainer Name RS (US/EU): up to 7 Bytes + string terminator 0xFF RS (Jap), FRLG & E: up to 5 Bytes + string terminator 0xFF 0x0C - Trainer ID default: 0x0000 0x0E - Trainer SID default: 0x0000 0x10 - Intro quote 6 x 2 Bytes 0x1C - Win quote 6 x 2 Bytes 0x28 - Lose quote 6 x 2 Bytes 0x34 - 1st Pokemon 44 Bytes 0x60 - 2nd Pokemon 44 Bytes 0x8C - 3rd Pokemon 44 Bytes 0xB8 - Checksum 4 Bytes (all 184 Bytes of the trainer data added together as words) Pokemon structure (44 Bytes) 0x00 - Species 2 Bytes 0x02 - Item 2 Bytes 0x04 - 1st Move 2 Bytes 0x06 - 2nd Move 2 Bytes 0x08 - 3rd Move 2 Bytes 0x0A - 4th Move 2 Bytes 0x0C - Level 0x0D - 0x00 0x0E - HP EVs 0x0F - Atk. EVs 0x10 - Def. EVs 0x11 - Init. EVs 0x12 - SP.Atk. EVs 0x13 - SP.Def. EVs 0x14 - ID 2 Bytes 0x16 - SID 2 Bytes 0x18 - IVs 4 Bytes 0x1C - PID 4 Bytes 0x20 - Nickname up to 9 Bytes + string terminator 0xFF 0x2A - 0x00 0x2B - 0xFF The size is 188 bytes. Mystery Gift Activation FRLG: Section 2 - 0x0067 - bit 1 E: Section 2 - 0x040B - bit 4 In Mystery Gift can be activated by answer the questionnaire in the Pokemon Market. The only requirement is that you have received the PokeDex. The phrase that activates the Mystery Gift feature is: Japanese: ともだち いっぱい ふしぎ つうしん English: LINK TOGETHER WITH ALL French: CONNEXION AVEC LES DRESSEUR German: LINK MIT ALLE ZUSAMMEN Spanish: CONEXIÓN CON TODOS Italian: INSIEME IN LINK ! Mystery Gift Data Structure Base Offset FRLG: Section 4 - 0x02A0 E: Section 4 - 0x03AC Wonder News Data Structure Japanese Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Wonder News ID word 0x6 Send Wonder News byte 0x7 Wonder News Graphic byte 0x8 Wonder News (Header) 20 bytes 0x1C Wonder News (Line 1) 20 bytes 0x30 Wonder News (Line 2) 20 bytes 0x44 Wonder News (Line 3) 20 bytes 0x58 Wonder News (Line 4) 20 bytes 0x6C Wonder News (Line 5) 20 bytes 0x80 Wonder News (Line 6) 20 bytes 0x94 Wonder News (Line 7) 20 bytes 0xA8 Wonder News (Line 8) 20 bytes 0xBC Wonder News (Line 9) 20 bytes 0xD0 Wonder News (Line 10) 20 bytes Notes: Total size is 228 bytes. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 and 0xE4. (224 Bytes) We still don't know what Offset 0x4 is for but assume that it's the Wonder News ID and it's a 16bit Integer. To make the Wonder News sendable to other Players a bitflag at Offset 0x6 can be set. (0 = OFF, 1 = ON) Offset 0x7 is for the Wonder News Graphic, there are 8 different designs for Wonder News in total. 1: 0x00 2: 0x01 3: 0x02 4: 0x03 5: 0x04 6: 0x05 7: 0x06 8: 0x07 International Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Wonder News ID word 0x6 Distribution byte 0x7 Wonder News Graphic byte 0x8 Wonder News (Header) 40 bytes 0x30 Wonder News (Line 1) 40 bytes 0x58 Wonder News (Line 2) 40 bytes 0x80 Wonder News (Line 3) 40 bytes 0xA8 Wonder News (Line 4) 40 bytes 0xD0 Wonder News (Line 5) 40 bytes 0xF8 Wonder News (Line 6) 40 bytes 0x120 Wonder News (Line 7) 40 bytes 0x148 Wonder News (Line 8) 40 bytes 0x170 Wonder News (Line 9) 40 bytes 0x198 Wonder News (Line 10) 40 bytes Notes: Total size is 448 bytes. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 and 0x1C0. (444 Bytes) We still don't know what Offset 0x4 is for but assume that it's the Wonder News ID. It's 16bit. To make the Wonder News sendable to other Players a bitflag at Offset 0x6 can be set. (0 = OFF, 1 = ON) Offset 0x7 is for the Wonder News Graphic, there are 8 different designs for Wonder News in total. 1: 0x00 2: 0x01 3: 0x02 4: 0x03 5: 0x04 6: 0x05 7: 0x06 8: 0x07 Wonder Card Data Structure Japanese FRLG: Section 4 - 0x0384 E: Section 4 - 0x0490 Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Wonder Card ID dword 0xC Graphic + Distribution byte 0xE Wonder Card (Header 1) 18 bytes 0x20 Wonder Card (Header 2) 13 bytes 0x2D Wonder Card (Center 1) 20 bytes 0x41 Wonder Card (Center 2) 20 bytes 0x55 Wonder Card (Center 3) 20 bytes 0x69 Wonder Card (Center 4) 20 bytes 0x7D Wonder Card (Footer 1) 20 bytes 0x91 Wonder Card (Footer 2) 20 bytes 0xB2 Pokémon Icon word Notes: Total size is 168 bytes. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 and 0xA8. (164 Bytes) Wonder Card ID is located at Offset 0x4, it's a 32 bit value that is separated into 2 16bit integers, similar to a Trainer ID. Known official Wonder Card IDs are 01000-65535 from the Aurora Tickets, 01001-65535 from the Mystic Tickets and 01002-65535 from the Japanese Old Sea Map. The Wonder Card Graphic shares the same Offset 0xC with the send functionality of Wonder Cards. Just like Wonder News there are 8 different designs... Although they are mapped in a different way with the help of bit flags. 1: 0x00 2: 0x04 3: 0x08 4: 0x0C 5: 0x10 6: 0x14 7: 0x18 8: 0x1C Adding bit 6 (+0x40) makes Wonder Card sendable, the receiver will get the Wonder Card without this flag activated. Adding bit 7 (+0x80) makes Wonder Card sendable, the receiver will get the Wonder Card with this flag activated. International FRLG: Section 4 - 0x0460 E: Section 4 - 0x056C Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Wonder Card ID dword 0xC Graphic + Distribution byte 0xE Wonder Card (Header 1) 40 bytes 0x36 Wonder Card (Header 2) 40 bytes 0x5E Wonder Card (Center 1) 40 bytes 0x86 Wonder Card (Center 2) 40 bytes 0xAE Wonder Card (Center 3) 40 bytes 0xD6 Wonder Card (Center 4) 40 bytes 0xFE Wonder Card (Footer 1) 40 bytes 0x126 Wonder Card (Footer 2) 40 bytes 0x15A Pokémon Icon word Notes: Total size is 336 bytes. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 - 0x150. (332 Bytes) Wonder Card ID is located at Offset 0x4, it's a 32 bit value that is separated into 2 16bit integers, similar to a Trainer ID. Known official Wonder Card IDs are 01000-65535 from the Aurora Tickets, 01001-65535 from the Mystic Tickets and 01002-65535 from the Japanese Old Sea Map. The Wonder Card Graphic shares the same Offset 0xC with the send functionality of Wonder Cards. Just like Wonder News there are 8 different designs... Although they are mapped in a different way with the help of bit flags. 1: 0x00 2: 0x04 3: 0x08 4: 0x0C 5: 0x10 6: 0x14 7: 0x18 8: 0x1C Adding bit 6 (+0x40) makes Wonder Card sendable, the receiver will get the Wonder Card without this flag activated. Adding bit 7 (+0x80) makes Wonder Card sendable, the receiver will get the Wonder Card with this flag activated. Mystery Gift Data Structure FRLG: Section 4 - 0x079C E: Section 4 - 0x08A8 Offset Content Length 0x0 Checksum word 0x2 Padding word 0x4 Mystery Gift Space 1000 bytes Notes: Total size is 1004 bytes. This is the actual Mystery Gift, the structure is exactly the same like an Mystery Event. The Checksum at Offset 0x0 protects the data between the Offsets 0x4 - 0x3EB. (1000 bytes) The Mystery Gift Data Header at 0x04 is always 33 FF FF FF, the game is looking for these bytes to check if there's a Mystery Gift. Mystery Event/Gift Checksum Algorithm unsigned int __fastcall MysteryEventGiftChecksum(int a1, unsigned int a2) { unsigned int v2; // r2 unsigned int i; // r3 v2 = 0x1121; // This is the seed for ( i = 0; i < a2; i = (i + 1) & 0xFFFF ) v2 = *(unsigned __int16 *)((char *)crc16_ccitt_table + (2 * (v2 ^ *(unsigned __int8 *)(a1 + i)) & 0x1FF)) ^ (v2 >> 8); return ~v2 & 0xFFFF; } crc16_ccitt_table.bin Mystery Gift Samples Extracted Mystery Gift Data from the ROMs (Includes Samples) Mystery Gift Data.zip Other sources -TOOLS- Other Threads related to this Topic: CURRENT RESEARCH STATUS: I would like to analyze the functionalities of the Aurora Ticket Distribution ROM and it would be cool if someone experienced with debugging could help with this Thanks for all the great support, effort and dedication to the project
