Showing Visitor Messages 196 to 210 of 216
-
March 30th, 2015 8:22 AMEricaHarperOh. Well. I've no intention of doing something like that, since I've no clue where some flags I could use for seen/caught would be. And I've little interest in keeping them in separate locations. Thanx again. Btw... you're making a hack right?
-
March 30th, 2015 8:17 AMJoexvPrety uch only if you didn't want it to be the same, like if you put the caught flags ina different location. Cause you would still need to know the amount between them.
-
March 30th, 2015 7:57 AMEricaHarperThank you! The yy especially threw me off. But I'm sure rush had a reason for that. He said it doesnt have to be the same. In what case would that be?
-
March 30th, 2015 7:54 AMJoexvCorrect
-
March 30th, 2015 7:52 AMEricaHarperYes. I think I get it. 661/8 rounded is 82, which in hex is 52, so that's my answer, right? Also xx and yy are the same.
-
March 30th, 2015 7:50 AMJoexvOh, those would be 52. And then the caught flags woul be at whatever ramoffset was stated in the tut(cant remember it atm) + 52. So it would be for xx and yy. If that makes sense.
-
March 30th, 2015 7:24 AMEricaHarperOops I'm sorry. I mean the xx here:
Put XX 22 at x843A0, where XX is the number of bytes taken by your dex flags.
Put 20 1C at x843A6.
Put YY 30 at x843A8, where YY is the number of bytes between the sets of flags. YY is probably the same as XX, but it doesn't have to be.
Put XX 22 at x843AC, where XX is the number of bytes taken by your dex flags.
I don't understand this. the bytes taken up by my dex flags. Like total for both seen and caught? And the number between them; I'd think that'd be zero. I just don't get it. Edit: I was half asleep when I sent that message to you. srry about that. -
March 30th, 2015 7:16 AMJoexvwhat do you men xx will stay 34? The xx xx xx 08 is where you put the save block hack, so example 20 30 40 08 then you add 1 to it so 21 30 40 08 and that would be what you put instead of xx.
then its the same concept for the yy's but you add 61 to it. -
March 29th, 2015 9:12 PMEricaHarperSo xx would stay 34, then? What is is the xx variable's significance? And only having 52 flags for 661 pokemon wont cause problems will it?
-
March 29th, 2015 9:10 PMEricaHarperOk, I get it. Thank you. It's hard when youre new because no ones got time to help you. But I'm really grateful that youre being patient with me. I have one more question because I dont wanna bug you.
I've never been able to get this here:
At 0x152E98, put 00 48 00 47 [XX XX XX 08]. For XX XX XX 08, it's the offset you put the save block routine +0x1.
At 0x15284E, put 38 47.
At 0x15288C, put [YY YY YY 08]. For YY YY YY 08, it's the offset you put the save block routine +0x61.
At 0x0D9CC6, put 38 47.
At 0x0D9D04, put [YY YY YY 08].
At 0x0DA284, put 00 48 00 47 [XX XX XX 08]. -
March 29th, 2015 9:05 PMJoexvnumber of dex entries/8, rounded up
so 52 -
March 29th, 2015 9:01 PMEricaHarperLol, thx a lot! What is the size of the flags table at 03d800? And how where should I place my caught flags at if I'm doing 661?
-
March 29th, 2015 8:58 PMJoexvI dont think that would be a pokedex order issue, but most likeyly an issue regarding where you put the seen/caught flags and the pointeres to them.
Yea I had gotten advice to try the unown slots too and it helped fix a lot of issues.:) I'm just glad ll made the new tut. -
March 29th, 2015 8:51 PMEricaHarperI expanded successfully like two days ago, but have had one problem. Every time I start a new game, random pokemon turn up seen in my deck; like las time it was Raichu, Gloom, Vileplume and Deoxys. Though I hadn't edited the dex order, so I speculate that was at least 75% of my prob. I'd love to have your input.
-
March 29th, 2015 8:48 PMEricaHarperOh! Cool. Thx. I was wondering about that. I was doing the tut, and couldnt get it right, so I talked to LC, since he was the only person who was available out of those I did. And apparently there was a huge help demand regarding it, so he posted a video tutorial. That helped a lot as I realize the tut was outdated.

