Editing Build (game engine) (section)

=== Early days ===
Version 2.0 of '''EDuke''', a project to improve ''Duke Nukem 3D'' for [[modding|modders]] by Matt Saettler (Matteus), was sent to 3D Realms for packaging shortly after the release of the Build source, leaving Duke Nukem 3D the pre-built libraries that 3D Realms had used with the original Duke. (Both ''Duke Nukem 3D'' and ''EDuke'' were still closed-source at this point.)

With the 2.1 private [[Software release life cycle|betas]], Saettler worked towards integrating Silverman's build source into the Duke source code, but the project fizzled out before producing anything more than some very buggy private betas. A few total conversion teams for Build games decided to work from Silverman's Build code directly, and an enhanced version of the Build editor known as Mapster was also developed.

It was claimed at the time by many on the 3D Realms forums that it would be impossible to port Build to a multitasking operating system, as it needed a large contiguous block of memory that wouldn't be available in a multitasking environment. This statement did not hold up to scrutiny, as all modern operating systems use [[virtual memory]] which allows apps to get contiguous logical memory without using contiguous physical memory, but conventional wisdom of the time was that porting Build to such an OS was unfeasible.