Warning: The interview below discusses Blood Pact, a game with
Domination/Submission themes, some tentacles, a succubus goddess, a
lust spell, and other elements not discussed in the interview, but
available both in the review’s content warning, and the content
warning page of the game itself.
As long time readers may know, I’m a big fan of learning from the older elements of game development history. So it was a little bit of a pleasure to have a brief chat with one of the creators of Tanglewood, Matt Phillips of Big Evil Corp, to get a glimpse of the kind of things you have to deal with when using a development kit from 1993, on a well known 16-bit system, to make a game in 2018.
TMW: As someone who grew up with older systems, it’s quite nice to see folks still making things for those older systems, what inspired you to go down that route?
The kid in me wouldn’t let it go – it’s something I’ve wanted to do since I was a 9 year old, proud Mega Drive owner. I also had access to a Commodore 64, so I was no stranger to the delights (and frustrations) of programming from an early age, and the dream never faded all the way through to adulthood.
TMW: There’s a lot that folks don’t really know about making games for older systems, so I’d like to start by indulging folks’ curiosity on creating a game for an older platform. Knowing that you were going to make Genesis cartridges, what sort of obstacles did you face, in the coding and hardware end?
The biggest problem we faced was that none of this old equipment works reliably any more. The devkit is from 1993, and parts fail on a regular basis. It’s quite frustrating when you’ve spent a few hours debugging a problem in the game, only to find out your code wasn’t at fault – it was another problem with the machine! When it works, it works BRILLIANTLY, though. I’ve yet to find a modern alternative that does such a good job.
Learning the language was a tough one, since resources for this kind of thing are few and far between these days. Further into development I started finding other 68000 programmers to talk to, and we struggled together to figure out some of the more intricate parts of the Mega Drive, and banded together to figure out optimisation issues.
TMW: Similarly, when building a game for an older system, there are limitations. What sort of things did you want to put in, but found wouldn’t really work?
The Mega Drive’s Achilles heel is its limited palette – it has 4 palettes of 16 colours, but three of those are reserved for transparency, so only 61 colours can be displayed on screen at any one time. Even worse, there are deeper rules about how those colours can be assigned to pixels, so we had to write a lot of tools to help arrange everything. Thankfully we found the right artists for the job, and they did most of the heavy lifting when it came to arranging colour usage.
Another issue is the slow CPU – although it certainly wasn’t at the time, the 68000 was a luxury compared to other consoles. There were a few things I had to cull in order for the game to run smoothly, the one that hurt the most was buoyancy on physics objects. Originally, Fuzzls could float on water, and would have been hilarious, but I had to rip it all out because it was only a gimmick and was very heavy on CPU usage.
TMW: Now, one of the hot button issues of the day is the games industry’s preservation (or lack thereof) … What would you, once the game’s reached the end of its sales life, like to do to preserve it for the future?
This is something I’ve thought a lot about, and I’d like to be the anti-corporation in all of this and release the game’s source on github on its 1 year anniversary – complete with raw assets. I can’t see sales coming in strong after a year, people would benefit more from studying – and maybe laughing at – the source code.
TMW: Well, thank you for talking to us, Matt, and, in conclusion, what sort of advice would you give to aspiring game devs of the future?
Make games. Make a lot of games. Just keep making games. Small games, stupid games, experimental games, ambitious games, games on new platforms, games on obscure platforms, just keep doing it and you’ll end up with such a wide range of skills you’ll be able to walk into any studio. Don’t stick to one genre, engine, tool, or discipline, try it all out.
Tanglewood released on the 14th of August, and you can see my thoughts here.
Source: Review Copy Price: £5.79 Where To Get It: Steam
Adventure games have quite the history, and it’s one with a lot of branches, and, interestingly enough, more than a couple of roots. For example, while it’s commonly accepted that CAVE, which was eventually renamed Colossal Cave Adventure, was the progenitor of Interactive Fiction (Due to the fact that anything earlier has been lost to time, it’s intriguing to note the history, as adventure games with graphics cropped up as early as 1980 (With Sierra’s Mystery House), and games with a point and click cursor (Controlled by the keyboard) came around 1983, with Project Mephius for the FM-7, a computer that released only in Japan. Indeed, part of the reason the timeline of game design is so messy is that European, American, and Japanese markets had their own home grown items that none of the others saw (Until later.)
Okay, so I’ve uncovered this… But how the heck do I open this door to the left? HRM.
Why all this preamble? To establish two things. That the adventures comprising this remake anthology are not, strictly speaking, firsts in the genre. Influential games, yes, but not firsts. But also that it’s fascinating to see changes and shifts, not just on the purely international level, but within individual nations. We’ll be briefly coming back to this, but first, the games!
The three games that comprise this trilogy were originally created in the mid 80s (1985-87) for the then humble Apple Macintosh, and, as such, were known as the MacVentures: Deja Vu, a noirish tale about an amnesiac detective down on his luck; Uninvited, a haunted house tale with the main character searching for their younger brother; and Shadowgate, a fantasy yarn that, despite the comparatively higher difficulty of the former two games, has a reputation for its gotchas and deathtraps. They had a graphic user interface, a selectable parser, and an icon based inventory, all of which were not, strictly speaking, new… But they might as well have been to the European and American audiences.
They did pretty well, well enough that a company called KEMCO ported them, with permission, to the Nintendo Entertainment System in 1989 and 1990. These are the games remade and presented in this anthology, and this, also, is interesting because the UI was changed, a controller led pointer was introduced (as in Project Mephius, several years previously), and Nintendo, a family friendly company even then, asked for… Changes. Some of these changes, I’m sure people are very grateful about: As far as I’m aware, the ten minute timer for one of Deja Vu’s “Solve this or die” puzzles (finding a cure for your amnesia) was gone. Yes, ten real time minutes. The interface was made tighter due to platform limitations, pentagrams were replaced by stars, and crosses by chalices, and, in an odd decision, it’s not the younger brother you save in Uninvited, but an elder sister.
Yep. That is indeed a greenscreen terminal filter. Yessirree.
In any case, that’s where we are today: Reviewing a port of a port of a trio of adventure games from the 80s. How do they hold up? Not that bad, actually! The Nintendo versions were not only notable for their changes, but a solid soundtrack that still holds up to this day, distinctive spritework, and an interface that, thanks to the fact we’re using a mouse rather than the NES controller, is highly accessible and a delight to use. Each could be played through over the course of an afternoon, perhaps less if you follow the ancient adventure game maxim of “Save Early, Save Often” , and only a few of the puzzles don’t have some signposting to their solution (There’s no clue, for example, that a certain ghost is afraid of spiders, sadly.) Be warned, however, that garbage items with no actual use in game abound. Old adventure games loved to do that, partly for realism’s sake (Yes, even then), but also partly to obscure solutions.
Being able to keep saves, and switch between them with relative ease? Oh yes, this is good. Having… Old monitor filters? Well, I guess it’s there? (Not gonna lie, if I wanted more eye strain, I’d just dig out my old BBC Micro and its CRT monitor. But they are nice filters.) And the writing of the games, for the most part, holds up. Deja Vu, being both a game of the 80s, and being inspired by the pulps, is perhaps the one that has aged most poorly, but there’s still some solid design there.
Also, the achievements. Ah ha ha yes, the achievements! It somewhat tickles me that the achievements for this trilogy all have to do with something you would either, unaware of this game from its heyday, stumble into, or, if you’re like me, a person amused by the death states of old videogames, actively seek them out: The deaths. Wait, you mean that lady wasn’t friendly? Gosh! And my shield could only take a few puffs of molten, superheated death spewing from a dragon’s mouth? Golly!
Well, we know we’re a dude. This much, we can be sure of.
As pieces of relatively faithfully preserved games history, this isn’t bad at all, although the “Volume 1” confuses me a little. After all, there were four MacVentures in total, so… Where would you go from here, General Arcade and Abstraction? Although it must be said, this trilogy did seem to inspire a wave of graphical adventure innovation in the West, from the Legend Entertainment games, to the Magnetic Scrolls series, each of which contributed, somewhat, to the eventual rise of the point-and-clicks we know and love today.
So yes, give these a go if you feel like experiencing some relatively solid 80s game design, and perhaps it might inspire you to check out other bits of adventure game history (Or, indeed, some of the other ports existing out there.)
The Mad Welshman enjoys older adventure games. Things tend to happen when he BITE LIP, however. Terrible things.
Source: Cashmoneys Price: £3.99 Where To Get It: Steam
I could write a single paragraph, and sum up Morphblade’s mechanics and concept. That’s how simple it is. I could sum up how I feel about it in a single sentence, if not the single word “Pleased.” That’s how uncomplicated it is to review. I could write a tiny essay on the tactical complexity the game’s simple rules and simple and easy to identify enemies provides, further fuel for my platform of “All games are made of simple rules, it’s what you do with them that counts.”
All games of Morphblade start something like this. There is, at first, one move.
I am going to do one of those things. Okay, maybe two. But first, I’m going to say it’s a short game where the pleasure is in playing. Unless you’re good, a single game will last all of two to five minutes. And then it will ask you whether you want to play again.
Instead, I’m going to use 264 words (counting this sentence), to ramble briefly about niches, and how “Short” and “Simple” are not dirty words. People seem to have this weird idea in their heads that if they have a short and simple game, they’re going to play it, get bored, and oh gosh, they’ve wasted… What’s currently the equivalent of two, maybe three bottles of Dr. Pepper. Oh no.
See, here’s the thing about short and simple games… Sometimes, you don’t want a long game. Even the people who say they want long games will find themselves, at 5AM (Coincidentally, it is 05:16), unwilling to touch their Torments, or their Age of Wonders. They’ll find themselves not wanting to stress out over their Overwatch rankings, or their Bulletstorm combos, or the inner complexities of a Hearthstone or whatnot. They’ll want something where they know what they’re in for…
As you can plainly see, tiles and enemies have their function explained, and it’s easy to remember (Not pictured: With right click)
…And Morphblade will be waiting for them. Silently, it will be reminding them that all its rules are explained… As you play. That all its symbols are open to it. That it won’t need you to quit in the middle of a game, because the end is always just around the corner. Just a couple of false moves (Rarely one. Usually two. At worst, three), and it’s all over. And it is definitely your fault, but it isn’t a problem. It doesn’t judge. In fact, it wants you to play it, and you can tell because it’s highly accessible, with an easily deciphered and colourblindness friendly palette, simple, easily deciphered shapes. It fits its niche excellently.
I bet a friend a tenner I couldn’t write more than 500 words about Morphblade, but not only am I going to win this bet, I’m going to finish the review by showing you some simple steps as to how to see for yourself how simple, deadly simple, the game is.
First, you look at the top of this review. There’s that price, less than £4. There’s also a Steam Store page link. Go click that. A video will autoplay (Or, if you have autoplay off, you can click play), and Tom Francis of Suspicious Developements will spend less than 3 minutes demonstrating the game (The length, funnily enough, of a normal game)
I can take one hit, so both of these enemy bugs are effectively dead. If one of them had been armoured, I could have run away. PLANNING.
I’ve now won a tenner, and am 6 quid up on my purchase. Which I can then use to buy Morphblade for a friend. Because I’m almost certain, based on play, the game, and Mr. Francis’ explanation of the game, that they will at least like it enough to come back to it.
It won’t mind. How can it, it’s a video game. Video games don’t judge. Only people do. I judged “Yea” on this one. You might too.
…Oh yeah, and a bottle of Dr. Pepper. Truly, I’m blessed.
Inevitably, you die. The only thing the game doesn’t *tell* you is that the turn counter is also the menu button.” Which is a tiny niggle, honestly.
The Mad Welshman smiled. Wave 19 isn’t so bad. We’ll see if we can top 20 later on. Or… Maybe now. Yeah, nothing urgent going on.
Goodness me, that rhymed. Lovely. Well, anyway, once again, it’s time to set the Wayback Machine, and the interesting game for this outing to the groggy times of yore is Dungeon Hack, the only official, licensed Dungeons and Dragons roguelike. Which is highly amusing when you consider how much early roguelikes (And even some modern ones) have been influenced by 2nd Edition DnD.
Dungeon Hack, released just after another title I’ve briefly dealt with, Dark Sun: Shattered Lands, uses an interface very similar to the Eye of the Beholder games. Similar enough, in fact, that I’m halfway convinced it’s the same engine, despite being developed by Dreamforge (Who, like SSI, created strategy and roleplaying titles, and did not survive 2001.) Nonetheless, it’s not the engine, so much as the visual style that impresses. There are several different level themes, all of them have a variety of different locks, tapestries, paintings, and gewgaws, and, if it weren’t for the rest of it, I would say that every run is a refreshing and different experience.
One of something like… An absolutely *silly* number of potential locks.
Unfortunately, I’m not saying that. Every run is, in fact, a tedious nightmare that often ends on dungeon level 2, due to the mechanical aspects of the design. Procedural generation has come a long way since the days of rogue, ADOM, and the like, and Dungeon Hack shows one of the weaknesses of early experiments… It’s predictable, and the difficulty curve is not so much a slope as one of the cyclopean steps of Great Cthulhu’s abode. As is often the case with roguelikes, there is a single, playable character.
But many of the monsters in AD&D are, in fact, balanced around groups taking them on. A perfect example of this is the main monstrous feature of the second dungeon level: The humble Ghoul. The Ghoul is normally a cowardly eater of the dead, picking on things it thinks it can eat, and making corpses when… Well, the corpses it normally feeds on are scarce. To aid it, it has a paralytic venom in its claws and fangs. Now, to be perfectly fair to the developers of Dungeon Hack, unlike in Eye of the Beholder, when your character is paralysed, they can still move (but not attack or use items), whereas if a mass paralyse from a Beholder hit in EoB 1’s later levels, you were pretty much dead.
The problem arises, then, from the fact that it’s corridors… And rooms. And corridors predominate. Corridors in which the other monster type that always inhabits the second level, the Troglodyte (in 2E, a stronger, but less intelligent relative of the lizardman) are very likely to ambush someone who hasn’t cleared the way behind them, and, even then, may get surprised by a respawn. As a Mage, you may just about have fireball at this point (Requiring a rest after every cast to regain it… We’ll come back to resting), as a warrior, you don’t really have any recourse except that old first person RPG technique of the sideways shuffle (Exploiting the AI in… Er… A room… To, er…Well, crap, that sort of invalidates it in a large set of situations, doesn’t it?), and it’s only as a Priest that you get… Turn Undead. Which, on the one hand, you have an infinite supply of. On the other, it’s not guaranteed to work, and you’re not guaranteed to hit on the attack that will break the Ghoul out of its “OhGodsAHolySymbolRunRunRun” mode Turn Undead tends to put it in.
Ghouls. There are many words I have to say about a lone adventurer fighting even small groups of ghouls. The vast majority of it is unprintable, even here.
So yeah, the difficulty’s a little sharp. Adding to this tedium is the predictability of monsters. Yes, you will always encounter Ghouls and Troglodytes on level 2. Just as you will always encounter Goblins and Orcs on level 1, with only the occasional Out of Depth monster to liven things up… Usually in a rather fatal manner.
And then, there are the keys. I mentioned before that there are a variety of different locks, and hoo boy, does the game use as many as it can. Each locked door has a specific key type. I’ve never encountered a situation where the key was behind a door, but each level becomes a case of three things: A sweep and clear, not unlike those annoying missions in Hero Quest and Space Crusade (Remember those?) where the victory condition was “Kill everything”; A hunt for various keys (Ice keys, flower keys, gold keys, chrome keys, platinum keys, bone keys, missing bull horns… The list is quite large); And, another staple of first person games and DnD RPGs of the time, either being a Dwarf, able to sense secret doors, or looking at the map, noticing large empty spaces, and wondering which of the walls you’re going to try and walk into will, in fact, turn out to be illusory.
Fun! It’s interesting to look at a game like this, because it has a lavish (if overacted) introductory cutscene (Involving the sorceress/demigod/secret deity… I forget which… Who sends you on the quest, and Sir Not Appearing In This Game, possibly the biggest, dumbest adventurer I’ve seen since Lands of Lore’s Conrad “The Scones Are Still Intact” McAdventurerson), a lot of thought put into a lot of locks and tapestries and statuary and fun things that mostly don’t have any bearing beyond looking pretty (Which I approve of), and yet… Once you get past that, there’s almost no balance, a steep difficulty spike on the 2nd level, and even less context than Angband or Nethack, relative contemporaries (1990 and 1987-2015.)
…I smell a cutscene, VO so fine!
Would I recommend playing it for enjoyment? Oh, Mystra, no! Would I, however, encourage budding developers to look at it critically? If you’re into procgen, licensed RPGs, and step/tile-based first person RPGs, yes. Because it is, to me, interesting to examine. Even if the examination can be… Rather painful.