I'd like to try collaborating on a map.



Here is the layout of kenobi-ctf. The red base is the middle red dot on the bottom. The grey dots are where the map connects after duplicating and rotating.







These textures will changes, they provide convenient lighting. At this point nothing is set in stone.


to check out the map from linux or mac: git clone git://github.com/drhodes/nexuiz-map-kenobi-ctf.git
(^^ URL Fixed)
if someone with windows wants to try, that would be great too, just to see if it can work.

Pushing changes back to github requires an account on github.

I have no expectations about how this will work, or the quality of the results. Anyone who wants to participate, should - even if you've never mapped before.
I would be happy if we built a map that people enjoy while incorporating as many ideas from as many people as possible. There's no time frame.

the project can be found here: http://github.com/drhodes/nexuiz-map-kenobi-ctf

I figure if people want to chat on irc about it, #nexuiz.editing on quakenet would be a good place.

One thing to note, there are two map files, I've found that having two instances of radiant open allows for one instance be a junk yard for map parts: sections of hallways, corners to be reused without cluttering up the main map. It's possible to copy and paste between the two.

Code: Select all

tyler@quadjutsu:~/nn_dev/nexuiz/nexuiz_vanilla/rev_8451/data$ git clone git@github.com:drhodes/nexuiz-map-kenobi-ctf.gitInitialized empty Git repository in /home/tyler/nn_dev/nexuiz/nexuiz_vanilla/rev_8451/data/nexuiz-map-kenobi-ctf/.git/
ERROR: Permission to drhodes/nexuiz-map-kenobi-ctf denied to z.
fatal: The remote end hung up unexpectedly

I had to type in:

Code: Select all

git clone git://github.com/drhodes/nexuiz-map-kenobi-ctf.git

edit:

Also, I see you have some scripts to build the maps but they aren't very portable as they contain relatively hard-coded directories. Perhaps you should base them off a configuration file and give an example of how you setup your working environment.

Yeah I've thought about a config file, but it's just been easier this way. When I get around to making it really portable i.e. to work on windows too, I probably will make it a config. Right now it has some os calls to fire up zip, and it makes symbolic links which windows doesn't support.

Ok, added BUILD.txt

git://github.com/drhodes/nexuiz-map-kenobi-ctf.git

yep, thanks Z - copied the wrong url, they keep em right next to each other.

Interesting, i'm not a mapper but i'll sure check out the map. I don't particularly like git, though.

dublpaws wrote:Ok, added BUILD.txt

Okay, this is definitely a step in the right direction but your workspace needs to be tidied up.

You have everything in the root and backup or otherwise unnecessary files checked into git (.bak/.autosave/~).

I'd suggest thinking about a hierarchy that encourages portability and abstract reuse of tools. For example, having happy-pack be a separate tool that will package any map and have kenobi be a map that exercises the use of this tool. Then you can keep that tool separate and update it without updating every map repo.

For example

Code: Select all

my_working_directory
|-tools
|--cleaner
|--linker
|--packager
|--tester
|--my_config.conf*
|-maps
|--dublhelix
|--kenobi
|--trust


*maybe throw in a global conf (or even in the root)