Talk:Mirage Island (Generation III): Difference between revisions

← Older edit

Talk:Mirage Island (Generation III) (view source)

Revision as of 16:08, 1 January 2022

4,434 bytes added , 1 January 2022

no edit summary

Kenny chen1998

20

edits

@@ Line 54: / Line 54: @@
 :::Sorry if these questions are getting a bit technical; it's just that this issue seems much more fascinating now! I'm not sure if I'm confusing myself further, though.. @_@ [[User:Fenyx4|Fenyx4]] ([[User talk:Fenyx4|talk]]) 04:00, 5 February 2014 (UTC)
+During my research on maximum play time through cartridges, flash cards which have time function, emulators and so on, I found that the mirage number won't change to 0x0000 at all. With battery alive, a maximum time cartridge would change its mirage number normally like the non maximum time cartridge does.<br>
+it's 2021 now, almost 7 or 8 years later, so when I searched what Hfc2x did on 2013, the photos here were all gone and can't be seen. But reading the words here, I guess Hfc2x had misunderstanding the 0x0000 of emerald. cus the offset of mirage number in emerald not always stands on 0x02026DE4, it would change it offset when player changes maps, and thus makes the types on 0x02026DE4 be 0x0000. the real mirage number jump to other offsets.<br>
+I will revise the page of mirage island after making more research and tests and getting a confident conclusion.--[[User:Kenny chen1998|Kenny chen1998]] ([[User talk:Kenny chen1998|talk]]) 13:25, 27 September 2021 (UTC)
+After many tests and research on Mirage island, i finally make sure that maximum play time won't genrate mirage island value to 0x0000. And the address of Mirage island value is:RS:(U) =0x02026ABC,(J) =0x0202681C; E:(U) = (content in pointer 0x03005D90) +0x2390, (J) = (content in pointer 0x03005AF0) +0x2390.
+In addition, I find a totaly new way to launch mirage island. It's not about cheating, checking and editing saves, or RNG abusing. I use the Pokémon Fan Club Chairman's sibling in Pacifidlog Town to find initial RTC, use Spindas'spot to calculate PID, use the standard list of elpased-RTC-days and Mirage island value made by myself to calculate to find elpased RTC days when mirage island appears, and use rtcread to finnaly accelerate the time to target RTC. (rtcread won't check or edit any of your save. you can also choose not to use rtcread and wait the real time to pass ) You can see my walkthrough [https://tieba.baidu.com/p/7680216276?pn=2 here] and my operation video on [https://youtu.be/BLi7_YnWpbI youtube] or [https://www.bilibili.com/video/BV1WP4y1n7CL?spm_id_from=333.999.0.0 Bilibili]--[[User:Kenny chen1998|Kenny chen1998]] ([[User talk:Kenny chen1998|talk]]) 16:08, 1 January 2022 (UTC)
 == ORAS ==
@@ Line 122: / Line 132: @@
 == Am I wrong about the probability of Mirage Island appearing? ==
-The article said, "approximately 1/10870 if the player has a full party". Then somebody (should I point fingers?) changed it to 1/10923, and said, "The probability with a full party isn't 6/65536 (which reduces to approx. 1/10870); that's not how probability works. It actually is 1 - (1 - 1/65536)^6, which is approx. 1/10923." According to my calculator, 6/65536 reduces to approximately 1/10923, while 1-(65535/65536)^6 reduces to approximately 10870. Please tell me if I'm wrong. I'm willing to spend a lot of money to replace my calculator. [[User:Sumwun|sumwun]] ([[User talk:Sumwun|talk]]) 13:20, 15 July 2016 (UTC)
+The article said, "approximately 1/10870 if the player has a full party". Then somebody (should I point fingers?) changed it to 1/10923, and said, "The probability with a full party isn't 6/65536 (which reduces to approx. 1/10870); that's not how probability works. It actually is 1 - (1 - 1/65536)^6, which is approx. 1/10923." According to my calculator, 6/65536 reduces to approximately 1/10923, while 1-(65535/65536)^6 reduces to approximately 1/10870. Please tell me if I'm wrong. I'm willing to spend a lot of money to replace my calculator. [[User:Sumwun|sumwun]] ([[User talk:Sumwun|talk]]) 13:20, 15 July 2016 (UTC)
+Quite simply your equation does not take into account the possibility of two (or more) Pokémon having overlapping PIDs
+~~shinyrex
+::That's not the point. The point is that somebody edited the article, said that he/she took that possibility into account but really didn't, and I'm here to make sure that the first part of the sentence is true before I change it back. Neither equation is necessarily MY equation. [[User:Sumwun|sumwun]] ([[User talk:Sumwun|talk]]) 00:04, 16 July 2016 (UTC)
+:::As near as I can tell, the value of <code>1/10870</code> is, relatively speaking, nowhere ''near'' the value of <code>1-(65535/65536)^6</code>, and I don't have the first idea why you think <code>1-(65535/65536)^6</code> reduces to <code>1/10870</code> unless you've completely assumed that. ''As near as I can tell'', relatively speaking, the value <code>1/10923</code> is approximately equal to ''both'' <code>1-(65535/65536)^6</code> and <code>6/65536</code>&mdash;at the very least, they're all much closer to equal to each other than <code>1/10870</code> is to any of them. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 01:17, 16 July 2016 (UTC)
+::::My math is right man. I garuntee it ~~shiny trex
+:::::Okay, I re-checked my math. It was probably a rounding error. Sorry. [[User:Sumwun|sumwun]] ([[User talk:Sumwun|talk]]) 03:54, 16 July 2016 (UTC)
+::::::It's okay. Sorry for any confusion. [[User:Shiny TRex|Shiny TRex]] ([[User talk:Shiny TRex|talk]]) 16:06, 7 October 2016 (UTC)
+== Spanish versions ==
+Which are the offsets for the spanish versions? I'm trying to reach the island in Pokémon Emerald but I could only reach it in Ruby thanks to a pair of GameSharks (1041B4B4 375704A9 in orden to change the MI values and E55ADD11 9D142FB1 486FF0A8 5140D6A1 FA225232 5F770121 240362D9 63D000D0 A4895EA1 68C41823 3B02F11E DE278605 D0CC9724 FD0D0FA7 2E618A61 B12C85A6 46A1CD10 71B2786A 6B8952E5 4EA46577 F68D22A6 E8F37EE9 5A44892C 298C3710 1B5AC142 50989EE5 844912AF 20D7CA12 C3F639B5 BD557BAD 9A5D5CDB 72C65BD3 2A3CB760 EB29468C 3BA1746B BB22CCD9 2CE5EAD0 0621AF4D 53E57771 C54C6B1D in order to get a compatible Pokémon).--[[User:LtLynx|LtLynx]] ([[User talk:LtLynx|talk]]) 16:55, 14 January 2018 (UTC)