in the status bar, because it intentionally overlaps with the OAM sprite #0. This is a special sprite because it sets the Sprite #0 Hit bit of a PPU status register ($2002) meaning it can be used to make code execute while specific pixels are being drawn.
It is used to differentiate the status bar from the rest of the game (you wouldn't want to make the status bar scroll with the camera, would you?).
This however only works if there is actually something that overlaps it, meaning that if the status bar gets glitched up and the coin symbol gets replaced by some transparent tile (0x24) it won't set the bit in the register and it softlocks in an infinite loop waiting for something to happen (also, while checking for the bit all interrupts are disabled, so there is nothing that can happen).
tl;dr: The freeze is a simple softlock, nothing special. Rather try figuring out why the glitchy status bar occurs in the first place.
someone on youtube complained about my PAL TAS that I was inside a piranha plant. And it seems hitboxes did overlap, so why did I survive?Did you play on NES or VC? I have seen people trying to get their games to run and fail/or get glitchy graphics on NES. I think that pause thing is related to that. In other words, a hardware failure. ----- http://i.imgur.com/mgCLhXL.gif someone on youtube complained about my PAL TAS that I was inside a piranha plant. And it seems hitboxes did overlap, so why did I survive?
Other, invisible fire hit and scroll lock would also be interesting.
FrameCounter = $09
;[...]
EnemiesCollision:
lda FrameCounter ;check counter for d0 set
lsr
bcc ExSFN ;if d0 not set, leave
Is that true in NTSC as well? It is kind of baffling to me that this is only being discovered now! This has to be useful for something, right?
Suggestion> on even frames, draw the box fully, or with less transparency. I do it in SMW (where the sprite id determines the parity) and it`s really useful. And having a different color for Mario would be nice too, and pretty easy to edit.
Did you play on NES or VC? I have seen people trying to get their games to run and fail/or get glitchy graphics on NES. I think that pause thing is related to that. In other words, a hardware failure.
https://www.twitch.tv/pmniac/v/81711394 Posted this in IRC, but might as well post it here. Why and how does this work?
That is the PAL version and it's known to have glitchy floor collision detection although I only saw it after hitting a block before. A PAL TAS could maybe use this in 4-2 to speed up the warp zone section.
I had tested it thoroughly in 4-2 and couldn't do it through the stairs. But I think it could be done in other levels such as 1-2 at the end but I don't know if it's faster than going through the wall.
But why would this work in 1-2 but not in 4-2?
EDIT: Is it maybe that you need a moving platform to get the right jump height?
