Welcome to the basics. This section is for those of you who have never made maps for Duke Nukem 3D before. Keep in mind that I've been using this program for years, and a lot of the keypresses are just instinct to me. I'll do my best, but I may accidentally forget to mention some keys here and there. E-mail me if you notice something missing. You may want to print these pages for reference while doing this activity.
Prelude
Well, if you're reading this, it must mean you're interested in learning how to build levels (henceforth referred to as "maps") for Duke Nukem 3D. When you first approach this task, it may seem overwhelming. But, over time you will realize that this is mostly a matter of absorbing a list of keypresses and their respective functions. The remainder of the work relies on your creativity and dedication.
I first learned how to build maps through two methods: FAQs and experiments. The FAQs were text-only, and with many effects it was hard to understand what the author was trying to explain (sliding doors come to mind). I remember the prehistoric method of drawing out an example using a mess of symbols. What great fun that was to pull apart. Anyway, a long while afterward I (excitedly) discovered some tutorials with images, only to realize they were missing loads of effects, which left me disappointed. It seemed as though nobody was interested in making a comprehensive guide to the program. Finally, after a couple of years, I started to document mapping techniques myself using HTML. This guide served as my own personal quick reference. It's grown enormous since then, and I'm always expanding and perfecting it.
The original DOS incarnation of the game has been dead for quite some time. Currently, EDuke32 is the most utilised form of the original game (and for good reason). Installing EDuke32 is as simple as dropping your DUKE3D.GRP
file into a directory, then unzipping the contents of the latest snapshot of EDuke32 into it. There's really no need to elaborate on such a simple process. If you're having trouble, consult a Duke3D forum.
The original map editor that came with the game was entitled "Build", and it was run in a DOS environment. Although Build has long been superseded by Mapster32 (the companion program to EDuke32), to this day I continue to use images taken in Build's style. I stick to this format both for nostalgia's sake, and because Mapster32's aesthetics are constantly being modified. There are some major differences between Build and Mapster32. One of the most important inconsistencies of which newcomers ought to be aware is the colour notation. Some of the colours originally used in Build have been changed within Mapster32, and will probably continue to change. This accounts for any differences you may notice between the screenshots in my guide, and the editor you are running.
Every form of the Duke3D map editor outputs maps with the extension [.MAP
]. It is best practice to limit your map names to eight letters. This is somewhat enforced, because maps with longer file names are abbreviated, and figuring out which file is which gets pretty tedious. In a roundabout way, this is actually a plus; One of the more satisfying prospects of a map is coming up with a cool eight-letter name that succinctly summarizes the theme. Anyway, this prelude is extending into the ample range, so it's time to get going with these tutorials. Remember to test out all of the mentioned keys as you read
through them. You'll gain a much clearer understanding of what the keys do if you
put them to action, rather than just trying to memorize them.