Quick Research & Development Thread

[Le pug]

The equivalent "Infinite Safari Steps" for Emerald appears to be at 0xFC15E. Again, just replace 01 38 with 00 38.
Emerald doesn't have a visible step counter in the menu to hide either, which is nice I guess.



If you'd like to "stone Pokemon to death" in Emerald, change the byte at 0x3EF94 from 0x06 to 0x00 as well.

To go along with this, does anyone have any research on anything else for the Safari Zone for EM? As in the location to change the amount of balls you are rewarded and how to change the locations you end up when your time is up or when you decide to retire?

 

[Sakakii]

This has probably been documented already, but if it's useful for anyone then hey I'm helping...
For FireRed:

Messed around with the 'view memory' function in my emulator.

0x020242D4 is the ram offset for Pokemon in first slot status condition.

It's one byte (00).
Changing this gives these effects:
01 gives you 1 turn of sleep, 02 gives you 2 turns of sleep, etc, the sleep counter persists after battle
(I guess this is how sleep works in this gen, or side effect of 'unnaturally' inflicting sleep?)
08 = regular psn (What is badly poison then?)
09 = psn, but when you go in battle the pkmn will be asleep, but instantly
wake up
0A = like 09, except you sleep for one turn. you take psn dmg during that turn.
0B - 0F same as above, sleep turn increases by one the higher up you go...
10 = regular burn
11-17 = same effects as 09-0A but burn instead of psn...
18 = psn and burned at same time (psn in status screen), no animation/sound
for taking dmg in-game
20 = regular freeze, not sure how to alter the chance of defrozt (standard should be 20 % each turn)
2F = sleep, freeze, psn. Yes, you are frozen when you wake up have fun.
30 = frozen and burned
40 = regular paralyz
99 = double psn, burn
FF = sleep animation uses psn, you take 2x psn, 1x burn, perhaps you
are also frozen and prz once you wake up sorry didn't test yet...

Here's an interesting thing, the next byte after 020242D4, so, D5, you can change this and it will
affect the 2nd psn damage you take... Idk if it does anything else, maybe it has something to do with badly poison? Ez way to test is to face a wild Pokemon that knows only toxic, Idc enough atm.

For example: FF FF = 2nd psn tick essentially one shots you
You can tune the 2nd part down to like 99 and it only does like 50 %...
I'll make a guide on how to use these things in actual XSE scripts when I feel confident enough,, it's really cool the things you can do just by altering the RAM.

 

[mgriffin]

It's one byte (00).
Changing this gives these effects:
01 gives you 1 turn of sleep, 02 gives you 2 turns of sleep, etc, the sleep counter persists after battle
(I guess this is how sleep works in this gen, or side effect of 'unnaturally' inflicting sleep?)
08 = regular psn (What is badly poison then?)
09 = psn, but when you go in battle the pkmn will be asleep, but instantly
wake up
0A = like 09, except you sleep for one turn. you take psn dmg during that turn.
0B - 0F same as above, sleep turn increases by one the higher up you go...
10 = regular burn
11-17 = same effects as 09-0A but burn instead of psn...
18 = psn and burned at same time (psn in status screen), no animation/sound
for taking dmg in-game
20 = regular freeze, not sure how to alter the chance of defrozt (standard should be 20 % each turn)
2F = sleep, freeze, psn. Yes, you are frozen when you wake up have fun.
30 = frozen and burned
40 = regular paralyz
99 = double psn, burn
FF = sleep animation uses psn, you take 2x psn, 1x burn, perhaps you
are also frozen and prz once you wake up sorry didn't test yet...

Maybe you've already worked this out, but it seems like this is a bit set.

7 6 5 4 3 2 1 0
T Z F B P S S S

S: Sleep = 0x01–0x07 = 2^0 + 1–7
P: Poison = 0x08 = 8 = 2^3
B: Burn = 0x10 = 16 = 2^4
F: Freeze = 0x20 = 32 = 2^5
Z: Paralyze = 0x40 = 64 = 2^6
T: Toxic = 0x80 = 128 = 2^7

Thus 0x99 = 0x80 + 0x10 + 0x8 + 0x1, and so 0x99 should be 1 round of poison, 1 round of burn, 1 round of toxic (which I'd expect to be 1/16th, not 1/8th like regular poison?), and 1 turn of sleep.

IMO it's a weird choice of data structure, because you "can't" have multiple statuses at the same time. The weird effects you see when setting multiple bits must be a result of the game code checking for each one individually (which is interesting, I'd expect it to only do one).
I also think it's interesting that the second byte contains the toxic counter, but the sleep turns are in the first byte. I assume this is because they behave differently, i.e. sleep doesn't reset on switch but toxic does.

 

[Sakakii]

Tested some sounds in FireRed, I want to test more but I don't know how to find more sounds, if anyone can help me that's great. After 15A there seems to be no more sounds they all generate silence, so Idk where to go :(

Spoiler:

these can be used by the command 'sound' in xse (example: sound 0xD, use checksound to make the sound finish playing before script continues)
0D = Hit by attack/take dmg
D1 = ?
D2 = ?
D3 = Sounds like some buglike Pokemon cry (but no actual pkmn that I know)
D4 = ?
D5 = ?
D6 = Basically Thunder the move
D7 = A short and quick clap
D8 = Silent
D9 = Unsure, 2nd part reminds me of some sort of warp sound
DA = Wish like sound, like a star?
DB = Very intriguing sound, might be fitting for an alien like Pokemon
DC = Spooky sound lasts like 3-4s, amazing sound effect for a horror area
DD = 1st part of moonlight?
DE = Reminds me of Donald Duck when he talks
DF = Weak tornado? Similar to Twister the move
E0 = Kinda like birds singing joyfully
E1 = Some weird sound then a drum
E2 = Kinda like pouring water over someone
E3 = Silent
E4 = Silent
E5 = Sweet Scent
E6 = Sad sound, like a hurt Meowth or Skitty
E7 = Silent
E8 = Stat boost (in-game, like after Bulk Up)
E9 = 3s long, kinda like a monster moving underground? Could be a great cry.
EA = Kind of like an angry crowd but very short like 0.x s...
EB = Like ice breaking?
EC = Silent
ED = I've never heard this before... decent sound for horror setting I s'pose,
kind of like an angry, evil fairy
EE = Stat drop (in-game, like getting Intimidated)
EF = Lasts 4s? Kinda like a swarm of bees.
F0 = No clue. Very short sound.
F1 = Door open/close
F2 = Idk, very short
F3 = Kinda like using a repel, seems like theres some silence after its done
playing (like for 1-2s)
F4 = Like saving your game sound. Some silence after playing.
F5 = Idk, garbage imo, very short
F6 = Something to do with setting options?
F7 = Same as f5
F8 = Buy/sell sound
F9 = S.S. Anne leaving
FA = SOUNDS VERY familiar. Harpy?
FB = Similar to FA
FC = Like FB/FA, but ends abruptly with some error sound
FD = Somewhat peculiar, alien like sound.
FE = Like Wish heal
FF = Error sound, like you chose the wrong alternative
100 = PC Heal
101 = Lv up
102 = Catch Pkmn
103 = Caught a Pkmn
104 = Got a badge?
105 = Some kind of success fanfare, RS style
106 = Pick Berry from tree sound
107 = silent
100 to 15A is basically these https://www.pokecommunity.com/archive/index.php/t-123520.html
15B = silent
15C =silent
15D =silent
15E =silent
15F =silent

 

[BirdstarCat13]

Disable "The Pokemon Stopped Evolving." [FR]

FR has a feature that if you attempt to evolve a Pokemon into something not in the Kanto Dex (and you don't have the National Dex), it will mysteriously stop evolving. You could just give the player the National Dex at the beginning of the game, but if you don't want to do that, you can easily disable this.

Basically, this will turn some conditional jumps into unconditional jumps, and remove some checks. No free space required.

0x08043156: 02 E0
0x080CE90C: 1C E0
0x080CF566: 17 E0
0x08126C26: C0 46 C0 46 C0 46 C0 46
0x08126C4C: 08 E0

The code explaining the above byte changes is:

Spoiler:

.text
.align 2
.thumb
.thumb_func

@ trade item removal
.org 0x043156
b 0x04315E

@ all three
.org 0x0CE90C
b 0x0CE948

@ trade
.org 0x0CF566
b 0x0CF598

@ stone
.org 0x126C26
nop
nop
nop
nop

@ stone
.org 0x126C4C
b 0x126C60

Those offsets do not exist. What am I doing wrong? Are they backwards or smth?! You should show the E X A C T series of numbers I need to type into my hex editor to jump t the right offset, and also show what's there by default so I know I'm at the right place. 0x08043156 is an offset which is 16 times the size of my ROM if I put it in as you've typed it.

 

[BLAx501!]

Those offsets do not exist. What am I doing wrong? Are they backwards or smth?! You should show the E X A C T series of numbers I need to type into my hex editor to jump t the right offset, and also show what's there by default so I know I'm at the right place. 0x08043156 is an offset which is 16 times the size of my ROM if I put it in as you've typed it.

0x means the number is hexadecimal. 08 is the memory type you are referring to (ROM in this case) and 043156 is the offset on the memory. So if you are using HxD or any other hexadecimal editor, you have to look for 43156 ;)

 

[BirdstarCat13]

0x means the number is hexadecimal. 08 is the memory type you are referring to (ROM in this case) and 043156 is the offset on the memory. So if you are using HxD or any other hexadecimal editor, you have to look for 43156 ;)

lol I know what 0x means, but that 08 bit made it unclear. "0x08043156" logically means "08043156, but it's hex" nothing about it indicates that it's supposed to be just "43156", so I don't see why he couldn't just put the literal offset - I think it would have been understood that it was hex and whatnot. that "memory type" seems like it was unneeded :P

 

[BluRose]

lol I know what 0x means, but that 08 bit made it unclear. "0x08043156" logically means "08043156, but it's hex" nothing about it indicates that it's supposed to be just "43156", so I don't see why he couldn't just put the literal offset - I think it would have been understood that it was hex and whatnot. that "memory type" seems like it was unneeded :P

we include it for consistency with the game itself :)
various tutorials replace pointers, which must refer to the memory type at the end--reverse pointers, in other terms
so the game would refer to 0x43156 as 0x08043156, so we decide to represent it as such when referencing any address

 

[BirdstarCat13]

we include it for consistency with the game itself :)
various tutorials replace pointers, which must refer to the memory type at the end--reverse pointers, in other terms
so the game would refer to 0x43156 as 0x08043156, so we decide to represent it as such when referencing any address

That's still really confusing, I don't see why you couldn't just at least include the *actual* offset for people who are just looking for what edit to make and where

 

[Lancekoijerwillborough]

That's still really confusing, I don't see why you couldn't just at least include the *actual* offset for people who are just looking for what edit to make and where

08 needs to be identified to determine what memory can the offset be found. If you expanded the rom, you would probably need to take a look at 08 part because you need to change it into 09, because again the code is read as that and it refers to the memory. You would not just write 0x43156 because "generally' speaking, it is read as 0x00043156 which is very different from 0x08043156.

0x00 refers to BIOS
0x02 refers to WRAM
0x03 refers to IRAM
0x04 refers to I/O
0x05 refers to PALETTE
0x06 VRAM
0x07 OAM
0x08 ROM

Look at the Visual Boy's Memory as your reference.

The codes that are provided here are not meant for Hex Editor only.
In general knowledge, 0x00043156 refers to BIOS.

Hope this helps you understand why 08 is included.

 

[BirdstarCat13]

08 needs to be identified to determine what memory can the offset be found. If you expanded the rom, you would probably need to take a look at 08 part because you need to change it into 09, because again the code is read as that and it refers to the memory. You would not just write 0x43156 because "generally' speaking, it is read as 0x00043156 which is very different from 0x08043156.

0x00 refers to BIOS
0x02 refers to WRAM
0x03 refers to IRAM
0x04 refers to I/O
0x05 refers to PALETTE
0x06 VRAM
0x07 OAM
0x08 ROM

Look at the Visual Boy's Memory as your reference.

The codes that are provided here are not meant for Hex Editor only.
In general knowledge, 0x00043156 refers to BIOS.

Hope this helps you understand why 08 is included.

So why not just include a note about it? Like, "here's the technical offset and the offset you should put into a hex editor"

 

[kalarie]

Because it's more convenient that the person who wants to learn romhacking takes time and effort to learn from tutorials, than for an experienced romhacker to explain himself in a simplified manner.

 

[Lancekoijerwillborough]

So why not just include a note about it? Like, "here's the technical offset and the offset you should put into a hex editor"

It's so inconvenient to put "here's the technical offset and the offset you should put into a hex editor" note to every research that will be posted here. This is Quick Research Thread actually so if you still have questions, because it has been explained already, you may want to make a thread on Rom Hacking Section.

 

[BirdstarCat13]

It's so inconvenient to put "here's the technical offset and the offset you should put into a hex editor" note to every research that will be posted here. This is Quick Research Thread actually so if you still have questions, because it has been explained already, you may want to make a thread on Rom Hacking Section.

I was just saying - the post with the offsets made it clear it was meant to help people edit certain locations, so it should have been written in a way convenient for that. That's all I'm saying.
What I was talking about was more listing the two sets of offsets, *not* literally including your explanation of memory types in each post that has offsets in it

 

[BirdstarCat13]

Because it's more convenient that the person who wants to learn romhacking takes time and effort to learn from tutorials, than for an experienced romhacker to explain himself in a simplified manner.

Yes but I learn nothing if I can't understand the offsets. I literally don't care about "memory types", I'm just on this thread to find out what needs to be modified ;)

 

[destinedjagold]

Yes but I learn nothing if I can't understand the offsets. I literally don't care about "memory types", I'm just on this thread to find out what needs to be modified ;)

If you can't be bothered to learn about these "memory types" then don't expect others to spoon-feed you either.

 

[DrFuji]

The first post has been updated (after nearly two years!) with links to almost one hundred informative posts! I love every discovery in this thread and everybody who's helped contribute to the community.

asm resource thread update coming soon

 

[Lunos]

This information seems to be important enough and it's not mentioned in the main post, so I just took the liberty of bringing it here.

Forcing the Set Battle Style in Fire Red

For anyone else who's interested - I was able to get in touch with DoesntKnowHowToPlay, who was able to help me.

In FireRed, starting at 0x1D8727, change 5 bytes to 28 92 87 1D 08. This modifies the battle script to bypass whatever the user set in the Options menu and always act like "Set" mode.

Source.

 

[xizqu]

Yes but I learn nothing if I can't understand the offsets. I literally don't care about "memory types", I'm just on this thread to find out what needs to be modified ;)

08 is required for telling someone what area of the rom it is. If be just put the offset without the memory, what bank would you change? You just use hxd so you don't get access to other Banks but what if he meant 02 which is ram. We hack banks 02, 03 sometimes 04 but mostly 08. So it's pretty much required. If he meant 02 and you changed it in 08, you'd break your game.

 

[BirdstarCat13]

08 is required for telling someone what area of the rom it is. If be just put the offset without the memory, what bank would you change? You just use hxd so you don't get access to other Banks but what if he meant 02 which is ram. We hack banks 02, 03 sometimes 04 but mostly 08. So it's pretty much required. If he meant 02 and you changed it in 08, you'd break your game.

I think it'd be a safe assumption if he hadn't had the bank listed, but if it's the absolute offset, then you already know that by definition it's by the ROM/bank 08