Unvanquished - User contributions [en-gb]

Talk:Downloading & Installing

2015-01-05T23:37:49Z

Viech: Created page with "This page should be renamed to "Installing the game" as downloading and installing are no seperate steps really. --~~~"

This page should be renamed to "Installing the game" as downloading and installing are no seperate steps really. --[[User:Viech|Viech]] ([[User talk:Viech|talk]])

Events

2014-04-14T15:39:53Z

Viech: Remove discontinued AU/NA dev games

Special, organised games are held weekly where you will find many more players online, including many of the developers.

== What time zone am I in? ==
This will depend on your location in the world. Consult a site like http://www.worldtimezone.com/ if you don't know your GMT offset. Note that GMT = UTC.

= Weekly Public Development Games =
Held at 20:00 (8:00 PM) UTC/GMT every Sunday on the Dev Server.
{{timezone|time=Sunday 20:00}}

Maps/Parpax

2014-03-24T15:26:35Z

Viech:

File:Release v0.24.png

2014-02-02T19:30:42Z

Viech: Local screenshot

== Summary ==
Local screenshot
== Licensing ==
{{licenses/pd}}

Events

2014-01-18T18:38:37Z

Viech: Fix EU/NA Dev Game time, Add some UTC/GMT, 12/24 distinctions.

<div style="float: right; border: 1px solid #aaa; background: #ddd; padding: 1em; width: 20em; ">
===What is my timezone?===
Find the time on this list that matches your actual local time. Note that GMT is the same as UTC.

{| class='wikitable' style="width: 100%;"
|-
! Time zone
! Time inside of it
|-
| GMT-12
|{{#time:l g:i a |-12 hours}}
|-
| GMT-11
|{{#time:l g:i a |-11 hours}}
|-
| GMT-10
|{{#time:l g:i a |-10 hours}}
|-
| GMT-9
|{{#time:l g:i a |-9 hours}}
|-
| GMT-8
|{{#time:l g:i a |-8 hours}}
|-
| GMT-7
|{{#time:l g:i a |-7 hours}}
|-
| GMT-6
|{{#time:l g:i a |-6 hours}}
|-
| GMT-5
|{{#time:l g:i a |-5 hours}}
|-
| GMT-4
|{{#time:l g:i a |-4 hours}}
|-
| GMT-3
|{{#time:l g:i a |-3 hours}}
|-
| GMT-2
|{{#time:l g:i a |-2 hours}}
|-
| GMT-1
|{{#time:l g:i a |-1 hours}}
|-
| '''GMT'''
|{{#time:l g:i a}}
|-
| GMT+1
|{{#time:l g:i a |+1 hours}}
|-
| GMT+2
|{{#time:l g:i a |+2 hours}}
|-
| GMT+3
|{{#time:l g:i a |+3 hours}}
|-
| GMT+4
|{{#time:l g:i a |+4 hours}}
|-
| GMT+5
|{{#time:l g:i a |+5 hours}}
|-
| GMT+6
|{{#time:l g:i a |+6 hours}}
|-
| GMT+7
|{{#time:l g:i a |+7 hours}}
|-
| GMT+8
|{{#time:l g:i a |+8 hours}}
|-
| GMT+9
|{{#time:l g:i a |+9 hours}}
|-
| GMT+10
|{{#time:l g:i a |+10 hours}}
|-
| GMT+11
|{{#time:l g:i a |+11 hours}}
|-
| GMT+12
|{{#time:l g:i a |+12 hours}}
|-
| VST
|When you fear daylight
|-

|}

Note that your GMT offset may change over the year because of daylight-savings. </div>

Special, organised games are held weekly where you will find many more players online, including many of the developers.

Have a look at the table on your right if you don't know what time-zone you are in. Use this GMT offset on the tables below to workout when they are on for you.

= EU/NA Development Games =
Held at 20:00 (8:00 PM) UTC/GMT every Sunday on the Dev Server.
{{timezone|time=Sunday 20:00}}

= AU/NA Development Games =
Held 4:00 UTC/GMT every Saturday on the Dev Server. This is Friday night for NA citizens.
{{timezone|time=Saturday 4:00}}

Tools/Sloth

2014-01-15T03:04:12Z

Viech:

Sloth is a Python console application that generates Quake3/XreaL/Daemon compatible shader files given a texture map source directory.

The tool has been written by [[User:Viech|Viech]] and can be found on [https://github.com/Unvanquished/Sloth github].

==Features==

* Supports diffuse, normal, height, specular and addition maps as well as preview images
* Generates light emitting shaders from addition maps given a number of named colors and intensities
* Detects alpha channels and supports different blending modes
* Detects texture variants (shaders sharing non-diffuse maps)
* Can generate multiple sets at once or merge different source folders into one set
* Supports hierarchical configuraton files (per-directory/prefix/shader) for full automation
* It's not slow, it's named Sloth because it's made for lazy mappers!

==Usage==

usage: sloth.py [-h] [-e] [-v] [-f FILE] [-g] [--height-normals VALUE]
[--daemon | --xreal | --quake3] [-d SUF] [-n SUF] [-z SUF]
[-s SUF] [-a SUF] [-p SUF] [-c NAME:COLOR [NAME:COLOR ...]]
[-l VALUE [VALUE ...]] [-i VALUE [VALUE ...]]
[--color-blend-exp VALUE]
[--gt0 | --ge128 | --lt128 | --alpha-test VALUE]
[--no-alpha-shadows] [-r ROOT | -x SUF] [-t FILE] [-o DEST]
PATH [PATH ...]

Generates XreaL/Daemon shader files from directories of texture maps.

positional arguments:
PATH Path to a source directory that should be added to the
set

optional arguments:
-h, --help show this help message and exit
-e, --example-config Prints an example per-directory/shader configuration
file (default: None)
-v, --verbose Print debug information to stderr. Supply twice for
more verbosity. (default: None)
-f FILE, --config FILE
Read global configuration (takes precedence over
command line arguments) (default: None)
-g, --guess Guess additional keywords based on shader (meta)data
(default: False)
--height-normals VALUE
Modifier used for generating normals from a heightmap
(default: 1.0)

Renderers:
--daemon Use renderer features of the Daemon engine. Makes the
shaders incompatible with XreaL and Quake3. (default:
False)
--xreal Use renderer features of the XreaL engine. Makes the
shaders incompatible with Quake3. This is the default.
(default: False)
--quake3 Use renderer features of the vanilla Quake3 engine
only. (default: False)

Texture map suffixes:
-d SUF, --diff SUF Suffix used by diffuse maps (default: _d)
-n SUF, --normal SUF Suffix used by normal maps (default: _n)
-z SUF, --height SUF Suffix used by height maps (default: _h)
-s SUF, --spec SUF Suffix used by specular maps (default: _s)
-a SUF, --add SUF Suffix used by addition/glow maps (default: _a)
-p SUF, --prev SUF Suffix used by preview images (default: _p)

Light emitting shaders:
-c NAME:COLOR [NAME:COLOR ...], --colors NAME:COLOR [NAME:COLOR ...]
Add light colors with the given name, using a RGB hex
triplet. They will only be used in combination with
grayscale addition maps. (default: ['white:ffffff'])
-l VALUE [VALUE ...], --custom-lights VALUE [VALUE ...]
Add light intensities for light emitting shaders with
custom colors (grayscale addition map) (default:
[1000, 2000, 4000])
-i VALUE [VALUE ...], --predef-lights VALUE [VALUE ...]
Add light intensities for light emitting shaders with
predefined colors (non-grayscale addition map)
(default: [0, 200])
--color-blend-exp VALUE
Exponent applied to custom light color channels for
use in the addition map blend phase (default: 1.0)

Alpha blending:
--gt0 Use alphaFunc GT0 instead of smooth alpha blending.
(default: False)
--ge128 Use alphaFunc GE128 instead of smooth alpha blending.
(default: False)
--lt128 Use alphaFunc LT128 instead of smooth alpha blending.
(default: False)
--alpha-test VALUE Use alphaTest instead of smooth alpha blending.
(default: None)
--no-alpha-shadows Don't add the alphashadows surfaceparm. (default:
False)

Input & Output:
-r ROOT, --root ROOT Sets the namespace for the set (e.g.
textures/setname). Can be used to merge source folders
into a single set. (default: None)
-x SUF, --strip SUF Strip suffix from source folder names when generating
the set name (default: _src)
-t FILE, --header FILE
Use file content as a header, "// " will be prepended
to each line (default: None)
-o DEST, --out DEST Write shader to this file (default: None)

==Examples==

./sloth.py textures/source_dir1 textures/source_dir2

Generates two texture sets from the given source directories and prints the resulting shader file.

./slothy.py -r textures/setname textures/source_dir1 textures/source_dir2 -o scripts/setname.shader

Uses the same source directories but creates a single set in the "textures/setname" namespace and writes the output to the file "scripts/setname.shader".

./sloth.py --daemon textures/setname_src -o scripts/setname.shader

Generates a shader file for the Daemon engine (e.g. Unvanquished). The "_src" extension of the texture source folder will be stripped for the set name (see the -x/--strip switch).

./sloth.py -e > textures/setname_src/options.sloth

Generates an example configuration file and writes it to "textures/setname_src/options.sloth" where it will be used as a per-directory configuration.

Tools/Sloth

2014-01-10T19:44:54Z

Viech: Update features and usage

Sloth is a Python tool to generate XreaL/Daemon shader files from directories of texture maps.

The tool has been written by [[User:Viech|Viech]] and can be found on [https://github.com/Unvanquished/Sloth github].

==Features==

* Supports diffuse, normal, height, specular and addition maps as well as preview images
* Generates light emitting shaders from addition maps given a number of named colors and intensities
* Autodetects texture variants (shaders sharing non-diffuse maps)
* Can generate multiple sets at once or merge different source folders into one set
* Can prepend a header to the resulting shader file
* It's not slow, it's named Sloth because it's made for lazy mappers!

==Usage==

usage: sloth.py [-h] [-m MOD] [-g] [-d SUF] [-n SUF] [-z SUF] [-s SUF]
[-a SUF] [-p SUF] [-c NAME:COLOR [NAME:COLOR ...]]
[-l VALUE [VALUE ...]] [-i VALUE [VALUE ...]] [-e VALUE]
[-r ROOT] [-x SUF] [-t FILE] [-o DEST]
PATH [PATH ...]

Generates XreaL/Daemon shader files from directories of texture maps.

positional arguments:
PATH Path to a source directory that should be added to the
set

optional arguments:
-h, --help show this help message and exit
-m MOD, --height-normals MOD
Modifier used for generating normals from a heightmap
(default: 1.0)
-g, --guess Guess additional keywords based on shader (meta)data
(default: False)

Texture map suffixes:
-d SUF, --diff SUF Suffix used by diffuse maps (default: _d)
-n SUF, --normal SUF Suffix used by normal maps (default: _n)
-z SUF, --height SUF Suffix used by height maps (default: _h)
-s SUF, --spec SUF Suffix used by specular maps (default: _s)
-a SUF, --add SUF Suffix used by addition/glow maps (default: _a)
-p SUF, --prev SUF Suffix used by preview images (default: _p)

Light emitting shaders:
-c NAME:COLOR [NAME:COLOR ...], --colors NAME:COLOR [NAME:COLOR ...]
Add light colors with the given name, using a RGB hex
triplet. They will only be used in combination with
grayscale addition maps. (default: ['white:ffffff'])
-l VALUE [VALUE ...], --custom-lights VALUE [VALUE ...]
Add light intensities for light emitting shaders with
custom colors (grayscale addition map) (default:
[1000, 2000, 5000])
-i VALUE [VALUE ...], --predefined-lights VALUE [VALUE ...]
Add light intensities for light emitting shaders with
predefined colors (non-grayscale addition map)
(default: [0, 200])
-e VALUE, --color-blend-exp VALUE
Exponent used to transform custom light color channels
for use in the addition map blend phase (default: 1.0)

Input & Output:
-r ROOT, --root ROOT Sets the namespace for the set (e.g.
textures/setname). Can be used to merge source folders
into a single set. (default: None)
-x SUF, --strip SUF Strip suffix from source folder names when generating
the set name (default: _src)
-t FILE, --header FILE
Use file content as a header, "// " will be prepended
to each line (default: None)
-o DEST, --out DEST Write shader to this file (default: None)

User:Viech

2014-01-08T23:08:35Z

Viech:

I live in Berlin, Germany and study computer science at the Technische Universität Berlin.

As an Unvanquished project head I'm responsible for artistic direction and gameplay.

I maintain the Archlinux User Repository [https://aur.archlinux.org/packages.php?ID=61163 monthly alpha package] as well as the [https://aur.archlinux.org/packages.php?ID=59477 bleeding edge package] of Unvanquished.

I made the map [[Parpax]] and the tools [[Tools/Chameleon|Chameleon]] and [[Tools/Sloth|Sloth]].

You will usually find me on [[IRC]] if you want to chat with me.

Tools/Sloth

2014-01-08T23:03:14Z

Viech: Created page with "Sloth is a Python tool to generate XreaL/Daemon shader files from directories of texture maps. The tool has been written by Viech and can be found on [https://..."

Sloth is a Python tool to generate XreaL/Daemon shader files from directories of texture maps.

The tool has been written by [[User:Viech|Viech]] and can be found on [https://github.com/Unvanquished/Sloth github].

==Features==

* Allows configuration of map type file suffixes
* Can generate multiple sets at once or merge different source folders into one set
* Generates light emitting shaders from addition/glow maps given a number of named colors and intensities
* Can prepend a header to the resulting shader file
* Can transform light colors to addition map blend phase colors given an exponent applied to each channel
* Autodetects texture variants (shaders sharing non-diffuse maps)
* It's not slow, it's named Sloth because it's made for lazy mappers!

==Usage==

usage: sloth.py [-h] [-d SUF] [-n SUF] [-s SUF] [-a SUF] [-p SUF]
[-c NAME:COLOR [NAME:COLOR ...]] [-i VALUE [VALUE ...]]
[-e EXP] [-o DEST] [-r ROOT] [-x SUF] [-t FILE]
PATH [PATH ...]

Generates XreaL/Daemon shader files from directories of texture maps.

positional arguments:
PATH Path to a source directory that should be added to the
set

optional arguments:
-h, --help show this help message and exit
-d SUF, --diff SUF Suffix used by diffuse maps (default: _d)
-n SUF, --normal SUF Suffix used by normal maps (default: _n)
-s SUF, --spec SUF Suffix used by specular maps (default: _s)
-a SUF, --add SUF Suffix used by addition/glow maps (default: _a)
-p SUF, --prev SUF Suffix used by preview images (default: _p)
-c NAME:COLOR [NAME:COLOR ...], --colors NAME:COLOR [NAME:COLOR ...]
Add light colors with the given name, using a RGB hex
triplet (default: ['white:ffffff'])
-i VALUE [VALUE ...], --intensities VALUE [VALUE ...]
Add light intensities (default: [0, 1000, 2000, 5000])
-e EXP, --exp EXP Exponent used to transform light color channels for
use in the addition map blend phase (default: 1.0)
-o DEST, --out DEST write shader to this file (default: None)
-r ROOT, --root ROOT Force set root to this, by default the last two
directories of the source pathes are used (default:
None)
-x SUF, --strip SUF Strip suffix from source folder names when generating
the set name (default: _src)
-t FILE, --header FILE
Use file content as a header, "// " will be prepended
to each line (default: None)

Tools

2014-01-08T22:52:52Z

Viech: Added Sloth

Unvanquished has a number of tools to assist developers in creating content.

* {{Subpage|Chameleon}} is a stand-alone application to assist mappers in changing textures.
* {{Subpage|Sloth}} is a tool to generates shader files from directories of texture maps.
* {{Subpage|Archipelago}} is a web-based utility to rearrange UV islands in a model either to minimize texture sheet usage or to make room for new geometry. (Work in progress)

In addition to these tools, information pertinent to using third-party tools to create content for Unvanquished is available on this wiki as well:

* [[Blender]]
* [[Mapping|Radiant]] (all variants)

Documentation for the following tools as is relevant to creating content for Unvanquished may be written at some point in the future:

* 3ds Max
* The GIMP
* Maya
* Photoshop
* ZBrush

These tools are currently being used by or have been used by members of the team in the past for work on Unvanquished. It is less likely that documentation will be written for proprietary software packages due to typically steep licensing fees.

Glossary

2013-12-09T22:11:32Z

Viech:

==B==

* {{Definition|bp}}, {{Definition|buildpoints}} — Team wide resource spent on the construction of structures such as spawn points and base defenses. Is acquired via mining structures.

==F==

* {{Definition|feeding}} — Reckless or poor play where one dies often to no benefit, giving the enemy a resource advantage.

==R==

* {{Definition|ret}} — [[Machinegun Turret]]. A near distance human defense structure.

Glossary

2013-12-09T22:09:24Z

Viech: Remove references to old gameplay, link entities to relevant articles.

==B==

* {{Definition|bp}}, {{Definition|buildpoints}} — Team wide resource spent on the construction of structures such as spawn points and base defense. Is acquired via mining structures.

==F==

* {{Definition|feeding}} — Reckless or poor play where one dies often to no benefit, giving the enemy a resource advantage.

==R==

* {{Definition|ret}} — [[Machinegun Turret]]. A near distance human defense structure.

Template:Game locations

2013-12-05T21:59:17Z

Viech:

<noinclude>
This template lists the locations of:
* Default game install directories
* Default user storage directories used by the game
</noinclude>

{| class="wikitable"
|-
! Platform
! Variant
! Default Binary Directory (fs_libpath)
! Default Data Directory (fs_basepath)
! Default User Directory (fs_homepath)
! Notes
|-
! rowspan="2" | Windows
| 32 bit
| colspan="2" | C:\Program Files\Unvanquished
| rowspan="2" | %APPDATA%/Daemon
| rowspan="2" | '%' is a variable notation – just copy and paste it into your file browser's location bar.
|-
| 64 bit
| colspan="2" | C:\Program Files (x86)\Unvanquished
|-
! Mac
| ???
| colspan="2" | ???/Unvanquished.app/Contents/MacOS
| ~/Library/Application Support/Unvanquished
|-
! rowspan=3 | Linux
| Compiled from source
| colspan="2" | ???
| rowspan=3 | ~/.Unvanquished
| rowspan=3 | The default user directory is a [https://en.wikipedia.org/wiki/Dotfile hidden dotfile].
|-
| Arch Linux (from the AUR)
| /usr/lib/unvanquished
| /var/lib/unvanquished
|-
| Debian, Ubuntu, Mint
| colspan="2" | ???
|-
|}

Shotgun

2013-10-22T18:58:36Z

Viech:

{{MPHumanWeapon
| name = Shotgun
| image = Shotgun.jpeg
| caption = A human wielding the shotgun.
| cost = 150 credits
| damage = 5*11
| primary attack = Spray of 11 pellets
}}

Affordable and a reliable weapon obtainable at stage 1, the shotgun remains useful throughout the entire game. It fires eleven pellets, each of which does a minor amount of damage. The shotgun is deadly at short range, however, its spray of pellets spreads out drastically past a few feet. With its slow rate of fire, good reflexes are essential.

==Tactics==

* '''Do''' keep track of the distance between yourself and potentially tricky opponents like the basilisk. You might get a shot off, only to find that you've been grabbed before you can get another due to the slow rate of fire.
* '''Don't''' fire this at anything past ten feet or so, unless it's something large. Reloading the shotgun can provide an opportunity for your opponent to rush you.
* '''Don't''' be afraid to approach aliens with this, otherwise you'll be missing a lot! Like the painsaw, it is definitely a short range weapon.
* '''Do''' take advantage of strafing while using the shotgun.

[[Category:Humans]]

File:Shotgun.jpeg

2013-10-22T18:56:35Z

Viech: Viech uploaded a new version of "File:Shotgun.jpeg": Switched to third person.

FP view of shotgun, unless concept art can be obtained, this will be used in wiki page

Credits/Media

2013-10-14T18:45:55Z

Viech: /* assets */

This site should list license and author (according to the desired form of attribution) of '''every''' asset file that is shipped with the game inside the ''pak[…].pk3'' files. Please make sure you keep this site up to date when you contribute assets. Maps, even those that are shipped with the game, have to maintain and ship their own comprehensive license files, preferably as a text file in an ''about'' directory inside the pk3.

If you are part of the development team, feel free to release your work in the name of "Unvanquished Development". You can add a note that explains that you are the author.

For each directory, add one entry for any number of files that has the same author. You can use * as a wildcard character for file names. Seperate multiple files with space. When multiple patters match, the one that is highest in the list wins.

=gfx=
==2d==
*indicator-alien* indicator-level*
**'''CC-BY-SA-3.0''' by '''Dozzer'''
*crosshair-* indicator-*
**'''CC-BY-SA-3.0''' by '''Unvanquished Development''' (authored by [[User:Viech|Viech]])

=minimaps=
*parpax.* yocto.*
**'''CC-BY-SA-3.0''' by '''Unvanquished Development''' (authored by [[User:Viech|Viech]])
*arachnid2.* atcshd.* atcszalpha.* citadel.* cruz-b6.* eden-b3.* karith.* methane-beta1.* nano.* nexus6.* niveus.* orion.* procyon.* sirius.* spacetracks-r1.* thunder-b2.* transit.* tremor.* UTCS.*
**'''?''' by '''?'''

=models=
==buildables==
===reactor===
* *
**'''?''' by '''?'''

Credits/Media

2013-10-14T18:43:08Z

Viech:

Credits/Media

2013-08-16T15:36:05Z

Viech: Created page with "This site should list license and author (according to the desired form of attribution) of '''every''' asset file that is shipped with the game inside the ''pak[…].pk3'' fil..."

This site should list license and author (according to the desired form of attribution) of '''every''' asset file that is shipped with the game inside the ''pak[…].pk3'' files. Please make sure you keep this site up to date when you contribute assets. Maps, even those that are shipped with the game, have to maintain and ship their own comprehensive license files, preferably as a text file in an ''about'' directory inside the pk3.

If you are part of the development team, feel free to release your work in the name of "Unvanquished Development". You can add a note that explains that you are the author.

For each directory, add one entry for any number of files that has the same author. You can use * as a wildcard character for file names. Seperate multiple files with space.

=minimaps=
*parpax.* yocto.*
**'''CC-BY-SA-3.0''' by '''Unvanquished Development''' (authored by [[User:Viech|Viech]])
*arachnid2.* atcshd.* atcszalpha.* citadel.* cruz-b6.* eden-b3.* karith.* methane-beta1.* nano.* nexus6.* niveus.* orion.* procyon.* sirius.* spacetracks-r1.* thunder-b2.* transit.* tremor.* UTCS.*
**'''?''' by '''?'''

=models=
==buildables==
===reactor===
* *
**'''?''' by '''?'''

Maps/Parpax

2013-07-29T12:09:28Z

Viech: Added minimaps.

File:Parpax upper.png

2013-07-29T12:07:04Z

Viech:

File:Parpax lower.png

2013-07-29T12:06:47Z

Viech:

Coding convention

2013-06-06T14:41:29Z

Viech:

The style for Daemon's source code should be the same as any other Quake-derived engine, and fairly self explanatory.

== Name conventions ==

=== Filenames ===
Filenames only contains lowercase characters. If they contain more than one word, they are separated by underscores ("_").

=== typedef, struct & enum names ===

As for filenames, they only contains lowercase characters. Also, as for filenames, words are separated by underscores ("_").

* struct names ends with "_s"
* type names (typedef) ends with "_t"

=== function names ===

Their first character is lowercase, then, each new word starts with a uppercase letter.

=== variable names ===
Variable names follows function's rules.
==== local ====
==== cvar ====
They starts with the prefix "g_".

== Function definitions ==

Function definitions are to be preceded by a C-style comment containing the function name, as follows:

/*
================
GL_TextureMode
================
*/

Note that the number of equals signs is constant regardless of function name length.

Parenthesis used in function calls and control structures are to be put off by their arguments by a single space, as are square brackets used for array subscripts. Code control structures get a space following the keyword, as well.

== Spacing ==

=== Indentation ===

Indentation uses tabulation character.

=== Other spacing ===
==== Brackets ====
Brackets are separated from their content with a space, like that:

foo[ bar ] = foobar;
if ( foo )

==== Comparisons ====

Comparators are preceded and followed by spaces:

if ( foo == bar )

==== Variables names alignment ====

Variables names should be aligned:

foo varName;
foobar varName2;

== Blocks and instructions ==

There are no one-line block, nor multi-instructions line. If you need an if followed by only one line use something like that:

if ( foo )
{
bar;
}

== Assertions, self-documentation and dependency reduction ==

* When a function takes a pointer as parameter, if this pointer should never be NULL, use an assertion to test it. It helps at debugging, but also to document the code.
* When a function takes a pointer to a struct for read-only access, please mark it as a const pointer.
* If a function only needs a subpart of a struct, pass only that subpart ( by example, if you only use gentity_t->playerState_t, only give it a playerState_t*)

User:Viech

2013-04-08T15:32:31Z

Viech:

I live in Berlin, Germany and study computer science at the Technische Universität Berlin.

I'm resposible for the Archlinux User Repository [https://aur.archlinux.org/packages.php?ID=61163 monthly alpha package] as well as the [https://aur.archlinux.org/packages.php?ID=59477 bleeding edge package] of Unvanquished.

I'm currently working on the map [[Parpax]].

I can do the following in support of the project:
* Create maps
* Create simple textures
* Record and edit sound samples
* Gamelogic programming

You will usually find me on [[IRC]] if you want to chat with me.

Maps/Parpax

2013-04-08T15:30:27Z

Viech: Delta 2

File:Parpax front storage.jpg

2013-04-08T15:29:36Z

Viech: Viech uploaded a new version of "File:Parpax front storage.jpg"

Room front storage on map Parpax.

Tools/Chameleon

2013-03-24T19:37:29Z

Viech: Adjust github link.

Chameleon is a standalone GUI-based texture replacement editor written in Python and PyQt. Its main task is replacing a number of textures inside a .map file while applying scale factors and rotation to all affected surfaces. It allows you to:
* Replace old-fashioned textures with high resolution ones without loosing the alignment
* Choose the target shader/texture from a cached database
* Create and export replacement rulesets for later use

The tool is under development by [[User:Viech|Viech]] and can be found on [https://github.com/Unvanquished/Chameleon github].

Contributing/Media

2013-03-21T19:59:28Z

Viech: Typography

This page outlines information about the project as a whole so that you can get involved more quickly.

==Trying Out the Game==

{{Note|content=Please be aware that this information applies to '''all''' members of the team. You are expected to try the game at some point if you intend on contributing content to it. This is only fair to everyone else who has contributed content in the past, and ensures consistency with existing content.}}

Although there currently are very few players on servers at any point in time, you still have a couple of options to play the game to try it out:
* '''Play against bots.''' — There are currently a number of servers with enough bots that the game is playable even without any human opponents. The training server typically always has bots, and even has a few special game modes. If you compile the source yourself, you can even test the bots offline.
* '''Wait for a scheduled development game.''' — For the past several weeks, we have been scheduling games on the weekends to ensure an adequate number of players for testing. Scheduled games are all posted in the [http://unvanquished.net/forum/forumdisplay.php/35-Events Events subforum].
* '''Test offline.''' — You can always start a [[Testing#Starting_a_testing_session|testing session]] and [[Testing#Testing_with_gameplay_code|use some cheats]] to test all the different weapons and character classes.

Of course, you can always check who's playing online at any given moment via the [http://master.unvanquished.de master server status page] or with [[Osavul]], the game's stand-alone server browser.

==Licensing==

Please understand that you will be expected to license your work. You are also expected to have some basic understanding of copyright law. '''It is extremely important that you license your work correctly and that you understand the implications of what you are doing!''' Also note that assets that are of questionable origin will not be included in the game.

You are expected to use one of the following Creative Commons licenses:

{| class="progress wikitable"
! colspan="2" | Name
! colspan="4" | Features
! colspan="2" | Text
|-
! Full
! Abbreviated
! Requires attribution?
! Allows modification?
! Allows commercial use?
! Allows relicensing?
! Human-readable
! Legal Code
|-
| Creative Commons Attribution-ShareAlike 3.0 Unported
| CC BY-SA 3.0
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-sa/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-sa/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported
| CC BY-NC-SA 3.0
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nc-sa/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NoDerivs 3.0 Unported
| CC BY-ND 3.0
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nd/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nd/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
| CC BY-NC-ND 3.0
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nc-nd/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nc-nd/3.0/legalcode Legal Code]
|-
|}

All of these licenses allow redistributing your work. Please note that we would much prefer if you would use one of the former two licenses. '''You must obtain permission from a project head to use one of the latter two licenses if you would like your work to be included in the game:''' while you are certainly free to license your work as you please, using one of the latter two licenses in certain situations might prevent your work from being included.

If you disagree with all of the above licenses, please contact any of the project leads with your concerns. If you have another license in mind, please inform us. Be prepared to defend your criticisms of the Creative Commons licenses (i.e., provide a compelling argument) and your choice for another license. Be aware that more restrictive licenses are not likely to be accepted by the project heads.

===Marking your Work===

If you are working in Blender, please add a license to your work visible in the default screen layout visible in a text editor view. '''Please note that you should not do this if you are not the original creator of the work.''' For example, if you are animating a model that was created by someone else, ask '''them''' to add a notice themselves.

You are advised to use the following template:

Copyright {{CURRENTYEAR}} <var>your real name</var>.

This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
http://creativecommons.org/licenses/by-sa/3.0/

Of course, you should modify this template to match whichever license your are using.

===Mappers===

In creating a map, you likely will end up using textures from a variety of sources. You '''must''' include copies of licenses and notices of attribution for any and all textures that you use not created by yourself. Those textures which you have created yourself should be licensed as outlined above, and a notice included. It is recommended to include a file named <code><var>mapname</var>.txt</code>, <code>map-<var>mapname</var>.txt</code> or <code>map-<var>mapname</var>-<var>version</var>.txt</code> inside a directory named <code>about</code> in your [[Packaging_game_data|.pk3]].

==Introducing Yourself==

Once you have access to the developer subforums, please create a post on the [http://unvanquished.net/forum/forumdisplay.php/36-Assets-amp-Artwork Assets & Artwork] subforum telling us a little about yourself.

At the end of your introduction, please add the following information using this template:

[LIST]
[*] [B]Skillset[/B]: <var>List your skills here</var>
[*] [B]Software[/B]: <var>List software you know well here</var>
[*] [B]E-mail[/B]: <var>Please place an e-mail address that you would like to be contacted at here</var>
[*] [B]Preferred means of contact[/B]: <var>How would you like to be contacted?</var>
[*] [B]Primary operating system[/B]: <var>Which operating system (and version) do you use the most often? (E.g., Mac OS X 10.6)</var>
[*] [B]Portfolio[/B]: <var>Add links to any work that you have done that is visible on the internet</var>
[/LIST]

If you do not have a portfolio and you are a 2d or 3d artist, please upload a gallery of images of your work to imgur. Similarly, if you are an audio engineer or musician, upload your work to some audio sharing site.

You may wish to include other information, such as:

* Alternate means of contact (e.g., Skype)
* Your time zone, so that we know when we can contact you

Continue reading for more specific instructions.

==Animators==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What software do you use?
* How familiar are you with your preferred software? I.e., what features of your animation package do you utilize? For example, if you use Blender, do you know how to use actions and constraints?

We currently use the MD5 format for animations. Please familiarize yourself with the following documentation before beginning to animate anything:

* Read the [[Modeling#Workflow_overview|workflow overview]]. This explains the workflow shared by our artists for bringing a concept into reality. You are expected to understand this. If you have any questions, do not hesitate to ask.
* From the model exporting guide, please read the [[Exporting_Models#Overview|overview]] and the [[Exporting_Models#What_is_MD5.3F|What is MD5?]] section. You will need to understand these in order to be able to create an animation that can successfully be exported from your animation package of choice and loaded into the game.

In particular, you are expected to know the limitations of the MD5 format. '''If you do not respect these limitations, you are guaranteed to have a great deal if difficulty when attempting to export your model.''' While the art lead is more than willing to provide help to get your asset in-game, you would be wasting his/her time by not reading the documentation beforehand; it is only respectful to do so.

==Audio Engineers & Musicians==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What hardware and instruments do you have access to?
* If you are a musician, what instruments do you play? If you don't play an instrument, what do you compose music with?
* If you are a musician, what sort of music do you like to compose?
* If you are an audio engineer, what is your particular skillset?

You are expected to familiarize yourself with the following:

* Please read the [[Music_and_sounds|documentation]] on music and sounds. Be aware that at the time of writing (19 March 2013), this information is rather inadequate, but it will at least answer some questions.
* Please take a look at the [[Sound_Progress|sound progress]] page for an idea of what sounds there are that need replacement.

In addition, you should be aware that as of the time of writing (19 March 2013), all of the sounds present in Unvanquished were inherited from Tremulous (with the exception of the main menu music) and '''must''' be replaced. '''Note that this is non-negotiable''': the sounds from Tremulous were later revealed to be stolen from various sources and cannot legally be included. As this is an open-source project, this sort of copyright infringement is not acceptable.

==Concept Artists==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What is your preferred medium? E.g., do you draw with a tablet in Photoshop, or do you use pencil and paper? Be specific.
* What is your greatest strength with respect to drawing? I.e., what is the one thing that you think you are the best at drawing?
* How long do you expect it to take to create a concept? We're not [http://clientsfromhell.net/ clients from hell], so we're not going to pressure you to do things quickly, but we'd just like to know in advance if it might take a week or whatever so that know you haven't just died on us if we don't hear from you for a while!

Please be aware:

* If you are unsure of what you would like to work on, please familiarize yourself with both the [[Aliens|alien]] and [[Humans|human]] teams.
* Be aware that you are expected to [[#Trying_Out_the_Game|try the game]] at some point!
* If you would like to know what character and weapon models have not been completed that are therefore available to create a concept for, take a look at the [[modeling progress]] page. Anything that is not being worked on is fair game, even if other concepts have been made before.
* There is not currently a listing of all the concepts made for the game, so you will have to browse the [http://unvanquished.net/forum/forumdisplay.php/36-Assets-amp-Artwork Assets & Artwork subforum] for now.

==Mappers==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What maps have you released to the public in the past, and for what games?
* What experience do you have with mapping software? Include any and all software that you have used, even if it was not for a Quake-derived game, and some indication of your skill with that software.

You are expected to familiarize yourself with the following:

* Pleas read the [[Mapping|mapping guide]] all the way through. You do not necessarily need to know how to use every feature of the tools right away, but you should understand the basics.
* [[Packaging_game_data|How to get data in the game]]. This is less important when you begin mapping, but you must understand this when you approach time to release or upload your map online for testing. Ideally, you would not be creating a final release of your map without at least one beta test version.

==Modelers==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What software do you '''prefer''' to use?
* What is your personal workflow? Do you begin with a high poly model and retopo that? Or do you begin and end with the geometry that will end up in the final game?
* Are you capable of completing a modeling assignment, or will you need assistance? If you will need assistance (e.g., with retopoing, unwrapping, texturing, rigging, or animation), please inform us. Be specific.
* Are you familiar with modern techniques? Specifically, we'd like to know if you know what the following are and how to use them:
** Normal maps
** Bump maps
** Specular maps
** Glow maps
** Parallax mapping
** Smoothing groups
* Are you familiar with the idea of not storing lighting information in your diffuse texture? '''If you do not understand what this means, please ask.''' A guide will eventually be written on this.
* Is hardware an issue? E.g., if you are going to be editing a very high poly model, do you have a video card that can handle that?

You are expected to familiarize yourself with the following:

* Read the [[Modeling#Workflow_overview|workflow overview]]. This explains the workflow shared by our artists for bringing a concept into reality. You are expected to understand this. If you have any questions, do not hesitate to ask.
* From the model exporting guide, please read the [[Exporting_Models#Overview|overview]]. If you are not going to animate your model yourself, this is less important, but it is good to know anyway.

==Texture Artists==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* Are you familiar with the idea of not storing lighting information in your diffuse texture? '''If you do not understand what this means, please ask.''' A guide will eventually be written on this.

You are expected to familiarize yourself with the following:

* Please read the [[texture creation]] guide. This contains important information about what formats the engine supports and where you can obtain special tools that you may need to create content specifically for our engine.

Contributing/Media

2013-03-21T19:57:13Z

Viech: Recommend using the "about" directory and unique names for map readme files.

This page outlines information about the project as a whole so that you can get involved more quickly.

==Trying Out the Game==

{{Note|content=Please be aware that this information applies to '''all''' members of the team. You are expected to try the game at some point if you intend on contributing content to it. This is only fair to everyone else who has contributed content in the past, and ensures consistency with existing content.}}

Although there currently are very few players on servers at any point in time, you still have a couple of options to play the game to try it out:
* '''Play against bots.''' — There are currently a number of servers with enough bots that the game is playable even without any human opponents. The training server typically always has bots, and even has a few special game modes. If you compile the source yourself, you can even test the bots offline.
* '''Wait for a scheduled development game.''' — For the past several weeks, we have been scheduling games on the weekends to ensure an adequate number of players for testing. Scheduled games are all posted in the [http://unvanquished.net/forum/forumdisplay.php/35-Events Events subforum].
* '''Test offline.''' — You can always start a [[Testing#Starting_a_testing_session|testing session]] and [[Testing#Testing_with_gameplay_code|use some cheats]] to test all the different weapons and character classes.

Of course, you can always check who's playing online at any given moment via the [http://master.unvanquished.de master server status page] or with [[Osavul]], the game's stand-alone server browser.

==Licensing==

Please understand that you will be expected to license your work. You are also expected to have some basic understanding of copyright law. '''It is extremely important that you license your work correctly and that you understand the implications of what you are doing!''' Also note that assets that are of questionable origin will not be included in the game.

You are expected to use one of the following Creative Commons licenses:

{| class="progress wikitable"
! colspan="2" | Name
! colspan="4" | Features
! colspan="2" | Text
|-
! Full
! Abbreviated
! Requires attribution?
! Allows modification?
! Allows commercial use?
! Allows relicensing?
! Human-readable
! Legal Code
|-
| Creative Commons Attribution-ShareAlike 3.0 Unported
| CC BY-SA 3.0
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-sa/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-sa/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported
| CC BY-NC-SA 3.0
| class="done" style="text-align:center;" | Yes
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nc-sa/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NoDerivs 3.0 Unported
| CC BY-ND 3.0
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nd/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nd/3.0/legalcode Legal Code]
|-
| Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
| CC BY-NC-ND 3.0
| class="done" style="text-align:center;" | Yes
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| class="none" style="text-align:center;" | No
| [http://creativecommons.org/licenses/by-nc-nd/3.0/ License Deed]
| [http://creativecommons.org/licenses/by-nc-nd/3.0/legalcode Legal Code]
|-
|}

All of these licenses allow redistributing your work. Please note that we would much prefer if you would use one of the former two licenses. '''You must obtain permission from a project head to use one of the latter two licenses if you would like your work to be included in the game:''' while you are certainly free to license your work as you please, using one of the latter two licenses in certain situations might prevent your work from being included.

If you disagree with all of the above licenses, please contact any of the project leads with your concerns. If you have another license in mind, please inform us. Be prepared to defend your criticisms of the Creative Commons licenses (i.e., provide a compelling argument) and your choice for another license. Be aware that more restrictive licenses are not likely to be accepted by the project heads.

===Marking your Work===

If you are working in Blender, please add a license to your work visible in the default screen layout visible in a text editor view. '''Please note that you should not do this if you are not the original creator of the work.''' For example, if you are animating a model that was created by someone else, ask '''them''' to add a notice themselves.

You are advised to use the following template:

Copyright {{CURRENTYEAR}} <var>your real name</var>.

This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
http://creativecommons.org/licenses/by-sa/3.0/

Of course, you should modify this template to match whichever license your are using.

===Mappers===

In creating a map, you likely will end up using textures from a variety of sources. You '''must''' include copies of licenses and notices of attribution for any and all textures that you use not created by yourself. Those textures which you have created yourself should be licensed as outlined above, and a notice included. It is recommended to include a file named <code><mapname>.txt</code>, <code>map-<mapname>.txt</code> or <code>map-<mapname>-<version>.txt</code> inside a directory named <code>about</code> in your [[Packaging_game_data|.pk3]].

==Introducing Yourself==

Once you have access to the developer subforums, please create a post on the [http://unvanquished.net/forum/forumdisplay.php/36-Assets-amp-Artwork Assets & Artwork] subforum telling us a little about yourself.

At the end of your introduction, please add the following information using this template:

[LIST]
[*] [B]Skillset[/B]: <var>List your skills here</var>
[*] [B]Software[/B]: <var>List software you know well here</var>
[*] [B]E-mail[/B]: <var>Please place an e-mail address that you would like to be contacted at here</var>
[*] [B]Preferred means of contact[/B]: <var>How would you like to be contacted?</var>
[*] [B]Primary operating system[/B]: <var>Which operating system (and version) do you use the most often? (E.g., Mac OS X 10.6)</var>
[*] [B]Portfolio[/B]: <var>Add links to any work that you have done that is visible on the internet</var>
[/LIST]

If you do not have a portfolio and you are a 2d or 3d artist, please upload a gallery of images of your work to imgur. Similarly, if you are an audio engineer or musician, upload your work to some audio sharing site.

You may wish to include other information, such as:

* Alternate means of contact (e.g., Skype)
* Your time zone, so that we know when we can contact you

Continue reading for more specific instructions.

==Animators==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What software do you use?
* How familiar are you with your preferred software? I.e., what features of your animation package do you utilize? For example, if you use Blender, do you know how to use actions and constraints?

We currently use the MD5 format for animations. Please familiarize yourself with the following documentation before beginning to animate anything:

* Read the [[Modeling#Workflow_overview|workflow overview]]. This explains the workflow shared by our artists for bringing a concept into reality. You are expected to understand this. If you have any questions, do not hesitate to ask.
* From the model exporting guide, please read the [[Exporting_Models#Overview|overview]] and the [[Exporting_Models#What_is_MD5.3F|What is MD5?]] section. You will need to understand these in order to be able to create an animation that can successfully be exported from your animation package of choice and loaded into the game.

In particular, you are expected to know the limitations of the MD5 format. '''If you do not respect these limitations, you are guaranteed to have a great deal if difficulty when attempting to export your model.''' While the art lead is more than willing to provide help to get your asset in-game, you would be wasting his/her time by not reading the documentation beforehand; it is only respectful to do so.

==Audio Engineers & Musicians==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What hardware and instruments do you have access to?
* If you are a musician, what instruments do you play? If you don't play an instrument, what do you compose music with?
* If you are a musician, what sort of music do you like to compose?
* If you are an audio engineer, what is your particular skillset?

You are expected to familiarize yourself with the following:

* Please read the [[Music_and_sounds|documentation]] on music and sounds. Be aware that at the time of writing (19 March 2013), this information is rather inadequate, but it will at least answer some questions.
* Please take a look at the [[Sound_Progress|sound progress]] page for an idea of what sounds there are that need replacement.

In addition, you should be aware that as of the time of writing (19 March 2013), all of the sounds present in Unvanquished were inherited from Tremulous (with the exception of the main menu music) and '''must''' be replaced. '''Note that this is non-negotiable''': the sounds from Tremulous were later revealed to be stolen from various sources and cannot legally be included. As this is an open-source project, this sort of copyright infringement is not acceptable.

==Concept Artists==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What is your preferred medium? E.g., do you draw with a tablet in Photoshop, or do you use pencil and paper? Be specific.
* What is your greatest strength with respect to drawing? I.e., what is the one thing that you think you are the best at drawing?
* How long do you expect it to take to create a concept? We're not [http://clientsfromhell.net/ clients from hell], so we're not going to pressure you to do things quickly, but we'd just like to know in advance if it might take a week or whatever so that know you haven't just died on us if we don't hear from you for a while!

Please be aware:

* If you are unsure of what you would like to work on, please familiarize yourself with both the [[Aliens|alien]] and [[Humans|human]] teams.
* Be aware that you are expected to [[#Trying_Out_the_Game|try the game]] at some point!
* If you would like to know what character and weapon models have not been completed that are therefore available to create a concept for, take a look at the [[modeling progress]] page. Anything that is not being worked on is fair game, even if other concepts have been made before.
* There is not currently a listing of all the concepts made for the game, so you will have to browse the [http://unvanquished.net/forum/forumdisplay.php/36-Assets-amp-Artwork Assets & Artwork subforum] for now.

==Mappers==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What maps have you released to the public in the past, and for what games?
* What experience do you have with mapping software? Include any and all software that you have used, even if it was not for a Quake-derived game, and some indication of your skill with that software.

You are expected to familiarize yourself with the following:

* Pleas read the [[Mapping|mapping guide]] all the way through. You do not necessarily need to know how to use every feature of the tools right away, but you should understand the basics.
* [[Packaging_game_data|How to get data in the game]]. This is less important when you begin mapping, but you must understand this when you approach time to release or upload your map online for testing. Ideally, you would not be creating a final release of your map without at least one beta test version.

==Modelers==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* What software do you '''prefer''' to use?
* What is your personal workflow? Do you begin with a high poly model and retopo that? Or do you begin and end with the geometry that will end up in the final game?
* Are you capable of completing a modeling assignment, or will you need assistance? If you will need assistance (e.g., with retopoing, unwrapping, texturing, rigging, or animation), please inform us. Be specific.
* Are you familiar with modern techniques? Specifically, we'd like to know if you know what the following are and how to use them:
** Normal maps
** Bump maps
** Specular maps
** Glow maps
** Parallax mapping
** Smoothing groups
* Are you familiar with the idea of not storing lighting information in your diffuse texture? '''If you do not understand what this means, please ask.''' A guide will eventually be written on this.
* Is hardware an issue? E.g., if you are going to be editing a very high poly model, do you have a video card that can handle that?

You are expected to familiarize yourself with the following:

* Read the [[Modeling#Workflow_overview|workflow overview]]. This explains the workflow shared by our artists for bringing a concept into reality. You are expected to understand this. If you have any questions, do not hesitate to ask.
* From the model exporting guide, please read the [[Exporting_Models#Overview|overview]]. If you are not going to animate your model yourself, this is less important, but it is good to know anyway.

==Texture Artists==

In addition to the [[#Introducing_Yourself|above information]], we'd like to know the following about you:

* Are you familiar with the idea of not storing lighting information in your diffuse texture? '''If you do not understand what this means, please ask.''' A guide will eventually be written on this.

You are expected to familiarize yourself with the following:

* Please read the [[texture creation]] guide. This contains important information about what formats the engine supports and where you can obtain special tools that you may need to create content specifically for our engine.

Tools/Chameleon

2013-03-07T19:14:56Z

Viech:

Tools/Chameleon

2013-01-10T15:08:54Z

Viech: Created page with "Chameleon is a standalone GUI-based texture replacement editor written in Python and PyQt. Its main task is replacing a number of textures inside a .map file while applying sc..."

Talk:Main Page

2012-11-10T20:17:02Z

Viech: Improvement ideas

1) The link to the developement blog is outdated, it is now included on the main page. 2) I maintain the arch linux package so we could set its description to (semi-)official to let people know that they can give feedback on IRC and forums. 3) The Links section could be organized in a table like the Contributing section. --[[User:Viech|Viech]]

Maps/Parpax

2012-10-20T16:11:04Z

Viech: Marked information outdated

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 8-16
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~8900
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~1900
|}

'''The information on this page relates to the outdated Beta 2 of Parpax. It will be updated as soon as the map's layout has come to a more static form.'''

A medium sized, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor. Its front entrance consists of huge shutter doors that lead to a big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of ventilation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and ventilation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

==Human Strategy==
'''Do''' use [[Jetpack|jetpack]] to fly over the strange machine in the alien's default base and drop grenades right at the slimy feet of the [[Overmind]].

==Alien Strategy==
'''Do''' use non-advanced [[Basilisk|basilisks]] and [[Marauder|marauders]] to enter the human's default base via the pipe shafts.

[[Category:Maps]]

Old/Mapping

2012-09-30T19:12:04Z

Viech: link to map test server, addtions/corrections to testing maps in-game

==Overview==

Map geometry is created using either a conventional modeling program (such as Blender) or with some variant of Radiant. Do note that if you intend on using Blender, you will need to use Radiant to perform a few final steps. This is discussed further below.

Radiant is the name used to refer to id Software's map editing tools from Quake 3 onwards.

* QuakeEd — Developed internally at id and used to create maps for Quake. Written for NextStep.
* QE4 — Developed internally at id and used to create maps for Quake II.
* QERadiant — A fork of the released QE4 source code by Robert Duffy.
* Q3Radiant' — id Software's fork of QERadiant used to create maps for Quake III. Windows-only.
* [http://icculus.org/gtkradiant/ GtkRadiant] — A port of Q3Radiant using the Gtk+ GUI toolkit, making it cross-platform (available to Linux and Mac OS X). Development stalled after 1.5 for a number of years, but has resumed with the recent release of version 1.6, which (for now) removes support for a number of games, including Tremulous.
* [http://dev.alientrap.org/projects/show/netradiant NetRadiant] — A fork of GtkRadiant (?) by Alientrap, developers of the former (FOSS) Nexuiz project. The project page for this fork is currently down, but builds are still available from noted Tremulous mapper [http://ingar.satgnu.net/gtkradiant/ Ingar's site].
* [http://darkradiant.sourceforge.net/ DarkRadiant] — A fork of GtkRadiant with the aim to improve the user interface and primarily intended to support Doom 3.
* [http://www.redsaurus.net/00/node/4 MacRadiant] — A port of GtkRadiant to Mac OS X.


===Compilation===

Creation of a map using either method is only part of the process; before a map can be played in-game, the map must then be <dfn>compiled</dfn>. This is a time-consuming process that can take hours even with new hardware. Compilation consists of several phases, discussed below. Note that it is not essential to understand precisely what happens in each of these phases. At a minimum, understand that compilation must occur before a map is ready to be played and that it is a highly time-consuming process.

* '''Space partitioning'''. Map geometry is subdivided (partitioned) in half successively, effectively breaking the map down into progressively smaller chunks. The reason for this is to improve in-game render speed; this is done in such a manner that the engine can quickly determine what portions of the map the player is not facing, and therefore avoid having to render such areas.   The scheme  by which this is done is referred to as [http://en.wikipedia.org/wiki/Binary_space_partitioning binary spatial partitioning], and this (as well as the data structure storing this information) is most often referred to as BSP. With each split, the compiler attempts to minimize the amount of geometry that must be cut to minimize the resulting size of the BSP. 
* '''[http://en.wikipedia.org/wiki/Potentially_visible_set Potentially visible set] calculation'''. This stage of compilation takes the rendering boost that BSP provides by  calculating which regions of the map are visible when viewed from other areas. Each of these areas for which a potentially visible set (PVS) is calculated is referred to as a <dfn>cell</dfn> or <dfn>portal</dfn>.  As an example, imagine standing in a room in a house.  Using only BSP, the game engine could very quickly determine which rooms you are not facing (as if the rooms were made of glass and every room were visible from every other room), and skip drawing them. However, while standing in that room, there are many other rooms in the house that you likely also cannot see (as the walls of the rooms are probably not glass and very much opaque). This is PVS in a nutshell: for that room, the PVS might only be an adjoining hallway and a closet (assuming that the doors are open). In a large house with many rooms, in a worst-case scenario (where both the player is facing the hallway and the closet at the same time), the engine still has very little to draw as compared to the entire house. This is discussed in greater detail on [http://fabiensanglard.net/doom3/dmap.php Fabien Sanglard's blog].
* '''Lightmap calculation'''. Using the position, color, and type  of lights placed in the map editor, the compiler generates a static <dfn>lightmap</dfn> which is essentially painted over (blended with) the map textures at run-time to create shadows and areas of light and dark. (Otherwise, the map would be the same brightness throughout and devoid of shadow). Note that this is not the extent of the engine's lighting capabilities; additional (dynamic) lighting is performed in real-time to create effects such as light generated from muzzle flashes. 



===Using other than Radiant to create maps===

Conventional modeling software other than Blender is outside of the scope of this document; only Blender will be discussed. 

While geometry other than triangles may be used during map creation, the map compilation tools can only handle brush geometry; as of now, the <code>.map</code> exporter for Blender can only convert polygonal geometry (triangles) to brushes, and as such it would be pointless to use anything else during the construction of a map except as a placeholder. 

A comprehensive guide of using Blender to create map geometry ready for Radiant and the compilation tools is available from [http://www.katsbits.com/tutorials/blender/map-basics-tutorial.php katsbits].

==Design mentality==

This section is oriented towards those with less experience mapping.

There are many potential pitfalls of map creation. Possibly the easiest to fall into is spending too little time on design and spending too much time on map details before even having a working base design. There is an adage that applies well here: "Weeks of effort will save hours of planning." Before you begin creating, do not concern yourself so much with visual elements but the physical layout of the map.

When designing a map, consider the following:
* What can players use to help themselves navigate the map? What would make a good landmark or how can different areas of the map be differentiated visually?
* Is the map partitioned well visibly? Are there any areas that may cause poor performance?
* Are corridors large enough to facilitate combat?
* Does the map provide other good locations to build in aside the defaults?
* Is the map biased towards one side or another?

==Using GtkRadiant==

===Editing brush geometry===

* Click and drag to create a new brush.
* With a brush selected, click and drag the mouse cursor to change the size of the selected brushes.
* Press Esc to deslect everything.
* Press and hold Shift and click brushes to select them.

===Placing entities===

* Right-click in a 2d viewport to access the entity placement context menu. 

===Navigating the views===

====3d viewport====

* Scroll using the mouse wheel to dolly the camera forward or back.
* Right-click on the viewport to look around. Using the mouse wheel to dolly the camera works while in this mode.

====2d viewports====

* Right-click and drag to move the views around.
* Change the view with the toolbar button:

[[Image:gtkradiant_toolbar_change_views.png|center]]

==Size Guidelines==

Player sizes, in quake units (qu)
{|class="wikitable"
|Dretch ||303
|-
|Granger ||403
|-
|Adv Granger ||403
|-
|Basilisk ||363
|-
|Adv Basilisk ||423
|-
|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 3m×3m, preferably around 4m×4m. 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 ~4×4m 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]]
* Additional shader functions (e.g., normal mapping) have been added; please see the [http://tremap.xtr3m.net/__Games/Xreal/Manual_Shader_1/ShaderManual.htm XReal shader manual] for more information.

==Testing maps in-game==

For testing purposes, it is most convenient to place your compiled <code>.bsp</code> file in the <code>main/maps/</code> subdirectory of the [[Running_the_game#Data_locations|data location]] appropriate to your system. Once you have done that, you may load your map with either the <code>devmap</code> or <code>map</code> commands after setting <code>sv_pure 0</code>. The former allows using cheats that make it easier to test. Additional commands are discussed on the [[testing]] page.

==Testing maps publicly==

You can put the map on the [http://188.40.187.142/ Map Test Server], as soon as you [[Packaging game data|packaged]] it accordingly. The server allows unfinished (alpha) versions and can get you early feedback on your design.

==Packaging maps for distribution==

When it comes time to distribute your map to the world (either for testing or as a final release), you'll have to create a compressed [[Packaging game data|package]]. This package may be distributed automatically via the server download feature or other means.

==Resources==

* [http://ingar.satgnu.net/gtkradiant/ Ingar's NetRadiant builds]
** [http://ingar.satgnu.net/gtkradiant/files/gamepacks/UnvanquishedPack.zip Unvanquished game pack]
* [http://www.custommapmakers.org/wiki/index.php/Main_Page Custom Map Maker's Wiki]
* [http://dev.xonotic.org/projects/xonotic/wiki/Mapping Xonotic mapping resources]
* [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/ Quake 3 Shader Manual] (outdated; please see the XReal shader manual)
* [http://tremap.xtr3m.net/__Games/Xreal/Manual_Shader_1/ShaderManual.htm XReal Shader Manual]
* [http://q3map2.robotrenegade.com/ Q3Map2 homepage]
* [http://en.wikibooks.org/wiki/Q3Map2 Q3Map2 Documentation]
* [http://shaderlab.com/q3map2/manual/ Additional Q3Map2 Documentation]

Testing

2012-09-26T22:27:13Z

Viech: Added map test server, reorganized

==Debugging==

To create a debug build, change <code>CMAKE_BUILD_TYPE</code> in CMake from <code>Release</code> to <code>Debug</code>, then [[Compiling_the_source|compile]].

You may find it necessary to set <code>in_nograb</code> to <code>1</code> to disable pointer grabbing so that you may use your debugger.

===Debugging with Xcode===

With Xcode 4, even if you did not build the game with Xcode, you may still use its facilities for debugging.

# Open any project. If necessary, create a new one. It may contain anything.
# Click "Product" on the menu bar and navigate to "Attach to Process". Look for "daemon.i386" listed under "Applications".

After a moment, the application will be ready for debugging.

See the [https://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/060-Debug_Your_App/debug_app.html#//apple_ref/doc/uid/TP40010215-CH3-SW1 Xcode 4 User Guide] for more information.

==Starting a testing session==

Start the game, and enter the following commands:

\sv_pure 0
\devmap <var>map name</var>

You may also load a map with the regular <code>\map</code> command. Be aware, however, that <code>devmap</code> enables cheats which can make it easier to test (such as being able to jump directly to stage 2 or 3 if required). Also note that with <code>devmap</code>, the build time for buildables is zero, so the building animation(s) will not play.

==Tips==

===General tips===

* To stress test the engine's ability to display a large number of buildables, set <code>g_humanBuildPoints</code> or <code>g_alienBuildPoints</code> to as high as you wish; this will allow you to build as much as you please.
* To determine what file was loaded for a particular asset (e.g., to determine if files are being read from a particular <code>.pk3</code> archive), use the <code>\which</code> command with the relative path to the asset as an argument, such as <code>\which models/buildables/acid_tube/acid_tube.md5mesh</code>. Note that <code>which</code> accepts both forward- and backslashes regardless of platform.

===Testing maps===

* To fly around the map, use the <code>\noclip</code> command. If you find that you are moving too slowly (or too fast), you may change the speed with <code>cg_flySpeed</code>.
* To make yourself invincible, use the <code>\god</code> command.
* To stop buildables from attacking, use the <code>\notarget</code> command.
* To publicly test your maps, upload them on the [http://188.40.187.142/ Map Test Server].

===Testing models===

* If the model is a buildable, weapon, or player model that is not immediately available (i.e., not available until a later stage), you can change the stage with <code>g_alienStage</code> or <code>g_humanStage</code>. Both of these cvars accept a single parameter, which is the zero-based index of the stage; to skip to stage 2, use 1 as a parameter, and to skip to stage 2, use 2 as a parameter (stage 1 is 0).
* If you do not have sufficient credits to purchase an item model you wish to test, or evos to evolve to the desired class, you may give yourself the maximum amount that you can carry with <code>\give all</code>.
* To visually inpsect a model's bounding box, which is set by its configuration file, set <code>\cg_drawBBOX</code> to 1.
* To visually inspect the bone structure of a MD5 model, set <code>r_showSkeleton</code> to 1. ''Note: at present there is a bug that causes bones to be displayed incorrectly. See [https://github.com/Unvanquished/Unvanquished/issues/2 Issue #2] on GitHub for more information.''
* To hide map geometry, set <code>r_drawworld</code> to <code>0</code>. Note that with this set to <code>0</code>, PVS will still be in effect, so it might still be difficult to view your model.

==Reporting bugs==

Please see the [[Bug_reporting|bug reporting]] page.

Feature proposals

2012-09-26T22:22:02Z

Viech: Marked as deprecated

'''This page is deprecated, use the [http://unvanquished.net/ideas/ idea tracker] for new feature proposals! Ideas on this page should be migrated over there.'''

This is a page to list and elaborate on engine features to implement in the future. As with the [[Game_design_proposals|gameplay proposals]] page, it is not the place to argue or otherwise discuss the validity or merit of these ideas; just to list them and build upon their description. Do not delete any idea for any reason, spam and trolling excepted (but if an idea has been rejected, mark it as deleted and add text describing why). If you would like to discuss any proposed feature or idea, do so in the associated talk page for this page.

==Ragdoll death animations==

===Trapper===

The trapper (and likely other alien structures, in future) poses an interesting problem in that it remains attached to the ceiling when it dies, but one would expect its tail to fall down and flop about realistically. As it stands now, the death animation only looks correct when it is built on the floor. A simple Newtonian particle physics system with springs should do to procedurally calculate positions of the tail bones.

==GUI controls to adjust game balance==

A config tree could be added, where each node is one of
* Tree (has more subnodes)
* Boolean
* Integer
* Float
* String

This would allow to access and adjust every configurable number in the following way:

game.buildings.reactor.health = ...
game.classes.dretch.weight = ...
network.port = ...
client.width = ...

Everyone who has seen about:config in Firefox knows how such options can be edited.

==Random idle animations==

Play a different idle animation every so often for buildable and player models.

==Detailed build animations==

Detailed build animations ala StarCraft II would be a lovely feature.

===Human buildings===

Human buildings when building might show geometry that would not otherwise be shown. For this reason, an entirely separate model and animation with this detail may be deemed necessary (depending on how much geometry is hidden, and how many buildables can be expected to be on screen at one time).

Maps/Parpax

2012-08-31T01:03:20Z

Viech: Adjusted number of brushes.

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 8-16
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~8900
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~1900
|}

A medium sized, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor. Its front entrance consists of huge shutter doors that lead to a big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of ventilation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and ventilation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

==Human Strategy==
'''Do''' use [[Jetpack|jetpack]] to fly over the strange machine in the alien's default base and drop grenades right at the slimy feet of the [[Overmind]].

==Alien Strategy==
'''Do''' use non-advanced [[Basilisk|basilisks]] and [[Marauder|marauders]] to enter the human's default base via the pipe shafts.

[[Category:Maps]]

Maps/Parpax

2012-08-30T15:26:56Z

Viech: Corrections, statistic adjustments, more strategy hints

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 8-16
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~8800
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~1900
|}

A medium sized, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor. Its front entrance consists of huge shutter doors that lead to a big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of ventilation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and ventilation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

==Human Strategy==
'''Do''' use [[Jetpack|jetpack]] to fly over the strange machine in the alien's default base and drop grenades right at the slimy feet of the [[Overmind]].

==Alien Strategy==
'''Do''' use non-advanced [[Basilisk|basilisks]] and [[Marauder|marauders]] to enter the human's default base via the pipe shafts.

[[Category:Maps]]

File:Parpax Gameflow.jpg

2012-08-26T03:16:59Z

Viech: uploaded a new version of "File:Parpax Gameflow.jpg": Adjusted for Beta 2/3.

The gameflow graph of the map Parpax.

Maps/Parpax

2012-08-26T03:01:17Z

Viech: Adjusted for Beta 2/3.

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 8-16
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~8400
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~1800
|}

A medium sized, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor. Its front entrance consists of huge shutter doors that lead to a big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

==Human Strategy==
TODO

==Alien Strategy==
TODO

[[Category:Maps]]

Maps/Parpax

2012-08-18T03:58:37Z

Viech: Description updated (Beta 2)

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9600
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~2200
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactor]]'s reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

Maps/Parpax

2012-08-15T23:25:25Z

Viech: Linked talk page.

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9600
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~2200
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in beta status. You can post bugs, critics and improvement ideas on the [[Parpax:Talk|talk page]].

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

Both default bases have a third entrance that can be opened temporarily by pushing a button located in the respective base. The button in the human base moves aside girders that block access to the ventilation shafts. The aliens' button opens an emergency exit that is a short path to the stairs and connects to the elevation shaft.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

'''Don't''' open the third entrance to your base carelessly as it might not have as good protection as the other two entrances.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactor]]'s reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

Voice say system

2012-08-13T18:23:05Z

Viech: Corrected "/vsay_area" to "/vsay_local".

The Daemon engine [http://unvanquished.net/forum/entry.php/5-Unvanquished-Alpha-2-Voice-Say has added support] for voice says (also known as "vsays"), which are short, pre-recorded audio messages used to communicate with one's team.

{| class="wikitable"
! Abbreviation
! Human Message
! Alien Message
|-
| <code>attacking</code>
| colspan="2" style="text-align:center;" | I'm attacking.
|-
| <code>attack</code>
| colspan="2" style="text-align:center;" | Attack!
|-
| <code>backup</code>
| colspan="2" style="text-align:center;" | I need backup!
|-
| <code>baserepairs</code>
| colspan="2" style="text-align:center;" | Base needs repairs!
|-
| <code>basestatus</code>
| colspan="2" style="text-align:center;" | What's the base status?
|-
| <code>bequiet</code>
| style="text-align:center;" | Be quiet!
| style="text-align:center;" | N/A
|-
| <code>builders</code>
| colspan="2" style="text-align:center;" | We need builders!
|-
| <code>building</code>
| colspan="2" style="text-align:center;" | I'm building.
|-
| <code>clearthepath</code>
| colspan="2" style="text-align:center;" | Clear the path!
|-
| <code>defending</code>
| colspan="2" style="text-align:center;" | I'm defending.
|-
| <code>defend</code>
| colspan="2" style="text-align:center;" | Defend!
|-
| <code>eggs</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | We need more eggs!
|-
| <code>enemyisnear</code>
| style="text-align:center;" | Careful, enemy nearby.
| style="text-align:center;" | Enemy is near!
|-
| <code>enemyomdown</code>
| style="text-align:center;" | Enemy Overmind down!
| style="text-align:center;" | N/A
|-
| <code>enemyspawnsdown</code>
| colspan="2" style="text-align:center;" | Enemy spawns down!
|-
| <code>enemynodesdown</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | Enemy telenodes down!
|-
| <code>enemyterritory</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | Enemy territory!
|-
| <code>fallback</code>
| colspan="2" style="text-align:center;" | Fall back!
|-
| <code>fixbase</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | The base needs fixing!
|-
| <code>flank</code>
| colspan="2" style="text-align:center;" | Flank!
|-
| <code>following</code>
| colspan="2" style="text-align:center;" | I'm following you.
|-
| <code>followme</code>
| colspan="2" style="text-align:center;" | Follow me.
|-
| <code>gogogo</code>
| colspan="2" style="text-align:center;" | Go! Go! GO!
|-
| <code>grangers</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | We need grangers!
|-
| <code>grenade</code>
| style="text-align:center;" | Grenade!
| style="text-align:center;" | Watch out, grenade!
|-
| <code>holdback</code>
| colspan="2" style="text-align:center;" | Hold back.
|-
| <code>holdposition</code>
| colspan="2" style="text-align:center;" | Hold this position.
|-
| <code>incoming</code>
| colspan="2" style="text-align:center;" | Incoming!
|-
| <code>inposition</code>
| style="text-align:center;" | I'm in position.
| style="text-align:center;" | N/A
|-
| <code>moveup</code>
| colspan="2" style="text-align:center;" | Move up!
|-
| <code>mowemdown</code>
| style="text-align:center;" | Mow 'em down!
| style="text-align:center;" | N/A
|-
| <code>needammo</code>
| style="text-align:center;" | I need ammo!
| style="text-align:center;" | N/A
|-
| <code>needbasi</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | Need friend basi!
|-
| <code>needhealth</code>
| colspan="2" style="text-align:center;" | I need health!
|-
| <code>no</code>
| colspan="2" style="text-align:center;" | No.
|-
| <code>rebuildbase</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | Base needs rebuilding.
|-
| <code>regroup</code>
| colspan="2" style="text-align:center;" | Regroup.
|-
| <code>reporting</code>
| colspan="2" style="text-align:center;" | Reporting in!
|-
| <code>retreat</code>
| style="text-align:center;" | Retreat!
| style="text-align:center;" | N/A
|-
| <code>silence</code>
| style="text-align:center;" | N/A
| style="text-align:center;" | Silence!
|-
| <code>sorry</code>
| colspan="2" style="text-align:center;" | Sorry!
|-
| <code>spawns</code>
| colspan="2" style="text-align:center;" | We need spawns!
|-
| <code>stayalert</code>
| colspan="2" style="text-align:center;" | Stay alert!
|-
| <code>stayalive</code>
| colspan="2" style="text-align:center;" | Stay alive!
|-
| <code>stayfocused</code>
| style="text-align:center;" | Stay focused!
| style="text-align:center;" | Stay focused.
|-
| <code>sticktogether</code>
| colspan="2" style="text-align:center;" | Stick together!
|-
| <code>thanks</code>
| colspan="2" style="text-align:center;" | Thanks!
|-
| <code>watchout</code>
| style="text-align:center;" | Watch out!
| style="text-align:center;" | N/A
|-
| <code>yes</code>
| colspan="2" style="text-align:center;" | Yes.
|}

==Usage==

<code>/vsay <var>abbreviation</var></code>

Use a voice say message that can be seen and heard by your entire team.

<code>/vsay_local <var>abbreviation</var></code>

Use a voice say message that can be seen and heard by nearby teammates.

Maps/Parpax

2012-08-13T14:22:36Z

Viech:

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9600
|-
| style="text-align:right;vertical-align:top" | '''No. of patches:'''
| style="text-align:left;vertical-align:top" | ~2200
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in a late alpha status and has not yet been released to public.

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

Both default bases have a third entrance that can be opened temporarily by pushing a button located in the respective base. The button in the human base moves aside girders that block access to the ventilation shafts. The aliens' button opens an emergency exit that is a short path to the stairs and connects to the elevation shaft.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

'''Don't''' open the third entrance to your base carelessly as it might not have as good protection as the other two entrances.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactor]]'s reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

Maps/Parpax

2012-08-13T13:29:33Z

Viech: Added an image.

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| colspan="2" style="color:white;background-color:black;text-align:center" cellpadding="1" cellspacing="0" | [[Image:Parpax_front_storage.jpg|300px]] ''front storage seen from elevator''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9.5k
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in a late alpha status and has not yet been released to public.

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

Both default bases have a third entrance that can be opened temporarily by pushing a button located in the respective base. The button in the human base moves aside girders that block access to the ventilation shafts. The aliens' button opens an emergency exit that is a short path to the stairs and connects to the elevation shaft.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

'''Don't''' open the third entrance to your base carelessly as it might not have as good protection as the other two entrances.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactor]]'s reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

File:Parpax front storage.jpg

2012-08-13T13:23:34Z

Viech: Room front storage on map Parpax.

Room front storage on map Parpax.

File:Parpax Gameflow.jpg

2012-08-13T13:16:02Z

Viech: uploaded a new version of "File:Parpax Gameflow.jpg": Small corrections.

The gameflow graph of the map Parpax.

User:Viech

2012-08-13T13:03:48Z

Viech: Added link to my contributions

I live in Berlin, Germany and study computer science at the Technische Universität Berlin.

I'm resposible for the Archlinux User Repository [https://aur.archlinux.org/packages.php?ID=61163 monthly alpha package] as well as the [https://aur.archlinux.org/packages.php?ID=59477 bleeding edge package] of Unvanquished.

I'm currently working on the Tremulous map [[Parpax]], which I'm planning to port to Unvanquished later. I've been asked to join the [[Developers|development team]] as a level designer as soon as I begin porting.

I can do the following in support of the project:
* Create maps
* Create simple textures
* Record and edit sound samples

You can browse my [http://levi.servequake.com/unvanquished/ contributions].

You will usually find me on [[IRC]] if you want to chat with me.

Maps/Parpax

2012-08-12T21:08:56Z

Viech: /* Human Strategy */

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9.5k
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in a late alpha status and has not yet been released to public.

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

Both default bases have a third entrance that can be opened temporarily by pushing a button located in the respective base. The button in the human base moves aside girders that block access to the ventilation shafts. The aliens' button opens an emergency exit that is a short path to the stairs and connects to the elevation shaft.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect in a small space. Even if one survives the ride, there may be a heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room in front of your default base's front entrance in order to defeat enemies before they get too close to your base. However, don't forget to have a look at the base itself as they are still able to sneak in.

'''Don't''' open the third entrance to your base carelessly as it might not have as good protection as the other two entrances.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactor]]'s reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

Maps/Parpax

2012-08-12T20:47:00Z

Viech: Created page with "{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0" | colspan="2" style="background-color:rgb(187,187,187);text-al..."

{| style="float:right;margin:1em 0px 1em 1em;border:2px outset #777;" border="0" cellpadding="1" cellspacing="0"
| colspan="2" style="background-color:rgb(187,187,187);text-align:center" | '''Parpax'''
|-
| style="text-align:right;vertical-align:top" | '''Designated no. of players:'''
| style="text-align:left;vertical-align:top" | 6-12
|-
| style="text-align:right;vertical-align:top" | '''No. of brushes:'''
| style="text-align:left;vertical-align:top" | ~9.5k
|}

A small, intense map by [[User:Viech|Viech]].

It is currently in a late alpha status and has not yet been released to public.

==Gameflow==
[[Image:Parpax_Gameflow.jpg|200px|thumb|right|Gameflow chart]]

The map consists of two floors connected by stairs, an elevator and ventilation shafts.

The [[Humans|human team]] has their default base on the lower floor in a spacious storage room containing huge pillars carrying a platform which can be reached via stairs and a ladder. The front entrance consists of huge shutter doors that open slowly and are prone to trap both attacking aliens and humans fleeing back to their base. It leads to another big storage room which connects to stairs, elevator and elevation shafts and thus is of great tactical importance to both teams. The side entrance of the human base leads to a narrow corridor which runs next to that room and ends at the stairs. The lower floor also contains a network of elevation and pipe shafts, giving small aliens and lightly armored humans additional movement options.

The [[Aliens|aliens]] have their default base in a tight room containing a strange machine. Its front entrance leads to a room which is, being close to stairs, elevator and elevation shafts, the counterpart of the storage room laying right under it. The side entrance leads to a longer but maybe less contested path to the stairs that also connects to the upper ends of the ventilation shafts.

Both default bases have a third entrance that can be opened temporarily by pushing a button located in the respective base. The button in the human base moves aside girders that block access to the ventilation shafts. The aliens button opens an emergency exit that is a short path to the stairs and connects to the elevation shaft.

The elevator is supposed to be the shortest but most dangerous path from one default base to the other. The car is open at the top and allows small aliens or grenades to slip inside and deliver their devasting effect on small space. Even if one survives the ride there might be some heavily armed greeting committee waiting at the other end of the shaft. While big aliens or battlesuits have only the stairs as a less dangerous alternative, lighter forces can also use the ventilation shafts or even the elevator shaft itself for movement between the floors.

==General Strategy==
'''Do''' try to control the big room that lays in front of your default bases front entrance in order to defeat enemys before they get too close to your base. However, don't forget to have a look at the base itself as enemys are still able to sneak in.

'''Don't''' open the third entrance to your base carelessly as it might not have as good protection as the other two entrances.

==Human Strategy==
'''Do''' use [[Repeater|repeaters]] to protect all entrances to your default base as the [[Reactor|reactors]] reach isn't big enough to power the whole room.

==Alien Strategy==
TODO

[[Category:Maps]]

Formats/Navigation mesh

2012-08-12T19:13:11Z

Viech:

The Daemon engine supports automatic navigation mesh generation from bsp map files. This navigation mesh (or "navmesh" for short) is used by the bots to navigate throughout the world.

==Generating a Navigation Mesh==

The -nav parameter to OWMap will generate a navigation mesh from a bsp file.
Use it like so:

===Windows===

OWMap.exe -game tremulous -nav mapname.bsp

===Linux===

./daemonmap.x86(_64) -game tremulous -nav mapname.bsp

===Optional Parameters===

The navigation mesh generation process is conservative by default. This means some areas (particularly, small ledges) that should be walkable may instead create a break in the navmesh which bots interpret as "I am unable to go past there." The following optional parameters give the map maker some control over navmesh generation to help with this.

<ul>
<li><code>-cellsize</code>

''Default'': 8

This value (along with <code>cellheight</code>) determines the accuracy of navigation mesh generation. A lower value will increase mesh generation accuracy at the cost of generation time and mesh size; conversely, a higher value will decrease generation time and mesh size at the cost of accuracy.

If you see gaps in the navigation mesh on "grating" floors where the grating parts, try using a higher value.
</li>
<li><code>-cellheight</code>

A lower cellheight will increase mesh generation accuracy at the cost of generation time and mesh size.

If there are gaps in the navigation mesh even though a player can easily just walk to get through, you can decrease the value to help.
</li>
<li><code>-median</code>

Applies a median filter to the walkable areas of the mesh to help contain any "noise."

See [http://digestingduck.blogspot.com/2010/07/recast-area-types-per-triangle.html this article] for more information.
</li>
<li><code>-optimistic</code>

Attempts to compensate for cellsize inaccuracy by increasing the stepheight navigation mesh generation parameter based on the current samplesize. It is recommended to be used with a lower than default cellsize to help avoid over optimistic assumptions (i.e., saying some areas are walkable that really aren't). Useful for fixing breaks in the mesh caused by some small ledges.

This produces bad results depending on how big your <code>cellsize</code> parameter is, but generating the mesh in this way will be faster than simply decreasing the <code>cellheight</code>.
</li>
</ul>

==Using a Navigation Mesh==

Navigation mesh files go in the <code>maps/</code> directory either in the folder specified by the <code>fs_game</code> cvar, or in the maps folder inside a map's <code>.pk3</code> file.

==Testing the Mesh==

<ol>
<li>Start a local server by starting Unvanquished and typing

\devmap testmap

into the console.

You may then enable drawing the navigation mesh by setting the <code>cg_bot_nav</code> cvar to <code>1</code>.


</li>
<li>Add bots with the <code>bot</code> command and spectate the game.
</li>
</ol>

==Editing the Navigation Mesh==
Unfortunately, automatic navigation mesh generation that fully supports all of the map features and player abilities in Unvanquished is increadibly difficult.
Automatic generation will usually produce a very satisfactory base mesh, but some areas may need further tweaking

===Adding Jump Links===
===Adding Ladder Links===
===Adding Pounce Links===
===Adding Drop off Links===
===Adding Walk Links===
[[Category:Bots]]