> jackphla.sh – Page 9 – Retro Computing/BBS Scene Nostalgia Blog

Getting into Amiga – Choices

Introductions out of the way, this whole adventure started in earnest when I saw a post of a local retro computer Facebook group. One of the members was parting with his upgraded Amiga 1200. It looked to be in great condition and included most of the standard upgrades, such as a CompactFlash card-based hard drive, a Gotek floppy drive emulator, and an Indivision scan doubler. The price seemed pretty reasonable, all things considered, and an upgraded A1200 is pretty much the ultimate Amiga in my mind, so I was very tempted. Unfortunately, someone else had been quicker on the draw and already called dibs on the purchase. I watched the comments on the post for a week hoping the original poster would announce that it was still available but alas, no such luck.

This got me thinking more and more about finally getting an Amiga of my own to play with, which led to multiple deep dives into Amiga forums and groups. Thanks to my interest in retro computing I already had some familiarity with the awesome things people had been doing in the Amiga scene for the last decade or more – insane modifications like the Vampire series of FPGA based accelerators, for instance. Of course, there were also numerous other emulation options as well. The more I looked, the more options it seemed I had to choose from.

First and most obvious, acquiring an actual Amiga. There seemed to me to be a disconcerting number of challenges involved in collecting real vintage Amiga hardware, including the limitations of the stock hardware from the era, like having to rely on floppy disks, the seemingly bottomless money-pits that are collecting and aftermarket modification, the availability of this stuff here in the US where Amigas are far less common, worrying about exploding capacitors, smoking power supplies, and other issues related to the relatively ancient age of the hardware, the physical space being at odds with my recent efforts to downsize into my modest apartment, NTSC vs PAL issues, and a host of other video output concerns – I certainly didn’t want to have to track down a compatible CRT monitor, and much, much more. All in all, I decided to take getting a real Amiga off of the table.

The next option was hardware emulation. I haven’t ever messed with any of the newer FPGA based computers, though I attended a retro computer festival in my city last year and the MIST FPGAs as well as the newer MISTer FPGAs were fixtures in just about every booth at the convention, emulating various obscure machines to what seemed like a high degree of speed and accuracy. In fact, I attended a talk by Joe Decuir, one of the original Amiga hardware engineers, and he even shouted out the MIST Amiga core during his presentation. I’d heard a bit about them in the past, but I don’t think I ever realized how awesome they were until I saw them being used there.

Using a dedicated FPGA has numerous benefits over real hardware – a relatively tiny form factor, USB input compatibility and scaled VGA output meaning I can use my existing peripherals, swappable SD card based hard disks, “cores” that can emulate not only both older OCS/ECS and newer AGA Amigas, but also innumerable other platforms including the Amiga’s Commodore forebearers as well as its most compared rival, the Atari ST. You can also max out the virtual hardware on any of these platforms, emulating a stock Amiga 1000 running the oldest ROMs and OSes, or a super tricked out Amiga 4000 running newer, post Commodore ROMs and OSes. All in all, aside from being quite far from the experience of using real hardware, the quality of the emulation of the Amiga cores is the biggest concern.

Finally, we have software emulation. WinUAE and its counterparts are all quite mature, which means that not only is emulation and the added modern utility excellent, but there’s also a huge user community out there for support. You also have all of the flexibility in emulation provided by the aforementioned FPGA options, and more. The usability of these platforms is, indeed, incredible. Of course, running a soft emulator on top of a modern OS, on totally modern hardware is without a doubt the most removed from the experience of using a real Amiga.

One middle ground that has gained a lot of popularity lately is building a dedicated Raspberry Pi based Amiga emulator. There’s an excellent UAE based Amiga emulator for ARM called Amiberry which, despite its popularity as a game emulator, can be used for emulating the entire environment. Indeed, there is even an entire distribution dedicated to the cause, Amibian. While you don’t get the other cores or the performance of using an FPGA (or even emulation on a modern, higher end PC) you do get a nice, unobtrusive, dedicated piece of hardware beautifully aping an Amiga.

At the end of the day I decided to go the FPGA route. While the newer MISTer might be a better long term choice with its superior hardware and more active development community, the original MIST’s lower cost of entry, simple operation, and native VGA output won me over, at least for getting my toes wet into the world of FPGAs. I also bought a copy of the latest Amiga Forever, since it seems like a little bit of software emulation can be helpful in supporting any of the above efforts, and, controversy aside, there’s nothing wrong with having “legal” copies of the various Amiga ROMs and Workbench versions it comes with. I’m also still intrigued by the idea of building a dedicated Amibian-based Pi. Given its tiny cost of entry, I think it’d be a fun little project to document here.

So, with that, the journey is off to a start!

—
1. Joe Decuir is the man. Involved in the Atari 2600, Atari 8 bit PCs, and the Amiga chipset, but also newer technologies like USB and Bluetooth.
2. A stock screenshot of Amiga Forever being used in a totally unrealistic way. Yay!

Getting into Amiga – Introduction

Let’s start this story, well, at the very start…

The earliest experience I can recall relating to a personal computer was looking over the shoulder of a childhood friend whose dad had an elaborate Commodore 64 setup, complete with multiple disk drives, a dot matrix printer, and hordes of floppy disks. Shortly thereafter, possibly talked into it by the same parent (though maybe just a case of trying to “keep up with the Joneses”) my dad brought us home a Commodore VIC-20. We eventually bolstered the old VIC with a tape drive, a dedicated monochrome monitor, and several game cartridges and tapes. While not nearly as nice of a machine as my friend’s C64, that didn’t keep my brother and I from sinking countless hours into playing cartridge games, exploring all of the demos and games we had on tape, and attempting to type in some of the BASIC programs included with the VIC-20’s rather nice user manual (which definitely a challenge as a 5 or 6 year old.)

Even after we got a shiny new Nintendo Entertainment System (well after most of my friends had acquired one) I still occasionally dusted off the VIC-20 to aimlessly mess around with it. There was just something… different about a computer that a video game console simply couldn’t approach. Even today it’s hard for me to fully describe, but between the seemingly “deeper” gameplay of computer games, to being confronted with a BASIC prompt the moment you turned so many of those old 8-bit machines on, it seemed like the possibilities were limitless, and my imagination had been effectively seized as a result. This was also still in the era of the arcade, and movies like WarGames and TRON, mind you. Unfortunately my VIC-20 stopped working after awhile, but that only served to help my fascination grow into an obsession.

A recurring theme when I talk about my history with computing, the years following the death of my VIC-20 were filled with attempting to get as much time with and exposure to these ever so exotic video game consoles and personal computers as I possibly could. I’d buy random magazines, read books, and watch any movie that had anything to do with computers and video games. I’d play with the relatively out-of-date Apple IIs, 286 PC clones, and the Apple IIGSes in my school computer labs. If I visited a friend whose parents had a computer or video game console, you’d better bet I’d try to convince them to spend some quality time with me on it. Similarly, I used to sneak time on a family friend’s old Sega Master System. Later the same friend, upon finding out about my love of computers and games, gave me a horde of his old Spectrum magazines which were as bewildering as they were fascinating. I’d go to the showrooms at department stores to drool over their demo PCs and I’d browse catalogs and build out my dream computer setups. With that, my fascination turned into a stubborn goal of obtaining a new computer. Aside from a family friend donating a (unfortunately, broken) Commodore Plus/4 to my cause, I’d have to wait quite a while.

When it comes to Amiga in particular, I recall two specific things that were highly influential to why I’m writing this today. First, a detail that is extremely important is that, despite being an American, I spent many of my more formative years living in the United Kingdom. In the late 80s and early 90s, Amiga, specifically the Amiga 500, was seemingly ubiquitous over there and apparently in many other countries in Europe. It was the machine you’d see when computers were given away to kids on television game shows, and I’d always be there, jealousy watching scenes of teary eyed kids holding massive Amiga boxes over their heads in celebration. A second, more specific memory, was that I ended up randomly buying this January 1990 issue of The One (for 16-bit Games) at the village newsstand, likely motivated exclusively by the pretty pictures inside. Pretty pictures they were indeed – little did I know it, but this magazine was largely devoted to the Amiga and was filled to the brim with articles and advertisements featuring the mind blowingly awesome 16-bit graphics of the machine, the likes of which I’d never seen before that. These graphics were on another level. Aesthetics aside, the games themselves were mostly nothing like what I’d seen in the pages of Nintendo Power or GamePro: I recall seeing ads and articles related to It Came from the Desert, Midwinter, and Space Ace to name just a few. Between all that, I determined that my next computer had to be an Amiga.

Sadly, we moved back to the United States before I ever secured one. While my obsession with computers continued undaunted, the Amiga, not anywhere in any of the local computer shops or department stores, quickly faded as a contender, and eventually, even an option. I bought this single issue of Amiga World before closing that chapter of the saga of my childhood computer obsession for good. Not long after, my parents finally succumbed to my years long campaign of harassment and bought me a reasonably close to top of the line IBM-compatible 486/SX. I only got deeper into all things personal computer from then on, though Amiga wouldn’t be much of a part of any of that outside of being a lingering childhood memory.

Not entirely though. Pretty much as soon as I acquired a modem I got heavily involved in the PC underground BBS scene which was very much adjacent to and influenced by the Amiga underground BBS, demo, and piracy scenes, and “old school” ASCII art (which is largely Amiga ASCII based) became one of my personal specialties. I also dabbled with tracking via PC programs like Impulse Tracker and enjoyed viewing the occasional PC demo, trying to wrap my head around how some of those effects might have been achieved. So, my appreciation for the Amiga never totally died even if it did take on a new and different light over the years.

This more or less brings us to the present day, and I’m going to finally, some 30 years, dig into the fascinating world of Amiga. I’m going to be using the “Amiga” tag almost exclusively to document every step of my journey to some degree. While a lot of the details may be fairly uninteresting to Amiga veterans, I hope some of what I discuss here will at least be interesting or perhaps even helpful to others interested in or already involved in going into similar journeys themselves. Stay tuned!

I may dive more into the above two magazines in later articles, but for now I’ve *somehow* figured out exactly which issues they were and linked to full scans of them I discovered on archive.org. Amazing!

—
1. My family and I in the mid 80s. Okay, actually, it’s taken from the cover of the VIC-20 user’s manual…
2. Amiga 500 Class of the 90s pack! In the UK Amigas were sometimes sold in awesome bundles like this one.
3. An example of an Ami/X style underground board, Hidden Power is running Sigma Express with a sweet ASCII by 2Fast.

A Look Back at Darkness

Early Inspiration

While first exploring the BBSes in my local scene in the mid 90s the “door games” that almost every BBS seemed to have were a big source of curiosity. Who had what games varied widely by what the host BBS software could support and, as always, the individual tastes of each SysOp. I quickly learned that most of the more interesting looking door games were unintuitive if not extremely esoteric. I remember bouncing hard off of strategy games like Trade Wars 2002 and Barren Realms Elite while also having strangely fond memories of my repeated attempts to survive the irradiated wastelands of Operation Overkill II. It wasn’t until I stumbled into Legend of the Red Dragon (LORD) by Robinson Technologies (RTSoft) that I finally found a door game that actually hooked me.

Drawn in by the relatively pleasing aesthetic and approachable action RPG gameplay, your first steps in LORD would be spent figuring out the extreme basics of the game and establishing a bit of a daily routine. Quickly thereafter you’d shift fully into your routine of gaining levels and trying to survive the competition while working to discover how some of the game’s more obscure systems functioned and chuckling at Seth Robinson’s quirky sense of humor along the way. On many BBSes game content would be further supplemented by the addition of IGMs, 3rd party addon “modules” which could hook into LORD’s data files. It’s some time after that point that the repetitious nature of the gameplay lead the fun to dry up for many. The game had the potential to be a very different experience, however. These days when discussing LORD I often observe a disconnect between people who missed out on playing in an active game full of rambunctious players versus those of us who have and got to appreciate LORD’s systems in a different light.

It’s my opinion that, as with many other multiplayer games, the best content was ultimately what the game’s systems enabled the players to create themselves. Owing to its earliest origins as more of a social platform than a game, LORD includes many such systems, designed to encourage players to interact in more ways than just trading positions on the leaderboard. Players could, for instance, chat on various walls and post announcements in the daily news, send private messages back and forth, fight for the affections of various NPCs and even each other, make arch enemies to avoid and/or hunt down, and establish secret alliances and cabals, pooling resources to dominate the competition. I recall at one point that my brother and I both had multiple accounts on one particular local BBS that had more or less been running on auto-pilot for years, the antics of the door game patrons going totally unpoliced. My brother, a grizzled veteran of pen and paper RPGs by this point, got really into the aspect of “role playing” numerous characters to use the relationships he’d build to strategically manipulate other players. There were friendships, romances, betrayals – all of the hallmarks of a great drama!

I became a bit of a LORD super-fan myself. I called Seth’s BBS, The Darkside, to register my own copy of the game and started collecting every IGM, utility, and other related file I could get my hands on (there were already a fairly vast amount of them by then.) I recall going through what has become a bit of a rite of passage for SysOps and BBS modders everywhere, trying to get every single IGM you could possibly make run added to the game to create a single uber-customized version of LORD. Of course, given the bugs and balance issues that even the best IGMs could introduce to the game, this also tended to be an uber-broken version of LORD. Taking that idea a step beyond, I once even setup a board called “The Fortress” that was 100% centered around LORD, totally custom themed to look like it, with multiple games of LORD running to cater to different tastes. Looking back, it was ridiculous to think anyone would be as into the idea as I was, but it was still a lot of fun to do.

The End of an Era

RTSoft released numerous updates to LORD in 1994 and 1995, each featuring a slew of content additions along with the expected new features and bug fixes. In 1996 RTSoft released the overhauled version 2.00 of their Trade Wars 2002-ish game, Planets: The Exploration of Space (TEOS). TEOS was never exceptionally popular from what I’ve seen but I still consider it a bit of a hidden gem. In 1997, after plenty of teasing, RTSoft finally released LORD 2: New World to a bit of a lukewarm reception. Some specific callbacks to the first game and Seth Robinson’s ever-present sense of humor aside, LORD 2 was an incredibly different experience. Featuring a huge, semi-persistent graphical world to explore, viewed from a top-down rogue-like perspective, it felt closer to early text based and graphical RPGs and action-adventure games than the original Legend of the Red Dragon. Still, it was definitely RTSoft’s most technically impressive game to date. Its release was surely too late though, as dial-up BBSes were well into the process of becoming almost totally extinct by 1997. Released years earlier, LORD 2 could have been an absolute mega hit, but as such its popularity seemed to be quite isolated. Regardless, people that loved LORD 2 seemed to REALLY love LORD 2, with a number of them taking advantage of the game’s REF scripting language to create their own quests or even totally new game worlds, and I feel like it was ultimately very influential to those of us still paying attention by then.

Seth himself had apparently seen the writing on the wall and was already moving on, releasing a single-player graphical action-RPG called Dink Smallwood the same year and selling the rights to all of RTSoft’s BBS door games to a company called Metropolis Gameport shortly thereafter. I don’t know much about the history of Gameport but the ensuing years certainly cemented their reputation among already typically anti-corporate BBSers as cynical opportunists, buying up the rights to popular shareware games and utilities, collecting registration fees for them, and then doing fuck all to support them. RTSoft released a token (mostly bug fix) v4.00 of LORD just before selling the game, but having not had a real update since v3.55 in late 1995, cobwebs had already started to form on LORD’s legacy, and Gameport was certainly making no effort to clear them away.

Hacking Away

Meanwhile, I’d been very slowly learning to program since getting into the modding scene and by 1997 had put out a number of small, mostly terrible doors. I started out using Enigma’s “edoor” library for Turbo Pascal which was nice and lightweight and had a bit of an underground scene style to it, thus appealing to me a lot more than some of the larger, more mainstream door libraries. For those unaware, such libraries (often called “door kits”) made the entire process of writing doors much simpler as they, at the very least, took care of all of the tricky communications stuff behind the scenes. Many went a step further by including some of the common underpinnings of door programs, such as SysOp-side functionality like a local status bar and the ever-important ability to hang up on annoying users. Armed with one of these, a programmer could focus on the actual functionality of their door. As an aside, it’s safe to say that without the existence of such door kits we wouldn’t have ended up with anything close to the huge number of LORD IGMs I mentioned earlier.

Anyway, my only real frustration with edoor was that its source code wasn’t available which meant certain aspects of it couldn’t really be customized. More crucially, the routines provided by the library couldn’t be modified either which could really hamstring a larger, more complex project. I’d imagine resulting from being annoyed by the very same limitations himself, my friend Natedogg released his own take on edoor which he called the “Xtreme Doorkit” (or simply “xdoor”) with Demonic Productions in 1997. Xdoor did just about everything edoor did while yes, including the full Pascal source code. As an added bonus I had full support from the developer himself if I ever needed it. Naturally xdoor instantly became my door library of choice.

Xtreme Doorkit (XDoor) v1.02 file_id.diz

By 1998, with xdoor in my possession and a slowly growing confidence in my programming ability, I felt ready to tackle something more ambitious than the small utilities and doors I’d been working on up till then. At the very least, I hoped working alone on a larger project from the ground up would force me to expand beyond my rudimentary knowledge of Pascal. Branching out to a door game seemed like a logical choice, especially having observed the disappointing situation with LORD and the relative lack of other new door games coming out to help take its place. The idea of writing a door game quickly morphed into a scheme to rewrite LORD. I don’t mean a similar style of game like Darkness would eventually become, but a literal, fully compatible duplicate of Legend of the Red Dragon. Not only did I not have any specific ideas of my own, I felt some odd sense of duty to keep LORD alive, somehow. I dove into the project with a kind of fiery indignation – I was going to save my favorite door game!

Starting with LORD 4.00’s data structures, the only pieces of LORD’s source code that had ever been publicly released (for the purpose of allowing IGM and addon developers to access LORD’s data files), I began working on manually reverse engineering the game from there. My efforts hadn’t got very far at all before rumors started circulating that Gameport had granted a fellow named Michael Preslar the rights to continue development of the old RTSoft games for them. While this was surely positive news, regardless of his ability as a programmer, it seemed unlikely to me that anyone could adequately fill Seth Robinson’s shoes. Besides, I had already decided that my door game was happening. Rather than cancel my plans entirely, my new game would simply be a LORD style game, not unlike New York 2008, Lunatix, and Jedi Knights to name a few. Ultimately, this would surely be easier than the increasingly daunting task of trying to duplicate LORD’s seemingly limitless number of idiosyncrasies, so I rolled up my sleeves and got to work. Darkness was born!

Shaping the Game

So where the hell did the name “Darkness” come from? Well, I don’t actually know. I can tell you where it didn’t come from, though. I’d never heard of the comic book series The Darkness, which came out just before I started work on my game, until a team of awesome ex-demoscene dudes named Starbreeze turned it into a popular video game franchise in the late 2000s. The British rock band The Darkness? They came along after I’d already started work on my game. White Wolf’s “World of Darkness” pen and paper roleplaying game setting, which I was familiar with, likely wasn’t any sort of inspiration. If anything, perhaps Agent Orange’s debut album “Living in Darkness” might have at least been responsible for why the word was bouncing around in my head at the time. Regardless of where the word came from, it was clearly edgy and cool enough to appeal to my 17 year old sensibilities, and that’s all that really mattered.

What about cyberpunk? Well, I don’t have a very definitive explanation for that either. Living up to nerd stereotypes, I was a longtime fan of science fiction, computers, and anime, and I’d been vaguely fascinated by the crossroads where these things all met, the genre of cyberpunk, since first being introduced to it by pen and paper roleplaying games like FASA’s Shadowrun and R. Talsorian’s Cyberpunk 2020. I’d been playing Shadowrun with some high school friends here and there, and the mid to late 1990s saw several notable cyberpunk-ish movies and shows such as Johnny Mnemonic and the original Ghost in the Shell film. The genre definitely appealed to me. Still, I couldn’t really tell you why I decided on that theme for Darkness outside of the fact that I didn’t know of any other explicitly cyberpunk door games, and if my game was going to be a LORD clone, at least its setting could stand out from the array of medieval fantasy and hard sci-fi themed door games out there, right?

As for the game itself, this isn’t really evident from the betas that I eventually released, but from the early days I aspired for Darkness to be much more than a straight LORD clone. I’d start with LORD’s gameplay as a core, definitely, but I planned to build systems onto it from there. I wanted to incorporate flavor and gameplay features from some of the cooler LORD IGMs I’d played with as well as some other door games, with Tao Ge’s original versions of Exitilus being a game that had particularly intrigued me. Features such as an elaborate gang territory control and warfare system were planned from early on, for instance. I also wanted the world to be considerably more gritty and “adult” (that is, what passed as “adult” to an angsty teenager) in tone than LORD, and bringing some of the style and flare of the underground scene that I had become so entrenched in into the game’s aesthetics was a stated goal as well.

Development

Despite not having a clear idea of what I needed to do and practically no other existing door game source code to look at for examples, things actually went surprisingly quickly at first. Of course there were numerous challenges – I had a weak grasp on how to use binary data files, and I’d never coded any sort of ordered list in my life, for instance. Luckily with friends like xdoor’s author Natedogg and numerous others in my corner, it was never too hard to get to be pointed in the right direction when I found myself off in the weeds. Still, in the spirit of using the whole process for learning, I attempted to work in a vacuum as much as possible. I admit, it was also kind of a secondary goal of mine to surprise some of my friends with just how much my programming ability had grown. Indeed, looking back, it’s hard to imagine how I managed to come up with some of Darkness’s more complicated features like multinode functionality and IGM support completely on my own.

It’s worth pointing out that 1998 was probably the most tumultuous year of my life – I was finishing up my senior year of high school, girls finally started noticing me (somehow) and I had my first drama filled relationship as a result, and I started my first IT job, all of which combined into a chaotic strew of stress and exhaustion. The following years would add even more demands on me free time, as in addition to starting college and having heaps of homework, I’d become heavily involved in my local punk scene and started going out to shows as much as humanly possible. It’s kind of a miracle that Darkness ever even ended up in a state resembling being finished in the first place, honestly, and towards the end I definitely rushed through a lot of the remaining work just to get it out the door. For instance, the final encounter at the end of the game, which had been a huge focal point in LORD, was totally thrown together with relatively little care. At long last, I released my first private beta in January of 2000, followed up with a public beta, v1.00 wide beta 2, in late May.

Coincidentally, the BBS landscape had started to change by then. In 2000, Mystic BBS shifted focus from its DOS and OS/2 versions to its Win32 and Linux ports, and Synchronet reentered the picture in a big way with the impressive version 3.00. Together, along with the RemoteAccess inspired EleBBS, these packages finally introduced a free and effective method for SysOps running more modern operating systems to run otherwise old school BBSes via telnet. To go along with that, all of these packages included support for a brand new drop file format specifically designed to allow Win32 and Linux native doors to communicate with them, DOOR32.SYS. Oddly, in order to help spread their new standard, both BBS authors had taken to hacking DOOR32.SYS support into some existing open source door kits, with Rob from Synchronet tackling the well-known C++ door library OpenDoors, and James from Mystic, in addition to his own Virtual Pascal library called D32, releasing a modified version of Natedogg’s xdoor which added Win32 support (via Virtual Pascal) while maintaining backwards compatibility with the older DOS versions.

Working with James, it took little effort to port the game from Borland Pascal to Virtual Pascal and upgrade to this new 3.00 release of xdoor, making Darkness one of the very first door games to support DOOR32.SYS when v1.00 wide beta 3 was released in mid 2001. This may seem like a footnote in Darkness’s story, but I believe this is probably the main reason Darkness hasn’t completely faded into obscurity in the years since. It went from mostly being only of interest to my friends in the underground scene to being on a huge percentage of SysOps’ radars practically overnight.

Final Release

Darkness v1.00 beta 3 file_id.diz

In the end, Darkness was pretty well received. People were excited for a new LORD style game, sure, but the gritty cyberpunk theme, including the over the top sex and violence, as well as the dark humor and underground aesthetic, seemed to really go over with the people it was most aimed at, which is to say angsty-ass teenagers and young adults like me and my friends. Surprisingly, a small handful of IGMs and utilities got released for it as well, and I was (and still am) grateful for the show of support.

Bug reports and suggestions also came rolling in and I did my best to address them. As with beta 2, I went on to release several interim builds that were distributed as archives of simple drop-in file replacements. This was a regrettably sloppy release strategy that has lead to a lot of SysOps who still run v1.00 beta 3 to unwittingly use older, buggier builds, though in my defense these releases were really only meant as stop-gap fixes for beta sites in between larger releases. Unfortunately, the next larger release never came and the build released at the end of November 2001 was to be the very last one. Not at all coincidentally, I entered the post-college workforce full-time in December. Quickly finding myself sapped of the energy and focus required, work on most of my scene related projects ceased, and I let Darkness fall by the wayside before ever getting it out of beta, and in hindsight, at a time when it was perfectly poised to ride the momentum of the growing telnet BBS scene.

To be continued…

Here’s is a quick list of Darkness v1.00 related files:

DRK100B2.ZIP – Darkness v1.00 Beta 2 (2000) D050300.ZIP – Darkness v1.00 Beta 2 Update #1 (2000) D061300.ZIP – Darkness v1.00 Beta 2 Update #2 (2000) D071900.ZIP – Darkness v1.00 Beta 2 Update #3 (2000) DRK100B3.ZIP – Darkness v1.00 Beta 3 (2001) D080501.ZIP – Darkness v1.00 Beta 3 Update #1 (2001) D101201.ZIP – Darkness v1.00 Beta 3 Update #2 (2001) D112001.ZIP – Darkness v1.00 Beta 3 Update #3 (2001)

DAMF105B.ZIP – Dark Alley Medical Facility IGM (2001) DENED1B5.ZIP – Darkness Enemy Data Editor (2001) DRKIGM8BALL10.ZIP – Magic 8 Ball IGM (2015) DRKIGMLEMO10.ZIP – Lemonade Stand IGM (2015) DRKIGMPSC10.ZIP – Darkness Plastic Surgery IGM (2015) FWH100B.ZIP – Females-Only Whorehouse IGM (2001) SM-WILLY.ZIP – Slick Willy IGM (2000)

—
1. Legend of the Red Dragon INTRO1 by David Nicholson from LORD400A.ZIP (1997)
2. Legend of the Red Dragon 2 Screenshot from LORD2 v1.01A (1997)
3. Xdoor v1.02 FILE_ID.DIZ by Jack Phlash from XDOOR102.ZIP (1997)
4. Exitilus v2.05 AD1.ANS by Tao Ge from EXS205-1.ZIP (1995)
5. Darkness INTRO1.ANS by Cyberphreak from DRK100B3.ZIP (2001)
6. Darkness v1.00 Beta 3 FILE_ID.DIZ by Jack Phlash from DRK100B3.ZIP (2001)