Nexuiz Ninjaz - Practicing the Ninja Art of Nexuiz

Intro

This tutorial is for Windows and Linux users. I don't know how to make maps on Mac OSX. Perhaps someone can add notes to this How-to.

In this how-to, I will show you how to make your first map for Nexuiz using GtkRadiant 1.5 which you can Download here if you haven't already.

Run through the install, selecting the 'typical' method when prompted.

Note that this is an older tutorial, a lot of points are still quite valid but you may want to combine this information with the knowledge found in [urlhttp://www.nexuizninjaz.com/forum/forumdisplay.php?fid=35]Mapjutsu[/url]. Specifically
[How-to] Begin mapping like a ninja and [Useful] Mapping Resources/Places to Visit.

Getting Setup

Open GtkRadiant, select 'Nexuiz' and click 'okay'.



You will be prompted to find your Nexuiz directory. Do so and click 'okay'.

You will be greeted with a screen similiar to this:


We're going to make it a little easier to understand by making the log box smaller an the grid bigger.

Do this by click the dividers and dragging them to where you want.

Once you have your area setup...

Make Your Box

Drag your grid so that the camera is in the bottom left corner. Do this by holding right click. Then left click and draw a box on the grid.


To get a better look at what you're working with, right click the preview box. You mouse will now control the camera angel, your arrows will move you through the environment. To deselect, right click again.


Make sure your box is selected, the box on the grid should be red. If it's not, shift click the box. Then hit 'Hollow' on the toolbar.


Press ctrl+tab to change to the grid view and select the bottom plane by holding shift and clicking it. If you select the wrong one, you can deselect it by hitting 'esc'


Press 'alt+down' to move the plane down one unit.


Repeat this method for the top plane.


Hit 'ctrl+tab' until your screen looks something like this


Using the method you just learned, move the planes so the look like this.

Remember: 'Shift+click' to select, 'esc' to deselect and take advantage of the camera view to rotate your map when you can't click something easily.


Okay, so why the hell did I just make you do all that? You should not overlap brushes EVER. It will slow down your map amongst other things. It's best to learn the proper method first.

Caulk It

This step is probably done best before you even draw your first box but we can caulk right now as well. I'll teach you a little trick too.

Make sure everything is deselected ('esc') and hit 'i' (inverse). Select 'common' in your textures list and find the 'caulk' shader.



Lets Go Inside

Using the camera view, go into your room and find a spot you'd like to place your player start point. Right click that spot on your grid and select 'info->info_player_start'.


Now that we have a spawn point, lets give the player something to look at. Select the walls brush faces by 'ctrl+shift+clicking' the walls. We're only selecting these faces because we'll never see the other ones and that would be a waste.


Select one of the evil packs from the texture list and find something to texture your walls, do the same for the ceiling and floor.



Get it ready for play

Give yourself something to play with when you go to test it and save your map.


Once you're happy with your setup, compile the map


Create a map config file in your 'Nexuiz/data/maps' directory (possibly '~/.nexuiz/data' on Linux/Mac).
If your map was called 'ztopia' you would call the mapcfg file "ztopia.mapcfg".

Inside this file, we point to our compiled BSP, also known as ztopia. Add this line, replacing ztopia with your map name to your newly created mapcfg file and save it.

Play it!

Now that we're all set, open up Nexuiz and drop the console (Shift+esc) and type 'map <yourmapname>'. So I would type, 'map ztopia'.



Now that's a small map!


This should be enough to get your started... I'll add more to this later, including how to make your own map pack.


Introduction to the pk3

The best way to understand how map files work in Nexuiz, or any pk3 (pack file) for that matter is to see it as a 'clean' way of adding files or subdirectories to the infamous data directory. A pk3 is merely a renamed zip file.

For example, if you wanted to share a bunch of demos, you could make create a zip file with the following hierarchy:

You can drop that file in your data directory and it will load the demos. can't believe it's that easy? download the above example and try for yourself.

Custom pack files have priority over data20070531.pk3 (dataxxxxxxxx.pk3) and unpacked files have priority over both.

For example, if I were to have a pack containing sound\misc\talk.wav with a custom sound this pack here, it'll replace the sound\misc\talk.wav in dataxxxxxxxx.pk3. To trump this, create the folders sound\misc in the data directory with a talk.wav file.

Note: Currently pk3's only auto run in data directory. Most likely for security reasons.

The information beblow is outdated, check out this thread:
[How-to] Begin mapping like a ninja: Packaging your map

Creating a Map Pack

Maps only really require one folder, maps. However, you can add any others you may need, such as 'sound', 'textures', 'scripts', etc.

I will use zion_beta_3.pk3 as an example.

This is pretty much as basic as you can get. Unless you didn't use any custom textures.

Note: If your map contains textures from any of the 'evil' folders, you do not have to include them in your pack.

Wow. Thank you! This is *exactly* what I wanted/needed. I've been wanting to start doing this for so long but I did not want to jump into it blindly.

I'm installing on a 64-bit Gentoo machine here and I've run into a few specific problems. The gtk-radiant installer does some 32-bit specific code without checking the processor, and links against 32-bit binaries. The result on a 64-bit machine is that the needed libgtkglext and libgdkglext libraries are missing or incompatible. There are several solutions that I found from searching:

1) Use the subversion build. I read the installer is fixed and I'll be confirming this soon.
2) Fix the installer. The tremulous forum had a thread with a repaired installer.py but I didnt have that file in my package and I cant find the url now.
3) If you have a 32-bit chroot, or dont mind making one, you can copy the 32-bit versions of the libraries from your /usr/lib32/ to your /usr/lib64
4) You might try these libraries someone prepared, at you own risk: http://www.geekbin.net/main/2007/09/23/p...d64-users/

The next problem was that the ebuild for gtkradiant did not include Nexuiz. I followed http://www.alientrap.org/forum/viewtopic.php?t=2275 for a subversion howto. I also snagged this helpful tip from the ubuntu forums but applies to kde users: You'll want to remap/disable the Walk Through Desktop List default shortcut key of ctrl+tab so you can use it properly in Radiant.

Good starting tutorial. It was pretty clear and the resulting map worked for me.

Perhaps this could be merged with this other Nexuiz tutorial that tZork and C.Brutail started over a year ago.
http://zdev.dvrdns.org/radiant_tutorial/...tents.html

It was originally discussed here
http://alientrap.org/forum/viewtopic.php?t=906

ok this was a first attemt to make a map and i feel proud to have made it .
it's not much but it works and is playable , uh , as much as you can play in a 20x20 room .
cant wait for more details to make a real map .geez look at the fps in this small room. click the thumb to enlarge

Do you guys know how to make new textures for the maps ? And also are you guys looking for training maps built specifically for rocket/laser jumps , hook , speed ,etc.? i really enjoy building these things and will submit some maps to nexuiz when i learn GTKradiant more.

Create them with your image editing software of choice, then drop them in data\textures\[your map name].

The should be accessible per that name via the texture box in radiantGTK now.

We like maps of all kinds :).

After a long drawn out evening , I think i have a map for training . this map focuses on jumps with the rocketlauncher and the laser . This is just a basic level for froggin' around . I tried to keep in mind not to make things too hard so that the user can get used to moving around . I made rounds in in here and found that it is a continous practice . So i need to let the teachers have it for inspection and some final touches .here's the screenies


also need directions on uploading . Isaw how to in gtkradiant but those are for q3 and i dont want to mess up . And where to upload to . see you in training1 map.

I can't see bigger pics :(. Use http://pics.nexuizninjaz.com for image hosting.

What do you mean you need directions on uploading? How to make a pk3?

You can click on the thumbs for bigger veiw now , sry didnt check that earlier .
by directions i mean , what do i need to do from here on out to get the map to you guys for inspection. i have never done this before .

The information beblow is outdated, check out this thread:
[How-to] Begin mapping like a ninja: Packaging your map


Introduction to the pk3

The best way to understand how map files work in Nexuiz, or any pk3 (pack file) for that matter is to see it as a 'clean' way of adding files or subdirectories to the infamous data directory. A pk3 is merely a renamed zip file.

For example, if you wanted to share a bunch of demos, you could make create a zip file with the following hierarchy:

You can drop that file in your data directory and it will load the demos. can't believe it's that easy? download the above example and try for yourself.

Custom pack files have priority over data20070531.pk3 (dataxxxxxxxx.pk3) and unpacked files have priority over both.

For example, if I were to have a pack containing sound\misc\talk.wav with a custom sound this pack here, it'll replace the sound\misc\talk.wav in dataxxxxxxxx.pk3. To trump this, create the folders sound\misc in the data directory with a talk.wav file.

Note: Currently pk3's only auto run in data directory. Most likely for security reasons.

Creating a Map Pack

Maps only really require one folder, maps. However, you can add any others you may need, such as 'sound', 'textures', 'scripts', etc.

I will use zion_beta_3.pk3 as an example.

This is pretty much as basic as you can get. Unless you didn't use any custom textures.

Note: If your map contains textures from any of the 'evil' folders, you do not have to include them in your pack.