This a video featuring the developer behind the game Sonic 3D Blast. I had never heard of this "secret", but about 25 seconds into the video, I kne...
For further actions, you may consider blocking this person and/or reporting abuse
When I first entered the industry I was at a company who had written a custom CMS in ASP classic (pre-.NET). I noticed that every single file had the following statement at the top:
After a couple of weeks I looked up it in the docs and found out, to my horror, that it's effectively saying "if there is a runtime error, just skip the offending expression and keep executing like everything is cool".
You could also do things like
On Error GoTo SomeFunction
that would do exactly what you'd think it might....Talk about dangerous programming! Hah.
Nice. I'm sure everyone, with enough experience, has a tale or two like this.
When I was learning C#, that's pretty much exactly what I did. Just try catch everything and have the catch do absolutely nothing. There I was, wondering why my application never did what I expected!
Nice! When in doubt, catch everything and silently suppress it. Nothing to see here.
It's amazing how the people can improvise when there are restrictions, I wonder why this is not being done in the actual gen games when something brokes.
This a very clever way to avoid the player's frustration from a frozen screen or load bug.
This is so great, makes me want to play the game again. Right after I'm done with Sonia Mania...