SOL Contingency's Community modding/mapping! :D

Alright everyone, here are a few answers to some of the top questions getting asked by community members:

          

Before we opened the forum to the public, we only used it for development discussion (in the private subforum hidden to non team members) where we established a few guidelines for developers. Obviously fans who are not developers (just players) and want to make maps and other stuff for the game (when it's playable), so I'm putting together a few guidelines for that too. I'm starting off with these and this thread may grow once the game's development gets further along.
Short answer: NO. The core of the game (mostly technology-related) is not finished, thus the game is only playable in a form that we would not hand out to anyone except team members, not even beta testers (and those would be the first to start mapping/modding, I believe). The game will eventually reach a state where we will have testing phases and select people will be able to play and map for it, but not yet.
The same tools we use to make the game: UDK and its editor to create BSP (which forms the basis for a map) and, if you want to make meshes for your maps, a 3D creation package such as Blender, Maya or 3DS MAX, plus a few converters. So yes, you can create levels for the game without spending money on software (using Blender or other 3D app for meshing, and the free UDK tools for mapping).
~ Minimum requirements for the UDK

• Windows XP SP3 (32-bit only), Windows Vista, or Windows 7
• 2.0+ GHz processor
• 2 GB system RAM / Can use less - but slower
  
• SM3-compatible video card / needed to install UDK
  
• 3 GB free hard drive space

You will need:

a.) A computer capable of handling the tools.
b.) Quite a bit of patience and knowledge to make a good map.

If you know how maps are made for modern games, you will know the answer to this - while it depends on your scope of detail, in general it's a much more involved process compared to the mapping we did in the 90s on engines such as id-tech 2 (Quake) and of course the original Descent. In Descent you used a form of cubic subtractive BSP to make maps, and they were pretty much error-free. In Unreal it starts with BSP, but creating clean and efficient BSP is very important to begin with and not as easy as it sounds. Then, to make a map look state-of-the-art, you won't get around many more things such as meshing, decorating with meshes, lighting, using particle effects, scripting with Kismet etc.
Yes, you can make a map purely from BSP and texture it, put some lights in and leave it at that. Just don't expect it to look any different from Descent 1.
Continuing from my above explanation, if you want to map for the game as a developer, you will really need to know your stuff with UDK. Even if you just want to make BSP layouts (which is perfectly reasonable) you should have the knowledge and skill to make clean and fast BSP that is scaled correctly and can easily be worked with when someone else takes it over for meshing. If you want to decorate your own map with meshes or even create those meshes yourself, keep in mind this is a time-consuming process that not every old-school mapper can get to grips with. I'm speaking from experience here; I love mapping in the old style but have a lot of problems differentiating between what BSP is used for these days and where to stop and start modeling meshes (which I find tedious).

We will only accept applications from level designers who have experience with modern mapping, not necessarily in Unreal although that is preferred. If you just want to get your head around modern mapping with UDK, you should stick with it and learn the craft before applying. Applications with no reference work (i.e. levels you built in a modern engine) will be turned down.
Since the game is currently an unlicensed non-commercial project, the source code will be partially open to people interested in programming, and you will probably be able to mod the game with add-ons using UnrealScript. Then of course you can also use the pretty powerful Kismet scripting system to make additions in your maps. You could also use Scaleform to change the menu system and interface. It will also be pretty simple to swap models or add additional ships, for example - some of these things will probably be supported in a limited fashion by the team because we will use workflows that make it easy for us to put such content into the game in the first place. It is also my goal to keep documenting important parts of development (like the 6DOF scripting doc) so everyone can benefit and in turn make good mods and maps.

With community members being so interested in making their own maps and engaging in the game beyond playing, I'm seriously considering an option that would make the multiplayer component of the game more open than the single-player game. This would entail an easy system to allow hobbyist mappers to make and add maps to a repository that every player could access, effectively letting the community generate most of the multiplayer content themselves. This would be in line with what Descent was: a collection of user-made levels that were distributed through official channels (such as Interplay's website and Levels of the World) and played a lot more than the handful of official MP maps. It would also give us developers more time to focus on the single-player campaign while the game could exist in the public as a growing multiplayer 6DOF shooter which gets its fresh content from users and not just the developers. 

We will see if this is possible -
  from a technical and legal standpoint.

 Quoted from: Max aka MadMax1998 @ forum.preparefordescent.com