Sonic 1 Bugs

There's like, only one real bug listed there. :P

 

The ripple effect in LZ?

 

Jumping next to some objects fails to send you into a spin
GHZ bg vertically scrolls backwards
Rolling into a wall holding the opposite direction results in walkpushing

I know there's more, but I didn't spot them on a quick GHZ run.

 

That rolling bad guy in Spring Yard Zone. One of his frames of animation is messed up.

 

In Sonic 1, holding right when you're moving above Sonic's "max" running speed resets his speed to the max. In Sonic 2/CD, this only happens during "controlled" jumps (jumps when you weren't rolling to start). In Sonic 3/K, this doesn't happen at all.
You would also fix a lot of collision errors by making wall tiles totally solid.

 

These are the bugs I think any Sonic 1 hack should get rid of before getting started:

-The water scrolling bug at the title screen.
-The "Sonic jumps without rolling sometimes" bug.
-The level resizing when going too fast through the infamous S-tube.
-The unused caterkiller tiles messing up the roller's graphics.
-The big raising platforms between spikes should have their sides solid, so you can't fall into the pits. (they even fixed that in the Sonic 2 early alpha, didn't they?)
-Some "walkpusing" that may happen, as said above. Also happens when you press the eggtrap going fast to the left, so Sonic keeps pusing it till it disappears.
-Sprites without the white stripe.
-The leftmost emblems at the end of one of Labyrinth's acts (forgot which one) tend to mess up because their graphics aren't still loaded.
-Those "secret" buggy monitors at Scrap Brain just shouldn't be there.
-Make Sonic stick properly at the circular thingies in SBZ, since he tends to slip and fall to the ground when less expected. There must be some small thing they didn't take into account until Sonic CD... or did that happpen in there as well?

Many other things mentioned in this topic, I see as intentional features.

 

The spike "bug" is my favourite example of that.

 

No, it was fixed on Sonic1GBA....

Nope, still does it on Sonic CD, just not as much.

 

http://youtube.com/watch?v=YcNAYgs32ug

 

Oh, that's right... They were just turned into small moving platforms in the Sonic 2 proto. But then, that object was later developed into the completely solid Hill Top rising platforms...

Ok, perhaps they were just intended to be that way since they were planned.

 

I don't understand why this attitude is so prevalent. It's a damage scheme unlike anything else in the game, they actually fixed it to be consistent with everything else in a later revision, and given the profusion of obvious bugs in sonic 1 in general there's nothing pointing towards it being a design decision.

 

You're supposed to be able to reach them by way of the hidden blocks that appear and disappear. However they don't show up like they should because of the blocks being generated "out of order" (due to the fact they generate from bottom-up in an area where there's a lot of other objects conflicting with this). So that in my mind is the real bug to fix.

TRICK FOR THOSE WHO DON'T KNOW: Hit the switch and jump on the long platform that comes out. Get all the way against the wall. Then run over to the left and jump. If done at the right time, you'll be able to see and jump on the hidden blocks and make it to the top.

 

They could have made the same harm enemies do, but Naka made a different routine just for the spikes. How do you explain that?

 

And die if you hit them while being hurt.

 

No.
Look at all the things that can hurt you in Sonic 1.
Spikes are the Only ones that you can touch the sides without getting hurt. They also make a different sound.
These two things necessitated a second routine. If the flashing invulnerability mechanism was added later, it would be quite easy to miss adding it to the spike routine.

 

Don't forget that the official bug logging database for the original Sonic release clearly recognizes the scenario in question as a BUG to be FIXED. The desired behavior was that Sonic would be able to treat atop the spikes while invincible after getting hurt. Whichever tester found this bug was most likely basing his findings on the desired behavior described in the original design document. Testers seldom make guesses about what they "think" should have happened. That is not their job.

Does anyone even still have these databases?