- 67
- Posts
- 15
- Years
- Seen Jan 24, 2015
HOLY CHEESE!
This is amazing! I might even consider starting a new hack!
This is amazing! I might even consider starting a new hack!
It seems it wasn't saved in the manual. That is for the a new function, that allows you to create several sized pedometers. The flags it asks for allow you to activate one of those pedometers, by setting the flag it asked for. Those pedometers are located at 0x0203f4e0 to 0x0203f4eb, but to access them you need to use the getbyte commands.
0x203f4e0 -> always on 32bit pedometer
0x203f4e4 -> first flag asked activated 32 bit pedometer
0x203f4e8 -> second flag activated 16 bit pedometer
0x203f4ea -> third flag activated 8 bit pedometer
0x203f4eb -> fourth flag activated 8 bit pedometer
These pedometers are totaly optional to use, and don't even depend on the 0x800 flag.
So, the only relation they have with the safari hack is that they ride on the back of the safari decreasing.
Honestly? I'm interested only to the answer of JPAN.. not to yours.Honestly? After all the amazing work he's done for the community with this engine, you say one thing about how "interesting" it is, without even looking at the manual and realizing the work he put into it I'll bet, and ask him to port it to Emerald? Wow.
JPAN, maybe you should add an option for variables more then 16 bit. 65535 isn't that much, and it ruins my bank script pretty hard xD And there are probably more cases when the 65k limit is verrrry annoying :C
I don't know if it is possible, but that would be an awesome addition :3
Something like that would require a total overhaul of how variables work. I doubt he will do it for you, but if you need to use higher values your best bet would be to take a look at ASM - a bank script in ASM would be much better, at least.
Not to say there are not 65535 variables either...
Besides, there are thousands of them anyway. I don't see how that can be very annoying.
I was talking about the limit of 65k in value. There are enough free variables to be used, that isn't the problem =P
And @ Darth, about ASM.. It costs pretty much time to learn ASM, and because of personal reasons, I don't have much time. I already figured out myself that ASM is a better solution..
My bad. I accidentaly left some debug table addresses in the main table. Remove them and place your pointer on the second slot (b0ff3908), and delete the third. In that case, it will be 1.I'm really confused with the overworld stuf.
If I make a new pointer here V
B0FD3908 B0FF3908 B0FE3908 New pointer
What table is it?
(The manual said that only one was occupied but there are already 3 pointers. so is it 0x1 or 0x3)
Look at the trainer flag hack area of the manual. I placed a picture there that explains the new data in the A-Map person event. Simply change the rightmost unknown byte, right below the picture number, to the table number. The change will not appear in A-Map, but in game it will be your sprite.And how can I display the new overworlds ingame?
(I tried by editing the event data in hexworkshop but failed.)
The item table starts at 0x3db028, and ends at 0x3df09c. If you can, after editing the Item in the Item editor, Open a table file in your hex editor and search for your item name, and it should pop up. If you can't open a table file, multiply the item number by 0x2c and add it to the base address.Wait, so how does the item hack work?
I have a script compiled at 0x900000. I'm using Item Editor by Thethethethe. Where should I enter the offset? Because I can't find where the item table is located in the rom...
#alias startContest mulVar
#org @start
mulvar
copyvar 0x8000 0x8001
end
HackMew, just out of curiosity, what do you mean by "backwards compatibility"?Backward compatibility has already been broken (which is the main reason I don't like this hacked engine), basically.
HackMew, just out of curiosity, what do you mean by "backwards compatibility"?
Oh, so you meant "script backwards compatiblility, as scripts from the old/new couldn't go on to the new/old"? I see.I'll give you a little example: the sethealingplace command. In the hacked engine, it has changed and now requires three variables to be set in order to work properly.
Oh, so you meant "script backwards compatiblility, as scripts from the old/new couldn't go on to the new/old"? I see.