Same Boss with different Hit Point Values - SMW Hacking Help

I'm using the Magikoopa Boss sprite in 2 sequential Boss rooms. The First Room is only meant to be beaten if you manage to get 7 hits on the Boss (Skipping the next room and ending the level), and the Second Room is meant to be beaten after getting 3 hits on the Boss. My idea for doing this was just to insert 2 different sprites with different HP values (One with 7 and another with 3). The problem is that when you fight the boss in the second room his HP will still be 7 just like the first room (even though I am definitely using 2 different sprites).

How can I fix this? I assume this has something to do with the RAM, but I'm stumped.

If I had to guess, it's because the two sprites you inserted actually aren't different. If you just copy-pasted the .asm and .cfg file and gave them a different name, then the issue likely lies with the .cfg file. If you open it up in a text editor, you'll see a line with "magikoopaBoss.asm" in it. This is the ASM file that the CFG is actually tied to. So if you just copy-pasted the file and gave it a new name without updating that line, it'll still actually reference the original sprite.
(you can also edit this value using PIXI's included CFG editor, the ASM file pointer is located at the bottom-left of the editor)

Professional frame-by-frame time wizard. YouTube - Bluesky - SMW Glitch List - SMW Randomizer

Originally posted by Thomas

If I had to guess, it's because the two sprites you inserted actually aren't different. If you just copy-pasted the .asm and .cfg file and gave them a different name, then the issue likely lies with the .cfg file. If you open it up in a text editor, you'll see a line with "magikoopaBoss.asm" in it. This is the ASM file that the CFG is actually tied to. So if you just copy-pasted the file and gave it a new name without updating that line, it'll still actually reference the original sprite.
(you can also edit this value using PIXI's included CFG editor, the ASM file pointer is located at the bottom-left of the editor)

That's exactly what the issue was. I can't believe I never noticed that in the CFG editor. Feel pretty silly now haha
Almost done with my hack! You've help me solve so many things along the way. I appreciate it!