Tag Archives: Commodore 64

Computer Computer Games

This is hopefully the first of many articles in which I review hacking, programming, and other games that mostly involve in-game interaction with computers. There are a ton of these, from classics like Infocom’s Deadline and A Mind Forever Voyaging and Activision’s Hacker and Portal, all released in the early to mid 80s, SysOp and/or BBS hacking simulator door games I played on BBSes in the mid 90s, all the way to the crop of modern games meant to either leverage, or in many cases teach, coding and automation concepts in a “gamified” way. I hope to explore dozens of these games, but I’m starting off with a few that have been collecting dust in my backlog for ages.

Given my love for vintage computing, including the Commodore Amiga and the BBS scene, two topics both relevant to Digital: A Love Story, I’d been meaning to play this one since first hearing about it… which was like 15 years ago. 😒

So yeah, what I knew about DALS was that it was a narrative heavy game whose gameplay mostly involved calling various BBSes and reading and sending messages. What I didn’t know is that it is actually much more of a visual novel than any kind of simulation. In fact, it’s built on the well-known visual novel engine Ren’Py. Evidently a lot of cool trickery went into making this feel like more of an immersive, faux computing simulation though, as it’s reasonably effective at it. Of course, it’s far from perfect, but while a giant nerd like me could get all “ackchyually…” about dumb stuff like DTMF tone and modem handshake noise accuracy, there are bigger fish to fry.

Reading a message on a board in DALS. Gotta find that warez!
“Reading a message on a board in DALS. Gotta find that warez!”

First, the entire BBS experience is extremely dumbed down. You dial a BBS and are treated to a welcome screen that looks more like a BBS advertisement (though this isn’t totally inaccurate – such welcome screens weren’t uncommon.) You then need to logon, which requires only a password and not actually a username, oddly. From there, all you can really do is read and reply to public messages and send private message the users on the BBS. The whole experience is very simple, reminding me a lot of the BBSes in Interplay’s Neuromancer adaption (which I reviewed years ago here.) It absolutely gets the job done in terms of gameplay though, and I think some abstraction is probably necessary, but regardless, these BBSes only barely resemble the real thing.

It’s all a little anachronistic too. The game’s intro/title screen is based on the Commodore 64, yet the rest of the game’s interface is based on Amiga Workbench 1.x. The fonts, music, graphics; none of it quite adds up. It’s even mouse driven, though this is somewhat forgivable as even though BBSes weren’t generally mouse based, basing the game’s interface on a mouse driven OS made this seem much more plausible. Despite these nitpicks, it’s effective enough in my mind. I mean, if someone like me could get immersed in it, it’ll surely work on someone less familiar with the tech.

Calling the new board I was just recommended.
“Calling the new board I was just recommended.”

Disappointingly, despite how absolutely crucial communication via messages is to the gameplay, you don’t actually get to see the messages your character writes. While I didn’t expect you to be able to free-form write messages yourself, you don’t even get to see what your character wrote. Instead, it’s only hinted at by the subject lines of the messages people are replying to. Kind of weird, but it’s also sort of cool that it leaves the contents of the messages open to interpretation. Given that your character is also kind of a tabula rasa, that’s probably for the best. That said, as mentioned, this is actually a visual novel, not some kind of slick hacking simulator, so the fact that it’s even this functional is remarkable.

Unfortunately the gameplay starts to feel repetitive quite quickly, as it mostly just involves dialing a BBS, reading and replying to messages, logging off, and moving on to the next board. Sometimes it’s not clear where you need to call next, or how to get into a system, but overall it’s all fairly simple. With a time to beat of around 2 hours, I appreciate that it doesn’t quite overstay its welcome either. Still, I would have personally liked to see more tension here. What I mean by that is that a big part of BBSing back in the day was having to wait hours, maybe even days to get a response to a greatly anticipated message, or for your daily allowance of time, game turns, or download credits on a particular board to reset, but none of that is really represented here.

Sweet welcome screen, though that's not quite ANSI.
“Sweet welcome screen, though that’s not quite ANSI.”

Surprisingly, I think where the game really stumbles is the story itself. Before playing it I imagined a really involved, lengthy narrative as the main character starts to befriend various people on these BBSes, perhaps build a reputation of sorts, and the romantic relationship referenced by the title blossoms. Instead, it all feels fairly surface level, especially the relationship, which progresses incredibly quickly to the point that I barely felt much towards the character you have this relationship with. It all feels a little rushed and shallow as a result. Beyond that, it cribs from Gibson pretty hard, but then, what good cyberpunk story doesn’t?

Digital: A Love Story is available for free from the author’s website, so if any of this sounds interesting to you, I’d recommend giving it a shot. There are much worse ways to spend two hours.

Speaking of slick hacking simulators, Introversion’s Uplink is just that, and really, one of the progenitors of the entire modern genre. After playing Introversion’s WarGames inspired global thermonuclear war focused light strategy game Defcon, I briefly became quite intrigued by Introversion Software and their innovative, stylish, often somewhat toy-like games that remind me of highly evolved products of the same underground computer scene I came up in. This is when I bought Uplink and a few other games of theirs, though somehow, despite thinking it looked awesome, I never actually got around to trying it.

Killing my boy Dan in the original Uplink. Sorry, bud!
“Killing my boy Dan in the original Uplink. Sorry, bud!”

Uplink takes place in some presumably cyberpunky version of (then future) 2010 in which you sign up with the Uplink Corporation as a freelance hacker. Through them you take on jobs/missions, monitor relevant news articles, update your software tools, and upgrade your gateway computer – something of a “jumpbox” that you do all of your nefarious deeds through. Once you have one or more missions, you’re emailed a more detailed description of your objective including the name and IP address of the server you need to carry them out with. You’ll need to connect to the server, but oh no, not directly, as you’d be traced and caught in no time. Instead, you’ll need to bounce your connection through multiple intermediary servers to increase the time it takes to trace you. It also helps if at least one of them is a server you can easily gain admin access to so you can clear the logs of your connection being routed through it to break that chain, as it were.

From there, things only get more complex. Some missions have you deleting files, some have you downloading and emailing files, sometimes needing to decrypt them first. Sometimes you’ll need to hack an institution to view or change some records, or move some money around, and sometimes you’ll need to trace someone else’s bank transfers, or even track down a rival hacker. The more difficult missions require a complex series of subtasks, and some may even have time limits. The mechanisms you need to work around are more difficult too. At first, just using a cracker to brute force an admin password is good enough. Later on, you’ll need to break encryption keys, provide voice imprints, and maybe even route your connections through other company servers. Sometimes you’ll need to disable monitoring servers, proxy servers, and firewalls too.

Providing a voice sample to work my way into this Logic Systems server.
“Providing a voice sample to work my way into this Logic Systems server.”

The variety and complexity of these tasks ties smartly into the game’s progression system. Each level of mission gives you more and more cash, which lets you buy new software tools, update old ones, and upgrade your gateway’s hardware, allowing you to handle higher tier missions, which grant you even more money. Repeat! At least, that’s how the game is meant to be played. A cheeky strategy I found a lot of references to online is to hack a bank early on to give yourself a massive injection of funds and shortcut a lot of this progression. Of course, you’ll still need to gain experience to have higher level missions available to you, though having all of the best tools and the fastest hardware would certainly make that easier.

Regardless of how you get there, this all culminates as you reach the hardest missions, which often require gaining access to a corporate LAN and mapping out and hacking every server in the network to reach your target. Each hack may require bypassing multiple of the above mentioned roadblocks, and you’ll have an admin aggressively chasing you at every step too. Fun!

Providing a voice sample, but this time in the Uplink OS mod.
“Providing a voice sample, but this time in the Uplink OS mod.”

One of the best things about Uplink, and honestly, all the best entries in this genre, is that it is quite immersive. You’re interacting with a virtual computer system of some sort, and given that you’re actually interacting with a real computer system of some sort to play the game, it’s not a massive leap to feel like you’re actually really doing something. Couple this with the realistic sense of isolation you experience playing a single character in first person (narratively speaking) staring at a somewhat open-ended GUI and/or a blinking cursor at a CLI prompt, with your only contacts being an occasional email or chat message. If you’ve ever been there yourself, and I’d wager most of us have in one way or another, it’s extremely effective.

Uplink suffers some here in that it was developed and released in the early 2000s. It still has a lot of now anachronistic references to “dialing into” servers and its GUI, while looking like a slick Window Manager you might have used with X back in the day, is a little clunky by today’s standards. Text boxes need to have their default text manually cleared, and have other weird input limitations, for example. The game also doesn’t handle modern screen resolutions very well, either. Thankfully, there are mods for all of that, some of which I almost hesitate to call mods as they replace the entire executable becoming what is more or less a whole new client for the game. The most popular of these is probably Uplink OS. I would highly recommend anyone looking to play Uplink these days just go ahead and start with something like Uplink OS, though with the caveat that you know that some of these UI and seemingly minor gameplay enhancements actually heavily affect the gameplay itself. That, and in Uplink OS’s case, even the aesthetics are quite different. While I prefer some elements of the original Uplink, Uplink OS was clearly a labor of love and its benefits outweigh its negatives in my opinion.

Uplink OS replaces the world map with a boring hexagon, but I love the Randomize button!
“Uplink OS replaces the world map with a boring hexagon, but I love the Randomize button!”

I started off with the original Uplink and didn’t find it too annoying to work around the UI and technical imitations of it, but at some point, maybe 10 hours in, I found myself almost hard locked from proceeding any further: I needed money to purchase some tools to do the new mission types at my current level, but had exhausted all of the lower tier missions I could actually handle. This is, admittedly, totally my own fault for not managing my funds better, but hey, this seemed like a good time to check out Uplink OS. Making a new character and being much more methodical this time (thanks to understanding the game a lot better) paired with a much more responsive UI, meant progression was waaaaay faster. Unfortunately I made another silly mistake. I was learning the ins and outs of hacking LANs when I finally completed my mission and increased the game speed to wait for the news to report on my deeds. Instead, I received my first game over screen – busted! This wasn’t really game over, but I essentially would need to work my way up from zero. As much as that sucked, I was much more annoyed by not knowing how I could have been caught. Regardless, having put probably 25-30 hours into Uplink, I’d have probably thrown in the towel if I hadn’t sneakily backed up my local save file at some point before this.

With that, I decided to change focus. When you make it far enough into the game, you start being offered missions out-of-band, which lead to a more linear set of special missions. With my second playthrough going so fast, I never got to the calendar date in which the first of these missions would be offered to me, so determined to beat the game legitimately at least once, I restored my game, did a few more missions to get a little more cash, then put the game’s clock on fast forward. At a high level, the story consists of two corporations vying against each other: one that wants to destroy the Internet because they feel like it has become corrupted by government and corporate control from its once great position as a bastion of free speech, while the other would rather, you know, NOT destroy the entire Internet. Of course, you’re able to choose either side, or ignore the entire thing (although that may eventually turn out badly for you if things have already been set into motion.) Personally, I chose Arunmor because at first ARC’s motives seemed more anti-social, plus being a professional hacker, my character would be out of work if the Internet were to cease to exist. I’m nothing if not practical!

Deleting a system's logs via CLI to cover my tracks.
“Deleting a system’s logs via CLI to cover my tracks.”

That said, the story feels a little rushed and could have perhaps used a bit more drama, even if just in the form of more emails, news articles, and other text, but I do appreciate how there are a lot of little clues about this whole plotline sprinkled throughout the game. More of this would have made the story that much better, though. As for the story missions themselves, beyond the new mechanics introduced by the Faith vs Revelation viruses, they utilize a little bit of everything you’ve learned up to this point. It’s a simple but smart design, and my final mission for Arunmor, which involved racing against the spread of the Revelation virus, was surprisingly tense.

Perhaps one day I’ll return to follow the ARC storyline, but for now I’m ready to move on to something else. In any case, Uplink is a bona fide classic. I’m looking forward to seeing how other games have attempted to evolve the formula, however.

I remember hearing a lot about Her Story when it was released back in 2015. It seemed like everyone was playing it, but I didn’t know much about it apart from it supposedly being one of the more impressive entries in a wave of FMV revival games. I knew it involved watching a lot of video clips, and that was about it. So what does it have to do with this theme?

Making my screen a little cluttered to show off the UI in Her Story.
“Making my screen a little cluttered to show off the UI in Her Story.”

Her Story puts you in the role of some kind of an investigator who is placed in front of an old PC with access to a curated archive of police interview footage. The interviews focus on a single person, Hannah Smith, the wife of a man found dead in their home, seemingly murdered. You’re not given much in the way of background on who you are, why you’re reviewing this data, or what your goal really is. One would assume you’re a detective, and you’re trying to determine the details of the murder, including whether or not Hannah is guilty or at least a legitimate suspect. Almost all of the interaction in Her Story involves typing simple search queries into this video database application and reviewing the results. Mostly this is in the form of keywords and phrases, but you can also add your own tags to individual clips, which is pretty neat. One interesting aspect of this is that each search will only let you see the first 5 results, which means narrowing down and refining your searches is practically a requirement, especially if you want to try turning over every last stone.

The simulation here is surprisingly competent for a game that, well, isn’t really about that. The machine you’re in front of is modeled after Windows 95 and you’re able to interact with it with a reasonable amount of fidelity – there are multiple programs you can open, including a little game that someone had apparently tried to delete, you can move windows around, etc. Probably the most interesting aspect of this is the “glare” effect which adds a not-at-all subtle CRT effect to the screen – scan lines, a slight curve to the picture, dust on the screen itself, and reflections in the form of the fluorescent lights behind you, occasional lights from passing police cars, and even your own character’s reflection at times. This is the type of feature that a lot of people might immediately turn off, but I’m personally really fond of Her Story’s implementation of it, and I feel that it does just as much to set the mood as the ambient soundtrack in the background.

Hannah tells us about her favorite video games.
“Hannah tells us about her favorite video games.”

What really intrigued me about Her Story was the mysterious nature of many of the details of the story, both those expected (the obvious “whodunit?” of it all) and perhaps surprising. I obviously need to tip-toe around potential spoilers here, but the biggest mystery is in regards to Hannah’s identity. Is she who she says she is? It’s blatantly clear that there is some kind of manipulation going on, but it seems as if the game goes to lengths to specifically throw you off the scent, tossing out hints to support and oppose both of the two main conclusions you’re likely to draw. Personally, I went with the… err, let’s say “same person” conclusion myself due to some phrasing that is used here and there and some of the overall manipulative behavior observed, though I later watched a video on YouTube that convinced me that the other option was probably correct. Regardless, the game purposely leaves a lot of this, a lot of everything, open to interpretation. In fact, before I was even 50% through the archive I thought I had a fairly good idea of what happened, but with no idea how I was supposed to “beat” the game. While that becomes more clear eventually, the game ends without answering many of these questions, and a detail given at the very end still managed to surprise me while re-framing a few things at the same time.

It’s short, despite clocking in at a few hours tops, and it’s minimally interactive for a “game” to boot, Her Story’s execution really worked for me, and its story is one that I won’t forget any time soon. Part of this is thanks to the performance of Viva Seifert, but I also want to seek out more of Sam Barlow’s games, including Telling Lies, which is something of a spiritual successor to Her Story and includes a similar style of gameplay, which means it might end up in a future installment of this series.

The First Four

Maybe it’s the holidays, but I was recently hit by a random streak of nostalgia around my family’s first ever computer, the Commodore VIC-20. I’m guessing it was sometime around 1985 or 1986 that my dad, almost certainly inspired by another family that we became friends with, the father being a huge Commodore 64 nerd, brought us home a VIC-20. We quickly amassed some game cartridges, a tape deck and a couple of tapes filled with demos and games, a joystick, and soon enough a Zenith ZVM-123 monochrome monitor so my brother and I weren’t tying up the family TV. I thought it would be fun to go back and revisit those first four cartridge-based games. This is where it all started for me!

Fast Eddie plays exactly how you might imagine from this screen.
“Fast Eddie plays exactly how you might imagine from this screen.”

Fast Eddie is a single screen side-perspective platformer similar to more well-known titles like Lode Runner, Jumpman, and Donkey Kong. Your objective is to avoid these little mushroom looking “Sneaker” dudes while you climb ladders up and down multiple levels collecting “prizes” that appear at random. There’s a really tall Sneaker on the top level (called the “High-Top”) who will shrink in height with each prize you collect, eventually getting short enough for Eddie to jump over, which completes the stage. It’s pretty simple, but even on the VIC-20 it feels reasonably fast and responsive. The challenge is in timing your movements with the fast moving Sneakers, which is easy to do, but the faster you try to clear a level, the more likely you are to make a mistake and lose a life. I also checked out the Commodore 64 version while I was at it, which despite being more colorful with higher resolution, well, everything, doesn’t have quite the same charm as the VIC-20 version to me. Still, the more responsive and smoother feeling controls make it the superior version.

Despite the fact that I recall liking Fast Eddie as a kid, it wasn’t my favorite, nor did it get a ton of playtime in my house. I think that’s likely because, like so many early arcade style games, the formula is almost immediately obvious and doesn’t deviate much from what is established at the start in anything but difficulty. Once you “figure it out” the only real drive to keep playing is to push yourself to further levels and higher scores. That said, it is fairly addictive, and when I replayed it for the first time in preparation for writing this article, I ended up playing it for a lot longer than originally planned. Not bad!

Despite the clown car colors, killing Klingons is serious business.
“Despite the clown car colors, killing Klingons is serious business.”

I never got into this next game as a kid, likely confused by its multiple perspectives and chaotic action, but I have fond memories of my brother camping out in front of this game for hours, filling little notepads up with diagrams and drawings. Having put a fair amount of time into the game while revisiting it for this post, I’m guessing these were simply sketches of ships and maybe a log of how far he made it and his scores, because an RPG or adventure game this is not; there’s really nothing to map nor clues to jot down.

Despite its title, Star Trek: Strategic Operations Simulator is purely an arcade action game, but one that crams a fair amount of ingenuity into its simple concept. On the top left of the screen you have indicators showing your health, photon torpedoes, and warp power. On the top right, you see an overhead view of your ship and the space around it in a style very similar to Asteroids. On the bottom of the screen, you see a first person perspective from the viewscreen of your ship (I assume the USS Enterprise?) which is synchronized with the action in the top down view. Pretty nifty. You fly around these little “sectors” shooting Klingon battlecruisers who are either attacking you, or focused on attacking your starbases. You can fly to a starbase to get a small bump in health, torpedoes, and warp. Your normal attack is an unlimited, rapid fire blast that is supposed to represent your ship’s phasers, but you can also launch a torpedo which has a devastating area of effect, and warping is simply a speed boost which I actually never found all that much use for. Once you dispatch all of the enemies, hopefully saving your starbases in the process, your score is tallied up and you move to the next sector map. There are some simple boss stages every 4 or 5 sectors as well. All in all, it didn’t really hook me, but it was fun, and I can imagine some people really enjoying it.

I tried out the Commodore 64 port of the game as well, and as with most games that exist on both platforms, while the gameplay is more or less identical, the graphics and sound are greatly improved (you can actually tell what the ships are supposed to be!) and control is a little more responsive, although it’s not bad in the VIC-20 port. The experience was so much more enjoyable that I ended up playing for quite awhile, far surpassing my previous high score on the VIC-20 version. Interestingly, the original game both of these ports are based on is a 1982 Sega arcade game. The arcade game looks vaguely familiar, but I don’t think I ever played growing up. Boasting impressive hi-res vector graphics and some digitized sound samples, it looks damn cool, although the gameplay is basically the same as what is presented in the home computer versions.

Frogger with a weird perspective and terrible controls? Sign me up!
“Frogger with a weird perspective and terrible controls? Sign me up!”

Out of the four of these games, there’s only one I had almost zero recollection of and that’s because, well, we barely played it, and we barely played it because it fucking sucked. Congo Bongo is a platformer that plays like a sloppy combination of Donkey Kong, Pitfall!, and Frogger, depending on which level you play. That is, the first level has much more of a Donkey Kong vibe, while the second brings in those Frogger elements. The key difference is that the levels are shown from something of a skewed isometric perspective. Different enough to keep the lawyers away, I guess. The wacky perspective, terrible, jumpy animations which make dodging coconuts and hopping onto moving platforms feel excruciatingly inaccurate, and the less than responsive joystick controls made a game that probably already relied a bit too much on memorization just one big bum out. I ended up beating the first stage (a feat I don’t recall if I ever managed as a kid) after about a billion tries but, running out of patience, abused TheC64’s save states to get through the second. That was it though, that’s the game! In theory, those two levels repeat with a higher difficulty 4 more times, but there’s no way I was going to go any further, at least not with this version.

This game was ported all over the place, however, and morbidly curious, I decided to check out the very similar Commodore 64 version of the game. I’m happy to report that while it looks quite close, it has more colors, better sprites, better animations, slightly better sound, and vastly superior controls. The monkeys even properly harass you in this version! Still only two levels though. Interestingly, the Commodore 64 actually had a second port released a couple of years later in 1985 which had much nicer graphics sporting a much better take on the arcade version’s isometric perspective, all 4 levels from arcade, and a lot of other original elements intact. Unfortunately the cracked dump I played glitched out on the last level so I couldn’t legitimately beat it, but hey, not too shabby! In either case, I’d have been a lot more satisfied with the Commodore 64 versions of the game than I was with this awful VIC-20 one. Honestly, the best part was the awesome box with its colorful cartoony characters and massive Sega logo.

Oh, and yes, believe it or not this game was based on an arcade game. The arcade Congo Bongo actually had beautiful graphics for the time and, while I’m sure it was still a quarter sucking kick in the balls, the gameplay looks a lot smoother. As a kid I had no idea it was ever in the arcade, and I didn’t know until researching the game for this replay that there’s actually an interesting story behind the game being something of a troll of Nintendo over a lawsuit related to Donkey Kong. I’ve never seen that event referenced before, but I wonder if that’s where the Sega and Nintendo beef all started?

Actually, Spider City doesn't look half bad.
“Actually, Spider City doesn’t look half bad.”

My favorite of these games as a kid was Spider City, AKA Flash Gordon. Spider City was a side-scrolling shooter, likely influenced by the arcade classic Defender. On the top half of the screen is a view of your ship, and on the bottom a sort of mini-map showing you the tunnel system you’re navigating. The map was crucial for locating your objective, the hordes of hatching spider warriors you needed to murder. Of course, you also need to avoid debris, patrol ships, and other hazards, as well as rescue captured spacemen. I remember thinking the game looked good as a kid, but… eh? Still, of these four games it does the most with the VIC’s meager sound capabilities by a longshot.

In retrospect, dazzling graphics aside, I don’t know why it appealed to me quite so much back then, other than I remember wanting to ape my brother’s deep fascination with Star Trek: Strategic Operations Simulator by diving deep into and mastering a game of my own. That said, like Star Trek: SOS, there wasn’t actually all that much to master. Fly through the map avoiding and/or shooting everything on the screen (except for spacemen, which you could fly over to rescue) and seek out the hatching pods, mow down the hatching spiders which would hopefully grant your ship a temporary shield, then rinse and repeat until the entire map is clear. There were also these “disruptor” zones which moved around the map and would fill your screen with debris when you entered one, though you could shoot the generator inside of them to freeze them temporarily if you couldn’t simply avoid them. Of course, all of these details are fairly obtuse and unintuitive, and I’m mostly only able to talk about them clearly because I read the manual.

Unlike the rest of these games, Spider City didn’t have a Commodore 64 port. In fact, the only other place it appeared was the Atari 8-bit computers. Odd, given that it’s actually fairly fun.

These days I think I probably prefer Fast Eddie to Spider City, but I still have to give Spider City major credit for being the first video game I ever loved. Additional takeaways? While I’m endlessly grateful to my dad for bringing home my first ever personal computer, I mean, I have multiple hobbies and a career to thank for my interest in computers, I definitely wish it was a Commodore 64 instead of a VIC-20. Oh well. As an aside, I’d love to make a part two to this if I can ever figure out exactly what those cassette tapes I mentioned having were. I have no idea if they were commercial releases or otherwise widely distributed, or if some dude at whatever local computer shop my dad got this stuff from cobbled them together himself. A mystery for another day. *shrug*

Apologies for the poor quality pictures – there are some major color inaccuracies, for instance. These were photos from my TV (usually at night, even) rather than actual screenshots. Box art stolen from LaunchBox’s games database.