Showing Visitor Messages 136 to 150 of 187
-
March 30th, 2015 8:25 AMEricaHarperI see. at the time it was thoght to be safe, but as the technique developed, it was realized that 60 d8 03 02 causes problems.... Why has the tut stayed so messy like that? All this important info has been floating round behind the scene... Mr. Rush must be suuuuuuuuper busy.
-
March 30th, 2015 8:17 AMXencleamasUnsafe anymore. :)
-
March 30th, 2015 8:05 AMEricaHarperK, thx! Then based on what you've told me, seen/caught flags extend from 0203d800-0203d85d. 0203d860 is too far and unsafe. Right?
-
March 30th, 2015 8:02 AMXencleamasYeah... seen will be 0x0203D800... then caught will be 0x0203D8??... ?? is the result of the divided by eight part. :)
-
March 30th, 2015 7:56 AMEricaHarperYes! I get it! Wow that was hard. that must be part of why I kept getting random seen pokemon in my rom after expanding the mons.. My seen flags should still be 0203d800, right?
-
March 30th, 2015 7:53 AMXencleamasYep.
-
March 30th, 2015 7:48 AMEricaHarperOh! Ok, so your caught flag would end in 5D and mine would end in 52?
-
March 30th, 2015 7:45 AMEricaHarperOk.. I think I get it. So I have to take my no of dex entries divide them by 8, and round them to a multiple of four and convert the result to hex? Then that is the number of flags I need? Then I find a place n the ram for seen and caught flags. You have said that 0203d860 will do me no good for my flags. ...My brain hurts. So I should use 52 because 661\8 is 82 when rounded which is 52 in hex? This is the hardest part to understand.
-
March 30th, 2015 7:31 AMXencleamasabout the 0x0203D85D leads to the ram when emulated in the game. Well you only need to do is revese hex it: 02 03 D8 5D ===> 5D D8 03 02... and type that to where it was instructed (example: C0744: point to new CAUGHT flags. I will put 52 D8 03 02.) 0x02000000 is a pointer too as same as 0x08000000... 0x08000000 goes to a part of the game (scripts, sprites etc)... while 0x02000000 leads to the ram outside the rom but when emulated in game.
-
March 30th, 2015 7:28 AMEricaHarperSo I thought the offset was like.. if it was a pointer itd look like this: 00 d8 03 02. Like the 02 was similar to the 08 you see in a lot of pointers.
-
March 30th, 2015 7:27 AMEricaHarperThose bytes were the ones I found at 03d800. My hex editor says that the offet 0203D85D doesn't exist.
-
March 30th, 2015 7:24 AMXencleamasHmm... the reason why I have said 5D because 744 is the max dex entries would register in the ram (744/8=93...93 in hex is 5D)... so again 3D860 will not work safe and nope you can't use more than 5D. So use 0x0203D85D for safety reasons. Safe flags? Do you mean the script flags? I bet they are until 0x95F. :/
And... what are those hex bytes? :/ -
March 30th, 2015 7:16 AMEricaHarperThat is to 03d860 in me rom. Are you saying I can use more?I don't know where the safe flags end. :\
-
March 30th, 2015 7:14 AMEricaHarper9C 44 02 02 04 5D 00 03 19 D8 03 08 32 43 02 02 74 44 02 02 A8 44 02 02 70 B5 14 4E 30 78 14 4A 00 28 01 D0 0C 20 10 70 12 4D 28 68 4B 30 12 4C 21 78 01 70 11 49 10 78 80 00 40 18 00 68 A9 F2 47 FC 0F 48 21 78 00 78 81 42 23 D3 0D 4A 10 68 0D 49 08 40 10 60 0D 4B 0D 4A 31 78 7F 20 08 40 80
I don't follow. That isn't enough? -
March 30th, 2015 7:08 AMXencleamasHmm... I have used up 5C more bytes for the caught flags... 5C because: 728 dex entries... 728/8=91+1=92... 92 in hex is 5C. 5C worked fine to me... but up to 5D can only be used. Your 0x0203D860 cannot make it work so use below 5D.

