Introduction

Q3map2build shot

Description:
What is Q3map2Build? This program is a slim, self-sufficient application front end for compiling maps. It was built by DLB (www.bobdev.com) back in September of 2002.

History:
There was a front end for q3map.exe called q3build which was later upgraded to GTKbuild, but from there the production of that particular app stopped. There were some others out there, but they would never be updated when new switches were introduced. Spurred by my constant complaints of cluttering up my GTK directory with dozens of batch files to handle the latest compile options as Ydnar (www.shaderlab.com) was working with q3map2, the nextgen compiler, I asked DLB for a solution and here it is. DLB wrote this app in about a day and mimicked the interface from the original q3build, which has the cleanest interface I have ever seen in any front end for anything.

Since I was working with multiple mods in helping get their shit together, was working with coders to ferret out bugs, and easing the seasoned mappers into q3map2's possibilities... this tool became a godsend for me. It's like the Swiss-army knife of front ends; without it I think my personal productivity would've suffered (or my organizational skills for keeping track of shortcuts and batch files would've been stressed).

Benefits:

• Doesn't touch the registry
• Doesn't install vb components that could break an OS
• Doesn't have any requirements other then runtimes
• Extensible framework
• It uses hardly any memory
• It fits on a floppy (I think 50 copies will)
• It lets you start up your mod/map with command line options
• It's clean
• It's small
• It logs as well as displays interactive output from the compiler
• Accepts any game that q3map2 does

Some other side benefits of this application are:

• Automatically scans all mod directories for maps
• Fully customizable if you want to mess around with it
• Great for startup options when testing or debugging
• Tool Tips for reminders of what switch does what
• I packed it with tons of options for compiling a bsp if you are a hardcore developer or want to play with all the settings.

I started sharing the application with the other level designers of WFA  (www.weaponsfactoryarena.com), then True Combat (www.truecombat.com) after I was using it and testing it. After a while. this application was widely being used by coders who could care less about most options and just want to test what they are working on, new mappers, and level designers who love to play with new toys.

The Low-Down:
As far as memory, most people never think about the excess utilization with Radiant open during a compile, it chews away from valuable cpu cycles that could otherwise be used for compiling. True is that most of the time this doesn't matter, but if you don't have a gig of ram (or you do have a gig and the compile is taking up 1.2 gigs of it) this could affect you. Q3map2build is slimware and uses minimal resources, and for me is easier to use and configure then the built-in options for Radiant or any other front end applications.

 
Q3map2Build, 5th column is physical, 6th is virtual.

GTK Radiant, 5th column is physical, 6th is virtual.

It's pretty much a no-brainer here. Ok so what does it do?