Unvanquished - User contributions [en-gb]

Old/Mapping

2012-07-29T02:09:35Z

UniqPhoeniX:

==Overview==

TODO

==Guides & Tutorials==

[http://tremulous.net/forum/index.php?topic=14411.0 Useful mapping links thread on Tremulous forums]

[http://tremmapping.pbworks.com/w/page/22453200/Starting%20Tremulous%20Mapping Starting Tremulous Mapping]

[http://tremmapping.pbworks.com/w/page/22453205/Understanding%20Vis%20and%20Hint%20Brushes Understanding Vis and Hint Brushes]

[http://q3map2.everyonelookbusy.net/shader_manual/ Shader Manual]

==Basic Guidelines==

Player sizes, in quake units (qu)
{|class="wikitable"
|Dretch ||30^3
|-
|Granger ||40^3
|-
|Adv Granger ||40^3
|-
|Basilisk ||36^3
|-
|Adv Basilisk ||42^3
|-
|Marauder ||46×46×36
|-
|Adv Marauder ||50×50×40
|-
|Dragoon ||52×52×55
|-
|Adv Dragoon ||58×58×66
|-
|Tyrant ||64×64×92
|-
|Human ||30×30×56
|-
|Crouching ||30×30×40
|-
|Battlesuit ||30×30×72
|}

Players will need an opening at least 1qu wider to fit through (possibly 2). In addition, player bounding boxes do not rotate, which means diagonal corridors would need to be wider (thus the majority should be axis aligned

Map scale:
32qu = 1m

Doorways should be a minimum of 3x3m, preferably around 4x4m. Corridors should be a minimum of 5m wide, although it is ''possible'' to use a mix of 4-5m (see Niveus for an example), and at most 8m wide. Do not create corridors more than 40m long without plenty of cover.
Currently large open areas and underwater areas are very human biased.

Alien bases need cover to hide things behind, the entrances should be ~4x4m and should not be easily visible from outside other entrances.

==New Features==

You may be interested in the list of [[Engine features|engine features]].

* [[Navigation Meshes]]

==Where to place your map files==

The most convenient place across platforms is to place your .bsp files and any other assets in the <code>main/maps/</code> subfolder of the [[Running_the_game#Data_locations|data location]] appropriate to your system.

==Resources==

* [http://ingar.satgnu.net/gtkradiant/ Ingar's NetRadiant builds]
* [http://www.custommapmakers.org/wiki/index.php/Main_Page Custom Map Maker's Wiki]

Old/Mapping

2012-07-29T02:09:06Z

UniqPhoeniX:

==Overview==

TODO

==Guides & Tutorials==

[http://tremulous.net/forum/index.php?topic=14411.0 Useful mapping links thread on Tremulous forums]
[http://tremmapping.pbworks.com/w/page/22453200/Starting%20Tremulous%20Mapping Starting Tremulous Mapping]
[http://tremmapping.pbworks.com/w/page/22453205/Understanding%20Vis%20and%20Hint%20Brushes Understanding Vis and Hint Brushes]
[http://q3map2.everyonelookbusy.net/shader_manual/ Shader Manual]

==Basic Guidelines==

Player sizes, in quake units (qu)
{|class="wikitable"
|Dretch ||30^3
|-
|Granger ||40^3
|-
|Adv Granger ||40^3
|-
|Basilisk ||36^3
|-
|Adv Basilisk ||42^3
|-
|Marauder ||46×46×36
|-
|Adv Marauder ||50×50×40
|-
|Dragoon ||52×52×55
|-
|Adv Dragoon ||58×58×66
|-
|Tyrant ||64×64×92
|-
|Human ||30×30×56
|-
|Crouching ||30×30×40
|-
|Battlesuit ||30×30×72
|}

Players will need an opening at least 1qu wider to fit through (possibly 2). In addition, player bounding boxes do not rotate, which means diagonal corridors would need to be wider (thus the majority should be axis aligned

Map scale:
32qu = 1m

Doorways should be a minimum of 3x3m, preferably around 4x4m. Corridors should be a minimum of 5m wide, although it is ''possible'' to use a mix of 4-5m (see Niveus for an example), and at most 8m wide. Do not create corridors more than 40m long without plenty of cover.
Currently large open areas and underwater areas are very human biased.

Alien bases need cover to hide things behind, the entrances should be ~4x4m and should not be easily visible from outside other entrances.

==New Features==

You may be interested in the list of [[Engine features|engine features]].

* [[Navigation Meshes]]

==Where to place your map files==

The most convenient place across platforms is to place your .bsp files and any other assets in the <code>main/maps/</code> subfolder of the [[Running_the_game#Data_locations|data location]] appropriate to your system.

==Resources==

* [http://ingar.satgnu.net/gtkradiant/ Ingar's NetRadiant builds]
* [http://www.custommapmakers.org/wiki/index.php/Main_Page Custom Map Maker's Wiki]

Old/Mapping

2012-07-29T02:05:57Z

UniqPhoeniX:

==Overview==

TODO

==Guides & Tutorials==

[http://tremulous.net/forum/index.php?topic=14411.0 Useful mapping links thread on Tremulous forums]
[http://tremmapping.pbworks.com/w/page/22453200/Starting%20Tremulous%20Mapping Starting Tremulous Mapping]
[http://tremmapping.pbworks.com/w/page/22453205/Understanding%20Vis%20and%20Hint%20Brushes Understanding Vis and Hint Brushes]
[http://q3map2.everyonelookbusy.net/shader_manual/ Shader Manual]

==Basic Guidelines==

Player sizes, in quake units (qu)
{|class="wikitable"
|Dretch ||30^3
|-
|Granger ||40^3
|-
|Adv Granger ||40^3
|-
|Basilisk ||36^3
|-
|Adv Basilisk ||42^3
|-
|Marauder ||46x46x36
|-
|Adv Marauder ||50x50x40
|-
|Dragoon ||52x52x55
|-
|Adv Dragoon ||58x58x66
|-
|Tyrant ||64x64x92
|-
|Human ||30x30x56
|-
|Crouching ||30x30x40
|-
|Battlesuit ||30x30x72
|}

Players will need an opening at least 1qu wider to fit through (possibly 2).

Map scale:
32qu = 1m

Doorways should be a minimum of 3x3m, preferably around 4x4m. Corridors should be a minimum of 5m wide, although it is ''possible'' to use a mix of 4-5m (see Niveus for an example), and at most 8m wide. Do not create corridors more than 40m long without plenty of cover.
Currently large open areas and underwater areas are very human biased.

Alien bases need cover to hide things behind, the entrances should be ~4x4m and should not be easily visible from outside other entrances.

==New Features==

You may be interested in the list of [[Engine features|engine features]].

* [[Navigation Meshes]]

==Where to place your map files==

The most convenient place across platforms is to place your .bsp files and any other assets in the <code>main/maps/</code> subfolder of the [[Running_the_game#Data_locations|data location]] appropriate to your system.

==Resources==

* [http://ingar.satgnu.net/gtkradiant/ Ingar's NetRadiant builds]
* [http://www.custommapmakers.org/wiki/index.php/Main_Page Custom Map Maker's Wiki]

Formats/Audio

2012-07-19T08:08:43Z

UniqPhoeniX: fixed a link, removed redundant text

==Overview==

TODO

==Licensing==

The following licenses are suitable for music and sounds:

* [http://creativecommons.org/licenses/sampling+/1.0/ CC-Sampling Plus]
* [http://creativecommons.org/licenses/by-sa/2.0 CC-BY-SA] (v2.0 or newer)

==Configuration files==

===Buildables===

There are 14 animations (animation types) per buildable (buildable type): ''construct1'', ''construct2'', ''idle1'', ''idle2'', ''idle3'', ''attack1'', ''attack2'', ''spawn1'', ''spawn2'', ''pain1'', ''pain2'', ''destroy1'', ''destroy2'', and ''destroyed''. Each buildable has a sound configuration file, located at ''sound/buildables/<var><buildable></var>/sound.cfg'', that describes 2 properties for each buildable animation:
* whether a unique (buildable-specific) sound is associated with the given buildable animation, and
* whether the animation's sound is to be played in a loop.
Such a file should contain a 1 for a yes answer and a 0 for a no answer, for the above 2 questions, in the given order, for each buildable animation. Technically, this means that the file should contain 28 integers (2 per animation). However, by convention, 1 line is used for each animation, and comments are added for guidance about which animation a pair of numbers refers to.

So each line in a buildable sound configuration file is formatted as follows:
<var><unique></var> <var><loop></var> //<var><filename></var>

An example of a full buildable sound configuration file is:
<pre>
1 0 //construct1.wav
0 0 //construct2.wav
1 1 //idle1.wav
0 0 //idle2.wav
0 0 //idle3.wav
0 0 //attack1.wav
0 0 //attack2.wav
0 0 //spawn1.wav
0 0 //spawn2.wav
0 0 //pain1.wav
0 0 //pain2.wav
1 0 //destroy1.wav
1 0 //destroy2.wav
0 0 //destroyed.wav
</pre>
Again, the comments only help human readers, and are indifferent to the game (do not reorder the lines!).

If, for a particular buildable, a unique sound is associated with a particular animation, then the game will look for the buildable-specific ''sound/buildables/<var><buildable></var>/<var><animation></var>.wav'' audio file, and otherwise (and also if the buildable-specific audio file cannot be found) the game will use the default ''sound/buildables/<var><team></var>/<var><animation></var>.wav'' (based on the team of the buildable).

==Sound filenames==

The structure <code>cg_customSoundNames</code> in [https://github.com/Unvanquished/Unvanquished/blob/master/src/gamelogic/gpp/src/cgame/cg_players.c src/gamelogic/gpp/src/cgame/cg_players.c] contains a list of some sounds.