Club PA 2.0 has arrived! If you'd like to access some extra PA content and help support the forums, check it out at patreon.com/ClubPA
The image size limit has been raised to 1mb! Anything larger than that should be linked to. This is a HARD limit, please do not abuse it.
Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
08/18/2011 - AnonymousShare:Share On TwitterShare On Facebook
Suppose you found a bug in a game that rendered a console unplayable? Suppose it was something akin to the original Myth II Uninstall problem where it basically formatted your hard drive, only worse?
There was a game that was released in the last 10 years that had a peculiar issue toward the end where you could crash the title just before one of the end bosses by doing a manual save just as it was autosaving.
If you did, it caused the console kernel to overwrite itself, rendering the entire unit non-functional.
After causing this to happen once, I was asked to replicate the issue in front of people who made a lot more money than I did. After sixteen hours of play, I, again, saved while the game was autosaving, and watched with everyone else in the room as the screen turned black and the console shut down. Attempting to boot it up didn’t even result in an error screen, it would just power on and then shut back down.
(To me) “You can do this every time?”
“If I want to, yeah.”
(To a marketing guy) “How long until we’re supposed to ship?”
“We’re supposed to go gold in a week.”
(To a developer) “How long would this take to fix?”
“We’ll have to rewrite the entire file structure. Weeks, at least. Probably months.”