Dan Chisarick stated: > >Just wondering if anyone has any good stories of an older game they >were playing that was somehow unbeatable due to a coding flaw, or just >downright not fun for design reasons.
It's a console game, but the Atari 7800 port of Impossible Mission is well known now for being truly impossible. They neglected to allow players to search the computer terminals for the puzzle pieces needed. (You can only activiate the terminal, not search it.) This only applies to the NTSC (North American) version. The PAL (European) version did not have this bug. >Last, and somewhat humorously, ever type in a game in Basic or assembly >from a magazine, and it didn't work? Seems the feature title ALWAYS >had some little typo in it that would require you to buy next month's >issue to resolve? :) Considering how long the listings were, I rarely typed in most of them. Usually when there was a bug, it was a typo on my part. What I hated was when there'd be some PRINT statement with a bunch of spaces in it. How do you tell how many there were? I'd usually end up running the game and then adjusting the spacing after seeing it on the screen. -- Lee K. Seitz [EMAIL PROTECTED] ---------------------------------------------------------------------- This message was sent to you because you are currently subscribed to the swcollect mailing list. To unsubscribe, send mail to [EMAIL PROTECTED] with a subject of 'unsubscribe swcollect' Archives are available at: http://www.mail-archive.com/[EMAIL PROTECTED]/
