| User | Post |
BMF98567
Posts: 271/1261 |
The original block code replaces the actual block with a blank, solid tile and spawns a "bouncing block" sprite (the slightly lighter block you see on top). When the sprite drops back down, it replaces the blank tile with a "used" tile and deletes itself. My guess is the new code somehow isn't capable of doing that like the original is, so the block is left behind. You could probably fix it by patching the original code to check for certain tile numbers when hit and changing the block it spawns accordingly, but don't ask me how...  |
jonwil
Posts: 4/25 |
since I probobly wrote (or ripped from nintendo anyway) the ASM for that, I can say that its known about but not really fixable.
|
Smallhacker
Posts: 301/2273 |
IIRC, it happens with the original blocks as well. |
asdf
Posts: 154/303 |
I think there's a way to fix it by modifying animated tiles, but I'm not sure. |
Robin
Posts: 16/35 |
This happens in mine too, and in many other hacks I've played.
I guess it's just normal when using that particular Block. |
Deleted User
Posts: 1/12 |
Righto, so I've been messing around with Block Tool and such, and I put the good ol' smashable brick into my hack, complete with ExGFX.
But when I hit one of these bricks as small mario and bounce them, it looks like there is another block behind it (I've already checked and doublechecked for overlapped objects).
Any way I can fix this? |
labmaster
