You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the bonus game sprite (sprite 82) is used in a level with sprite memory setting 0x08, a small visual bug will occur here:
Here, there is a stray bonus game block that infinitely wraps around the screen horizontally. I remember encountering this bug in SA-1 1.32 as well but never thought much about it. Why would anyone set the sprite memory to 0x08 here? Well, maybe it is because people would like to extend the bonus game level and add more enemies to pose some challenge. It would be nice if this bug is fixed. Thanks!
The text was updated successfully, but these errors were encountered:
This seems to be caused by the sprite spawning the 9 boxes not being erased afterwards, which then gets handled like one of the boxes. This doesn't happen in other sprite headers because the spawner actually gets replaced with one of the 9 boxes (since its sprite slot is 9, and it spawns the boxes in slots 1-9), but using sprite header 8 makes it spawn in slot 19 which doesn't get replaced.
I made a simple patch here which fixes the issue.
Although the patch doesn't fix the whole bonus game roulette itself wrapping around every screen (which I should've specified myself), it does fix that stray bonus game box wrapping across the screen horizontally. Thanks for the fix! I will see what I can do about that other bug.
If the bonus game sprite (sprite 82) is used in a level with sprite memory setting 0x08, a small visual bug will occur here:
Here, there is a stray bonus game block that infinitely wraps around the screen horizontally. I remember encountering this bug in SA-1 1.32 as well but never thought much about it. Why would anyone set the sprite memory to 0x08 here? Well, maybe it is because people would like to extend the bonus game level and add more enemies to pose some challenge. It would be nice if this bug is fixed. Thanks!
The text was updated successfully, but these errors were encountered: