Tools related to EDuke32. Mapster32 (a BUILD Editor replacement) is included with the EDuke32 download.

Many more tools in other sections of this site still work with EDuke32, so please check them.

Some of these tools below will still work with Duke3D and other BUILD Games.

A simple program I created that use the provided palette.png file to create a new duke3d palette. The image file is just a series of white squares that you fill with the colors you want, arranged in order of the duke3d palette so you can make sure the colors are in the correct positions for shading and such. Use any paint program to customize the palette.png, rename it, and use the program to convert the palette.

PalMake creates a palette from a png file.
PalShift lets you modify the Palette.dat file used in build games/duke3d.

What it's not going to do:
Cast shadow as new sectors, create shading from scratch, correct shading based on the overall texture brightness.

What it does:
Reset the lighting of a map, adjust walls and sectors lighting based on a specified reference (floor or ceiling, brightest or darkest, average value), adjust walls brightness using "bulb sprites". More in the readme, it's nothing fancy and there's probably another piece of software doing that very thing somewhere else...

Not sure how the bulbs work though.

Pick a sprite you never actually use in your map (I picked 1220 in the example maps). Place the sprite somewhere in your map, and set its hitag to the light radius (every wall within that range will receive light). Since the program doesn't create extra vertices, you need to break the wall yourself. Use the "-bulb [tile number]" parameter so it knows what sprite should emit light. There's no occlusion (light goes through walls), but only wall facing the sprite and within range are affected anyway. It's not the best way to do it (ideally I should rely on vertices instead of surfaces and the surface's angle to determine the light level -- currently, only the distance is considered). Bulbs do NOT affect flats (floor/ceiling).

This program only exists because I wanted to know what was exactly contained within .map files (because of the "out-of-sector pivot" door glitch I tried to explain)