[1] Pressing the menu button while Link is walking up or down automatically on the stairs:
Problem: Two stair sounds will play instead of one. Also, Link will sometimes reverse his direction. The menu will also shift up or down after the second sound plays, which seems to only happen when you press the menu button at the very bottom or top of the stairs.
Fix: The easiest fix would be to disable the menu while walking on stairs. The original game does this anyway. Actually, it pauses EVERYTHING in ALL auto transitions, even enemies, and it locks ALL buttons.
Oops, that one slipped through. I already fixed the sword vs stairs.
At first I made it like in the original, locking everything while you were moving on the stairs. After thinking about it for a while I felt that it was unnecessarily unrealistic, so I made it so that enemies etc. continues in realtime. The same also goes for jumping from ledges and during room transitions. For these events I'm using a variable called Link_Status_Special. Glitches like this appear when I forget to lock functions if Link_Status_Special does not have it's default value.
[2] Pressing the sword button while Link is walking up or down automatically on the stairs:
Problem: Two stair sounds will play, Link's sword sound will play but he does not slash his sword and Link will also freeze in place for a short time. After Link freezes, he will either continue walking upward or he will reverse direction.
There may be other keys that have a similar effect as in these first two glitches.
Fix: Obvious. Make sure Link can't do anything in the middle of auto-walking.
Found and fixed. See above.
[3] Poking wall:
Problem: If you're powering up your sword (holding the sword button) and holding a directional key while poking a wall, then if you let off of the sword key while still pressing that directional key into the wall, Link will continue to hold his sword out, poking the wall. His sword will continue to charge up when doing this, even though you are no longer pressing the sword key.
Fix: Not sure how you're coding this so I haven't got much of an idea how to fix it.
However, I did notice that, in the original, poking the wall does not reset your powering up of the sword like you have it do in your game. Instead, the original game pauses the powering up for a short time every time you tap the wall, then it continues to power up. Just in case you want to make it EXACTLY like the original. If not, your way is totally fine.
Hhmm. Interesting. I'll have to look into it, but it doesn't look to complicated to fix. My guess is that releasing the sword button negates charging, but not (yet) poking. I'm using a single variable called Link_Status for all of link's actions. It should be just a matter of adding a new condition to releasing the sword button. "If released while poking do the same as when released while charging", or something similar.
Continuing to charge while poking would cause some small problems I'd need to overcome so I'll leave it as it is.
[4] Spin attack sparks:
Problem: When doing a spin attack underneath a layer (i.e. floor above you) you will see the sword sparks above that layer.
Fix: Should be just a simple depth problem. On an interesting note, I found that the original game actually had a problem with depth in certain areas as well, but usually when swimming in the water. I just seem to stumble upon these minor things for some reason. ^_^
Okay, that shouldn't be too much trouble to fix. This is something left over from creating two walking depths. This is just the kind of stuff I wouldn't find on my own.
[5] Room scrolling:
Problem: If you press the sword or menu key when scrolling/transitioning into another room, BAD BAD things happen.
Fix: Don't let any key work during any auto scroll or walk.
Check point 1 and 2. The sword button has already been fixed. The menu button will be fixed shortly.
Hope that helps! Even with all those glitches, I actually found your tech demo surprisingly solid. A lot of people don't realize just how complex something like this can be. Seriously, this demo is great. I'll continue testing and I'll let you know if I find more glitches. 
I'll get on these glitches before I release the next demo. This will means some delay, but oh well. At least the next one will be glitch-free (*fingers crossed*)
