Unvanquished - User contributions [en-gb]

Clans

2021-02-22T10:04:57Z

Derek:

Clans are groups inside the game. Clan tags are usually used in tournaments to identify players.

Try learning Callouts to inprove your game: https://wiki.unvanquished.net/wiki/Call_Outs

To add your clan tag go to menu>player and click on "nickname" then put <code>^1[Clan-Tag](another colour)your name</code>

= Current in-game clans: =

The first and only clan as of now is:

=== KING ===

King was founded by Derek and has two members:

# Derek
# RNGLatico

----
///Put other clans here and their description and list players

Call Outs

2021-02-22T10:04:26Z

Derek:

Callouts in Unvanquished are crucial. These were made by us for personal use and skill improvement.

What is a Call Out?

According to the Oxford Dictionary "a statement drawing critical attention to someone's unacceptable actions or behaviour."

A Call Out is a way to drag attention to a location ex: Humans are pushing Ventilation. here we can see the noun is "Humans" the verb is "Pushing" meaning that they are trying to take control of the region and the Call Out is "Ventilation" this system helps communication in the game grow and also enables the player to simplify the names of Places that are tightly woven. for example "Ventilation" is the room "Ventilation" and "Ventilation shaft" combined because we know that if a human is pushing into Ventilation they have to be inside the shaft to enter.

Callouts are great with clans - https://wiki.unvanquished.net/wiki/Clans

# Antares

Storage - Alien Spawn base https://i.ibb.co/G5W3w1m/Storage.jpg

Storage East - Rightside of Storage (Ventilation) (This term is mainly used to tell that people are coming in through that enterance rather than stating people are in ventilation and you are holding them back - https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/knSDjsbhucBqQpgCWFEablqh

Ventilation [Can be called shaft] (Usage: Humans Pushing Ventilation)

Processing-

Processing can be split into three parts.

Processing-Vent or Processing-V (The Part of Processing that is closest to the Ventilation area)

Processing (Middle Region of Processing)

Processing-C or Processing-Corridor (More on this later).

This is a Diagram of what I've said https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/NjMzHTzYdMehVYiwsmYiBtmI

Processing-C is the Processing Corridor. which links into the Human Base.

Human Base will just be called Human Base instead of the room name. There fore Level Access will mean the Room across Processing-C which is close to Main Corridor.

Compiling the source

2021-02-17T10:52:08Z

Derek: /* Debian/Ubuntu */

==macOS==

First, you need to [[Getting_the_source|acquire the source code]].

Regardless of what interface you may use to compile the source, you will need [http://www.cmake.org/cmake/resources/software.html CMake] to generate makefiles. You will also need to install [https://developer.apple.com/xcode/ Xcode] (making sure to choose to install the command-line utilities when prompted by the installer).

Then, you will need to acquire (and in some cases, manually compile) at a minimum the [[#Dependencies|necessary libraries]].

Once you have the source code and the libraries installed, you may actually proceed to compile the source. You have several options:
* '''Compile the source at the command line'''. This is the easiest if you would just like to compile the game to use yourself and you do not intend to work on the code.
* '''Compile the source using an IDE'''. This is preferred if you intend on developing the source.
** Xcode is Apple's flagship IDE and you should have installed to compile the source regardless of which method you use.
** [http://qt-project.org/downloads QtCreator] is cross-platform and provides real-time feedback of syntax errors, a Vim mode, as well as other features.
** [http://www.codeblocks.org/ Code::Blcoks] is also cross-platform but lacks some of the features of Xcode and QtCreator.

===Dependencies===

You only need to use one of the following methods (HomeBrew or compiling by hand). Please try and avoid mixing methods as this may produce unexpected results.

Unvanquished requires the following libraries:
* [[#JPEG|JPEG]], version 8 or higher. (Version 6 was known to have problems)
* [[#Simple_DirectMedia_Layer_.28SDL.29|Simple DirectMedia Layer]] (The binary provided by libsdl.org causes graphical corruptions. Compile from source or use homebrew/macports)
* [[#The_OpenGL_Extension_Wrangler_Library_.28GLEW.29|The OpenGL Extension Wrangler Library]]
* CuRL
* [[#The_GNU_MP_Bignum_Library_.28libgmp.29|GMP]]
* [[#WebP|WebP]] (v0.2.0 or newer)

The following libraries are optional:
* Theora
* Speex
* [[#Ogg|Ogg]]
* [[#Vorbis|Vorbis]]

====HomeBrew====
Install [http://mxcl.github.com/homebrew/ HomeBrew] and then run the following command

$ brew install nettle libjpeg curl sdl webp xvid gmp glew speex libvorbis theora

All the necessary libraries should now have been installed.

====Compiling by hand====
This is more time consuming than other methods but might be useful if you need more control over your libraries.

=====JPEG=====

$ curl http://www.ijg.org/files/jpegsrc.v8d.tar.gz > jpegsrc.v8d.tar.gz
$ tar xvzf jpegsrc.v8d.tar.gz
$ cd jpeg-8d
$ ./configure
$ make
$ sudo make install

=====The OpenGL Extension Wrangler Library (GLEW)=====

$ curl -L https://sourceforge.net/projects/glew/files/glew/1.7.0/glew-1.7.0.tgz/download > glew-1.7.0.tgz
$ tar xvzf glew-1.7.0.tgz
$ cd glew-1.7.0
$ make
$ sudo make install

=====Simple DirectMedia Layer (SDL)=====

Do not use the binaries provided by libsdl.org, as these are known to cause issues with gamma and color display. Instead, compile your own:

$ curl http://www.libsdl.org/release/SDL-1.2.15.tar.gz > SDL-1.2.15.tar.gz
$ tar xvzf SDL-1.2.15.tar.gz
$ cd SDL-1.2.15
$ ./configure
$ make
$ sudo make install

=====The GNU MP Bignum Library (libgmp)=====

$ curl ftp://ftp.gmplib.org/pub/gmp-5.0.5/gmp-5.0.5.tar.bz2 > gmp-5.0.5.tar.bz2
$ tar xvjf gmp-5.0.5.tar.bz2
$ cd gmp-5.0.5
$ ./configure
$ make
$ sudo make install

=====Ogg=====

$ curl http://downloads.xiph.org/releases/ogg/libogg-1.3.0.tar.gz > libogg-1.3.0.tar.gz
$ tar xvzf libogg-1.3.0.tar.gz
$ cd libogg-1.3.0
$ ./configure
$ make
$ sudo make install

=====Vorbis=====

$ curl http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.3.tar.gz > libvorbis-1.3.3.tar.gz
$ tar xvzf libvorbis-1.3.3.tar.gz
$ cd libvorbis-1.3.3
$ ./configure
$ make
$ sudo make install

=====WebP=====

You do not need to compile WebP by hand; Google provides binaries for Mac OS X available from their [https://code.google.com/p/webp/downloads/detail?name=libwebp-0.2.0-mac-10.5.tar.gz project page]. You will need version 0.2.0 or newer.

Once downloaded, you must still install the header files and the binary:

$ curl https://webp.googlecode.com/files/libwebp-0.2.0-mac-10.5.tar.gz > libwebp-0.2.0-mac-10.5.tar.gz
$ tar xvzf libwebp-0.2.0-mac-10.5.tar.gz
$ cd libwebp-0.2.0-mac-10.5
$ sudo cp include/webp /usr/local/include
$ sudo cp lib/libwebp.a /usr/local/lib

===Configuring with CMake===

# Run CMake.
# Enter the location of the source code.
# Enter the location in which you would like to build the source code. This should be a different directory.
# Click "Configure". You will be prompted as to which generator you would like to use. If you have Xcode installed, choose that. Wait while the configuration process runs. You may have to set the following:
## If CMake did not find your jpeg headers for some reason, set <code>JPEG_INCLUDE_DIR</code> to <code>/path/to/Unvanquished/src/libs/jpeg</code>.
## If you have selected to generate Xcode project files, make the <code>SDLMAIN_LIBRARY</code> field blank. This option is not available if you have the generator set to Unix makefiles.
# Click "Generate".
# You may now close CMake.

===Compiling===

====With Xcode====

<ol>
<li>Either start Xcode and open the project file (in the build directory you specified) or double-click the project file in Finder.</li>
<li>Open the project file created by CMake, which should be in the build directory you specified.</li>
<li>Change the active target to "ALL_BUILD" and click Product→Build.</li>
</ol>

====With Unix Makefiles====

<ul>
<li>Start Terminal (Applications → Utilities → Terminal).</li>
<li>Type the following commands:
<pre>
$ cd /path/to/Unvanquished-build
$ make
</pre>
If you are on a multi-core or multi-processor machine, you may speed up the process by passing the <code>-j</code> argument followed by the number of available cores to <code>make</code>; e.g., <code>make -j4</code>. Note that doing so makes reading error messages more difficult, as multiple instances of the compiler will print to the screen at once, causing information to appear out of order.
</li>
</ul>

===Testing the build===

====With Xcode 4====

To test the game, select the "client" scheme from the combo box on the toolbar, and click the run button or press {{Hotkey|MacCommand}}{{Hotkey|R}}.

====With Unix Makefiles====

After compiling, you'll have to place the data files in the <code>main</code> directory in your build directory. [[#Acquiring the Game Files|For download instructions, see below.]]

Your file structure should look as follows:

[[File:Build_dir_Mac_OS_X.png]]

You may now start the application as such:

$ ./daemon.i386

===Bundling the Application===

====With CPack====

CPack is able to create standalone bundles (as well as many other types of installers). However you must generate the files using Unix Makefiles instead of Xcode.

$ cd /path/to/Unvanquished-build
$ cpack -G Bundle

Some warnings will be printed however these can be safely ignored. There should be a file called Unvanquished.dmg in the Unvanquished-build folder.

====Manually====

{{Note|header=Important|content=
Please be aware that these instructions are very much out of date, and may not work. Also note that the dynamic library bundler does '''not''' work as intended and although you will be able to run your build on your machine, it will most likely not work on other machines. It is strongly suggested that you compile the source using Xcode.
}}

You'll find the Mac [http://macdylibbundler.sourceforge.net/ dynamic library bundler] to be quite useful (you must generate the files using Unix Makefiles instead of Xcode):

$ curl -L http://sourceforge.net/projects/macdylibbundler/files/macdylibbundler/0.4.1/dylibbundler0.4.1.zip/download > \
dylibbundler0.4.1.zip
$ unzip dylibbundler0.4.1.zip
$ cd dylibbundler
$ make
$ sudo make install

Once you've done that, you can proceed to create the application bundle. Note that these steps assume that you have downloaded the data files to <code>main/</code> as shown above:

<pre>
$ git=/path/to/Unvanquished-git-repo
$ build=/path/to/Unvanquished-build-dir
$ mkdir -pv Unvanquished.app/Contents/{libs,MacOS,Resources,Frameworks}
$ cp -r $build/main Unvanquished.app/Contents/MacOS
$ sips -s format tiff $git/debian/unvanquished.png --out temp.tiff
$ tiff2icns temp.tiff Unvanquished.app/Contents/Resources/Unvanquished.icns
$ rm temp.tiff
$ cp $build/daemon{,ded}.i386 $build/*.dylib Unvanquished.app/Contents/MacOS
$ cp -r /Library/Frameworks/SDL.framework Unvanquished.app/Contents/Frameworks
$ install_name_tool -id \
@executable_path/../Frameworks/SDL.framework/Versions/A/SDL \
Unvanquished.app/Contents/Frameworks/SDL.framework/Versions/A/SDL
$ install_name_tool -change @rpath/SDL.framework/Versions/A/SDL \
@executable_path/../Frameworks/SDL.framework/Versions/A/SDL \
Unvanquished.app/Contents/MacOS/daemon.i386
$ install_name_tool -change @rpath/SDL.framework/Versions/A/SDL \
@executable_path/../Frameworks/SDL.framework/Versions/A/SDL \
Unvanquished.app/Contents/MacOS/librendererGLi386.dylib
$ install_name_tool -change @rpath/SDL.framework/Versions/A/SDL \
@executable_path/../Frameworks/SDL.framework/Versions/A/SDL \
Unvanquished.app/Contents/MacOS/librendererGL3i386.dylib
$ for binary in Unvanquished.app/Contents/MacOS/*.{i386,dylib}; do
dylibbundler -b -x $binary -d $dest/Unvanquished.app/Contents/libs/; done
$ cp /usr/lib/libGLEW.1.7.0.dylib ./Unvanquished.app/Contents/libs/libGLEW.1.7.0.dylib
$ chmod +w ./Unvanquished.app/Contents/libs/libGLEW.1.7.0.dylib
$ install_name_tool -id @executable_path/../libs/libGLEW.1.7.0.dylib \
./Unvanquished.app/Contents/libs/libGLEW.1.7.0.dylib
$ install_name_tool -change /usr/lib/libGLEW.1.7.0.dylib \
@executable_path/../libs/libGLEW.1.7.0.dylib \
./Unvanquished.app/Contents/MacOS/daemon.i386
$ cat > Unvanquished.app/Contents/Info.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleName</key>
<string>Unvanquished</string>
<key>CFBundleDisplayName</key>
<string>Unvanquished</string>
<key>CFBundleExecutable</key>
<string>daemon.i386</string>
<key>CFBundleIconFile</key>
<string>Unvanquished.icns</string>
<key>CFBundleIdentifier</key>
<string>net.Unvanquished</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>0.4.0</string>
<key>CFBundleVersion</key>
<string>0.4.0</string>
</dict>
</plist>
^d
</pre>

Note: <code>^d</code> indicates pressing {{Hotkey|Ctrl}}{{Hotkey|D}} on the keyboard.

The contents of the completed application bundle should look like this:

[[File:Bundle_dir_Mac_OS_X.png]]

'''Note''': If you compiled SDL from source, you will not see a directory titled <code>SDL.framework</code>.

==Windows==

===Visual Studio===

CMake can generate Visual Studio projects for Unvanquished.

# Add _NO_DEBUG_HEAP=1 to your environment variables otherwise performance under the debugger [http://www.massimpressionsprojects.com/dev/altdevblog/2011/07/27/the-unexpected-performance-of-debug-builds/ will be terrible]
# Run CMake with the source directory as the base directory of your source code (which should contain directories such as <code>main</code> and <code>src</code>), and the build directory as a subdirectory of the source directory named <code>build</code>.
# Open <code>build/Daemon.sln</code> in Visual Studio 2013.
# In the two text boxes in the toolbar, select "Release" or "Debug" in the first one and Win32 in the second one
# Use Build → Build Solution to compile the code (or just press {{Hotkey|F5}} to build and run).

====Important Notes====

* ncurses is not supported under Visual Studio.
* Due to limitations with CMake, the startup project cannot be specified. This must be set manually to debug the client with Visual Studio:
** Right click on client and select "Set as StartUp project".

===MinGW===

It is possible to build Unvanquished with MinGW.

====Notes====

* The easiest way to acquire and install MinGW is with the graphical [http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/ mingw-get-inst installer]. At a minimum, you will need to install the C and C++ compilers. 
* When configuring the build with CMake, you will find that you will have to set a number of libraries manually. You can find precompiled DLLs for most of the dependencies; those that are not pre-compiled can be built with the corresponding <code>USE_INTERNAL_</code> setting.

====Instructions====

The easiest way to get a build up (at the time of writing) is as follows:

{{Note|content=Although there are 64-bit binaries of most of the libraries required to build the game, these do not work with MinGW at present, so the following instructions all use the 32-bit binaries.}}

<ol>

<li>Open a command prompt and <code>cd</code> to your source directory.</li>
<li>Run <code>make</code>:
<pre>
> mingw32-make
</pre>
If you would like verbose output, set the <code>VERBOSE</code> environment variable before running <code>make</code>.
<pre>
> set VERBOSE=1
</pre>
To make it easier to build the source, you can create a batch file (call it something like <code>compile.bat</code>) and place it in your build directory:
<pre>
@echo off

set RETURN=compile

:get_time
:: Thank you, Rob van der Woude:
:: (http://www.robvanderwoude.com/datetimentparse.php)
FOR /F "tokens=1,2,3 delims=:." %%A IN ("%Time%") DO (
SET /A HOURS = 100%%A %% 100
SET /A MINUTES = 100%%B %% 100
SET /A SECONDS = 100%%C %% 100
)
SET /A TICKS=( %HOURS% * 3600 ) + ( %MINUTES% * 60 ) + %SECONDS%
GOTO %RETURN%

:compile
SET START_TICKS=%TICKS%

SET VERBOSE=1
:: mingw32-make clean
mingw32-make -j4

set RETURN=finish
GOTO get_time

:finish
SET /A COMPILE_TIME=%TICKS% - %START_TICKS%
SET /A MINUTES=%COMPILE_TIME% / 60
SET /A SECONDS=%COMPILE_TIME% %% 60
ECHO.
ECHO Compilation took %MINUTES%m %SECONDS%s.
PAUSE
</pre>
</li>
<li>Once compilation finishes, you may find that the game will fail to run due to DLL dependencies. To resolve these:
<ul>
<li>The following DLLs need to be in the same directory as the executable. They should be copied into the appropriate build directory automatically.
* freetype6.dll
* libcurl.dll
* libpng14-14.dll
* zlib1.dll
If the renderer's DLL dependencies are not met, you will be informed that the game failed to load a renderer. If you receive an error stating that the application failed to start at all, then you are likely missing some version of the Microsoft Visual C runtime redistributable.
<p>You may find that you also need these DLLs (if you configured your build differently):</p>
* libbz2.dll
* libogg.dll
* libtheora.dll
* libvorbis.dll
* libvorbisfile.dll
* msvcr100.dll
* msvcr100d.dll
* zlibwapi.dll
The easiest way to obtain these DLLs is by copying them from the installation directory of an [http://sourceforge.net/projects/unvanquished/files/latest/download official release] of Unvanquished.
</li>
</ul>
Once you have completed these steps, you should never have to do them again.
</li>
</ol>

====Notes====

* If you would like to use curses, try using [http://sourceforge.net/projects/pdcurses/files/pdcurses PDCurses].

===QtCreator===

# Install MinGW and follow the above instructions, except select Code::Blocks as the generator.
# Start QtCreator, and select "Open File or Project…" from the File menu.
# Navigate to your source directory and open CMakeLists.txt.
# At the CMake Wizard, select the same build directory you already configured using CMake. (If you did not chose Code::Blocks as the generator, you will have to start over again, as QtCreator requires a Code::Blocks project file in order to compile the source.)
# Ensure that a generator is selected in the combo box, and click "Run CMake". If there is no generator listed, see the [[#Troubleshooting|troubleshooting]] section below.
# Click "Finish" to close the wizard.

You should now be able to compile, run, and debug the code using QtCreator.

====Troubleshooting====

If at the "Run CMake" prompt of the the CMake Wizard, select "Run CMake" and are warned that no generator was selected, and notice that there are no generators in the combo box, you will likely have to [http://doc.qt.digia.com/qtcreator-2.4/creator-tool-chains.html manually configure your toolchain]. Select "Options…" from the "Tools" menu, then navigate to "Build & Run".

At the options window,
* Go to the "Kits" tab, and mouse over the "Desktop (default)" kit under "Manual". If there were any errors in configuring this kit, they will be displayed in the tool tip. If there are problems, select the kit. You may need to manually specify the location of the MinGW debugger, for example, which is typically <code>C:\MinGW\bin\gdb.exe</code>.
* Go to the "Compilers" tab, and ensure that MinGW is present. If not, you will need to add it manually.

==Linux==

===Dependencies===


====Debian/Ubuntu====

sudo apt-get install build-essential cmake libcurl4-gnutls-dev \
libglew-dev libgmp-dev nettle-dev zlib1g-dev libncursesw5-dev \
libsdl2-dev libopenal-dev libjpeg-turbo8-dev libpng-dev libwebp-dev \
libogg-dev libvorbis-dev libtheora-dev libopusfile-dev \
libgeoip-dev libfreetype6-dev \
python3-yaml python3-jinja2

If libsdl2-dev isn't available, you can use libsdl1.2-dev instead.

If the version of WebP supplied by your version of Debian or Ubuntu is older than v0.2.0, you will need to [https://code.google.com/p/webp/downloads/detail?name=libwebp-0.2.0.tar.gz download] and [https://developers.google.com/speed/webp/docs/compiling#unix compile it from source]. After compiling and installing with <code>sudo make install</code>, in CMake, you'll need to set <code>WEBP_INCLUDE_DIR</code> to <code>/usr/local/include/webp</code> and <code>WEBP_LIBRARY</code> to <code>/usr/local/lib/libwebp.so</code>.

Actual dev package names may vary, e.g. libgmp3-dev instead of libgmp-dev and libglew1.7-dev instead of libglew-dev.

Since we have a debian directory in the source, you can also to check what's needed then install the listed packages (choosing from alternatives as needed):

cd <var>/path/to/unvanquished</var>
dpkg-checkbuilddeps
…
sudo apt-get install <var>package(s)</var>

If dpkg-checkbuilddeps produces no output, you have all necessary build dependencies. Also, debhelper's only needed if you're building .debs.

====Fedora====

(This was tested to work on fedora 22 workstation)

$ sudo dnf install \
cmake gcc gcc-c++ \
{GeoIP,glew,gmp,lua,mesa-libGL,ncurses,nettle,openal-soft,opus,opusfile,SDL2,speex}-devel \
lib{curl,jpeg-turbo,png12,theora,vorbis,webp}-devel

====Gentoo====

$ emerge curl freetype glew gmp jpeg ncurses libogg openal libpng libsdl libvorbis zlib

====openSUSE====

$ sudo install zypper gcc gcc-c++ Mesa-libGL-devel SDL-devel libjpeg8-devel \
libpng12-devel glew-devel webp-devel ncurses-devel gmp-devel libcurl-devel \
libnettle-devel openal-soft-devel speex-devel libvorbis-devel \
libtheora-devel

The latest version of WebP must be installed manually:

$ wget https://webp.googlecode.com/files/libwebp-0.2.1.tar.gz
$ tar xvzf libwebp-0.2.1.tar.gz
$ cd libwebp-0.2.1
$ ./configure && make
$ sudo make install

You must disable curses (set <code>USE_CURSES</code> appropriately in CMake) as failing to do so will cause Unvanquished to crash on startup.

===Configuring the code with CMake===

After you have [[Getting the source|acquired the source code]], you can proceed to compile. Unvanquished uses CMake, so you must have that installed.

====Using ccmake (curses-based front-end)====

On Debian or Ubuntu:

$ sudo apt-get install cmake-curses-gui

On Gentoo you should set the '''ncurses''' USE flag either globally or individually, just for cmake.
To add the USE flag globally, edit the USE array in /etc/make.conf for it to include '''ncurses'''.
To only install cmake with ncurses functionality, you could do the following:

$ echo 'dev-util/cmake ncurses' >> /etc/portage/package.use && emerge cmake

Note that in Ubuntu, <code>cmake-curses-gui</code> is in Universe, which you may have to enable with <code>software-properties-gtk</code>. Make sure to reload the software sources with <code>sudo apt-get update</code> afterwards.

Optionally: to use clang (rather than the default gcc and g++ compilers) export the CC and CXX variables before running cmake:

$ export CC="clang"
$ export CXX="clang++ -stdlib=libc++ -lc++abi"

Next, configure the codebase.

$ cd <var>/path/to/unvanquished</var>
$ mkdir build
$ cd build
$ ccmake ..

Or, in Debian or Ubuntu, you can build a package (but you'll need to have devscripts and fakeroot installed):

$ cd <var>/path/to/unvanquished</var>
$ fakeroot dpkg-buildpackage -b -uc
$ sudo dpkg -i <var>../unvanquished_*.deb</var>

Once in <code>ccmake</code>, use the following keys:

* Press {{Hotkey|c}} to configure. If an error occurs during this phase, make note of it and press {{Hotkey|e}} to dismiss it.
* Use the up and down arrow keys to navigate the compilation options.
* Press {{Hotkey|Enter}} to enable or disable boolean options (i.e., on/off) or to edit textual options.
** Press {{Hotkey|Esc}} when editing a textual option to cancel the change.

Once you have finished the configuration process, press {{Hotkey|C}} again, then {{Hotkey|G}} to generate the makefile.

====Using cmake-qt-gui (graphical front-end)====

This graphical front end for cmake has its own package you must install:

=====Debian/Ubuntu=====

$ sudo apt-get install cmake-qt-gui

=====Gentoo=====

With the '''qt4''' USE flag enabled:

$ emerge cmake

Once installed, run with <code>cmake-gui</code>.

[[Image:Cmake-qt-gui.png|thumb]]

# Set the path where you have the source code downloaded.
# Set the path where you would like to build the engine. This may be the same directory if you wish.
# Click 'Configure'.
# Click 'Generate'.

====Unnecessary libraries====

Regardless of which front-end to cmake you use, you may want to disable some libraries that are not strictly necessary:

* <code>USE_BREAKPAD</code> — Disabling this will cause the game to not produce crashdumps on failure.
* <code>USE_CURSES</code> — Disabling this will cause the external (not in-game) console to not use curses; it will not be scrollable and will be similar to the console in the original Tremulous. This does in no way affect gameplay.
* <code>USE_GEOIP</code> — Disabling this will make the game unable to locate players from their ip address.

===Compiling===

$ cd <var>path/to/unvanquished/build</var>
$ make -j4

The <code>-j</code> switch to make allows you to speed up the compilation process by running it in multiple threads; set the number following this to the number of cores your processor(s) have.

==Acquiring the Game Files==

===Acquiring mandatory game files===

The game files are not in the Git repository, and must be downloaded separately. They must be saved to the [[Running_the_game#Data_locations|data location]] for your system.

Linux users may use the <code>download-pk3.sh</code> script that is distributed with the source code, which requires that curl be installed:

$ cd path/to/unvanquished/build
$ mkdir -p pkg
$ ../download-pk3.sh pkg

Otherwise, the set of necessary packages can be extracted from the [https://github.com/Unvanquished/Unvanquished/releases latest release], or downloaded a la carte from the [http://dl.unvanquished.net/pkg/ package index].

==Errors==

===The C Compiler is not able to compile a simple test program===

When attempting to generate a solution for Xcode CMake fails with the following error
-- Check for working C compiler using: Xcode -- broken
CMake Error at /Applications/CMake 2.8-8.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
The C compiler "/usr/bin/gcc" is not able to compile a simple test program.

It fails with the following output:

Change Dir: /Users/danielmaloney/Documents/Unvanquished/build-xcode/CMakeFiles/CMakeTmp

Run Build Command:/Applications/CMake\ 2.8-8.app/Contents/bin/cmakexbuild
-project CMAKE_TRY_COMPILE.xcodeproj build -target
cmTryCompileExec1400153232 -configuration Debug

Error: No developer directory found at /Developer. Run
/usr/bin/xcode-select to update the developer directory path.

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:19 (project)

This is due to Xcode 4.3 having a different directory structure to previous versions. Simply running the following command will correct this error:
sudo /usr/bin/xcode-select -switch /Applications/Xcode.app/Contents/Developer/

Server/Running

2021-02-03T05:24:34Z

Derek: added how to become an admin

Servers can be quickly setup over LAN by starting a match in-game, however this is not as powerful or efficient as running a dedicated server separately.

= Starting the Server =

Check this Forum post on how to set one up: https://forums.unvanquished.net/viewtopic.php?f=8&t=2195&p=18178&hilit=set+up+server#p18178
Default binary directory is called <code>libpath</code>, default data directory is called <code>basepath</code>, default user directory is called <code>homepath</code>, optional package directory is called <code>pakpath</code>.

The executable <code>daemonded</code> ('daemon dedicated') should be included with your installation.
{{Game Locations}}

So, if you need to be explicit on every path, you can do that:

<code>./daemonded -libpath /usr/lib/unvanquished -basepath /var/lib/unvanquished -homepath ${HOME}/.local/share/unvanquished -pakpath /var/www/unvanquished/pkg</code>

The <code>pakpath</code> is an optional path for game packages, you can add as many as you want.

Quick list of useful options:
* <code>-curses</code> — enabled ncurses console interface (default behavior is to disable it so messages remain on-screen after crashes).
* <code>+map mapname</code> — without a map the server will kill itself

=Netiquette=
Unvanquished is currently a small community. Please don't aim to create a server in order to only compete for players — division of players will disallow larger matches.

=Specs=
Port <code>27960</code> (default Quake Ⅲ Arena server port), on udp only.

= Configuration and Operation =

To discover more commands than are listed here: type a first letter (eg 'g') and press '''Tab''' to list available options starting with that letter. If you are in a terminal: '''Shift+Page Up''' allows you to scroll and the opposite for down.

* [[Server/Map Rotation|Server/Map Rotation]]
* [[Server/Map layouts|Server/Map layouts]] — default building locations

==Server Config File==
Here is the template for the server config: {{SourceFile|dist/configs/config/server.cfg}}.
{| class="wikitable"
! Platform
! Location
|-
| Linux
| ~/.local/share/unvanquished/config
|-
| Windows
| C:\Users\*username*\Documents\My games\Unvanquished\config <--may be depreciated
|-
| macOS
| ???
|-
|}

Ensure your server mode is not set to '2' unless you want your server to be listed for other players.

# Server mode
# 0 - local server
# 1 - LAN server
# 2 - public server

Public servers will want to set sv_hostname to a non-default value

==Commands==
Please add common and useful commands, not every one

{| class="wikitable sortable"
|-
! Command
! Description
|-
| devmap
| Loads a map with <code>sv_cheats</code> enabled. <code>sv_cheats</code> cannot otherwise be changed during play
|-
| listadmins
| List current admins in-game
|-
| listlayouts
| List available layouts (for this map?)
|-
| listplayers
| List current players in-game
|-
| listmaps
| List maps available to the server
|-
|}

==Cvars==
Please add common and useful cvars, not every one

{| class="wikitable"
|-
! Cvar
! Description
|-
| g_dretchPunt
| Allow dretches to be pushes out of the way by bigger aliens?{{Verify}}
|-
| g_friendlyfire
| Allows players to hurt their team
|-
| g_gravity
| Gravity.
|-
| sv_maxclients
| Maximum number of joined players{{Verify}}
|-
| g_maxGameClients
| Maximum number of players in teams (ignoring spectators){{Verify}}
|-
| g_motd
| Message displayed to joining players (Message Of The Day)
|-
| g_needpass
| Whether passwords are enforced on game entry or not
|-
| g_password
| Password to enter game
|-
|}

==(wip) A short tutorial on how to make a dedicated server.(14/10/2017)==

====Linux:====
Tip: Please see [http://linuxcommand.org/learning_the_shell.php linux commands tutorial] and [http://www.openvim.com/ vim tutorial] (really recomended)
Install vim:
<code>sudo apt install vim -y</code>

#Download the latest update by running this command in the folder that you want to be your game directory: <code>wget https://github.com/Unvanquished/Unvanquished/releases/download/v0.51.1/unvanquished_0.51.1.zip</code>.
#Unzip the file by running: <code>unzip unvanquished_0.51.1.zip</code> (if you don't already have unzip you can get it by running <code>apt-get install unzip</code>)
#Create a folder called config in the unvanquished folder using the <code>mkdir config</code> command.
#create 2 cfg files inside the config folder using <code>touch server.cfg</code> and <code>touch maprotation.cfg</code>
#Create a script to ease starting a server:

Run: touch startsv.sh
Then give it proper perms: chmod +x startsv.sh

Edit it: vim startsv.sh

Press <code>i</code> to enter in insert mode, copy & paste this:
./daemonded -homepath ./ +exec server.cfg
Press esc and type <code>:wq</code> to save the file.

Go to <code>config/server.cfg</code> and edit it (<code>vim server.cfg</code>)
Copy & paste this, and edit to match your preferences: {{SourceFile|dist/configs/config/server.cfg}}

Run the server with <code>./startsv.sh</code>

Want to keep the server after closing a ssh session? See this [https://www.digitalocean.com/community/tutorials/how-to-install-and-use-screen-on-an-ubuntu-cloud-server tutorial]

====Windows:====
#Download the latest version of unvanquished from the GitHub releases page [https://github.com/Unvanquished/Unvanquished/releases here].
#Unzip the file into the directory you want your server to run from.
#Create a folder inside that directory called config

===IN-game Server Config===
To make yourself an in-game admin

enter the game make sure you've made your in-game name by pressing esc > player

then type /register, it should say your account is now registered. next type in /listplayers, and log your number

then go into the console and type /setlevel (your number) (your level)

here are the levels

[level]
level = 5
name = ^1Server Operator
flags = ALLFLAGS -IMMUTABLE -INCOGNITO

[level]
level = 4
name = ^3Senior Admin
flags = listplayers admintest adminhelp time putteam spec999 warn kick mute showbans ban namelog buildlog ADMINCHAT register unregister l0 l1

[level]
level = 3
name = ^2Junior Admin
flags = listplayers admintest adminhelp time putteam spec999 warn kick mute ADMINCHAT buildlog register unregister l0 l1

[level]
level = 2
name = ^6Team Manager
flags = listplayers admintest adminhelp time putteam spec999 register unregister

[level]
level = 1
name = ^5Server Regular
flags = listplayers admintest adminhelp time register unregister

[level]
level = 0
name = ^4Unknown Player
flags = listplayers admintest adminhelp time register

Install and play

2021-02-01T10:31:14Z

Derek: added a download source

== Getting the game ==

Most users will want to visit the [https://unvanquished.net/download main download page] on our website.

You can get your device specific download on:
* [https://gamejolt.com/games/Unvanquished/571330 Game Jolt page]
Alternatively you can download universal zip on:
* [https://github.com/Unvanquished/Unvanquished/releases GitHub release page]
* [https://sourceforge.net/projects/unvanquished/files/Universal_Zip SourceForge.net file browser]
* [https://www.indiedb.com/games/unvanquished/downloads IndieDB download page]

See [[Coding]] for tips and guides on compiling.

== Running and Configuration ==
* Using the [[console]]
* [[Colours]] in names and chat
* [[Runtime options]] for eg screen resolution, game data location
* [[Creating custom keybinds]]
* [[Optimisations]]

== Bugs ==
Unvanquished has lots of them. We have an extensive [https://github.com/Unvanquished/Unvanquished/issues bugtracker] that we invite you to add your bugs to.

* Have a read of our [[Bug reporting]] page for tips on making effective reports
* Search the bugtracker for bugs similar to yours before adding a new one.
* Some of the tips on the [[Testing]] page may be useful.

== Getting in Contact ==
The two best ways to get in contact with other community members are:
* through the [https://forums.unvanquished.net forums]
* over [[IRC]]
On the [[IRC]] page are links to web-clients if you don't have an IRC client already installed.

== Running Servers ==
* [[Server/Running|Running a server]]
** [[Server/Map layouts|Map layouts]] — default building locations
** [[Server/Map Rotation|Map Rotation]]
** [[Server/Bot skill|Bot skill]]

Call Outs

2021-01-31T18:52:20Z

Derek: added new-def to Level Access

Callouts in Unvanquished are crucial. These were made by us for personal use and skill improvement.

What is a Call Out?

According to the Oxford Dictionary "a statement drawing critical attention to someone's unacceptable actions or behaviour."

A Call Out is a way to drag attention to a location ex: Humans are pushing Ventilation. here we can see the noun is "Humans" the verb is "Pushing" meaning that they are trying to take control of the region and the Call Out is "Ventilation" this system helps communication in the game grow and also enables the player to simplify the names of Places that are tightly woven. for example "Ventilation" is the room "Ventilation" and "Ventilation shaft" combined because we know that if a human is pushing into Ventilation they have to be inside the shaft to enter.

# Antares

Storage - Alien Spawn base https://i.ibb.co/G5W3w1m/Storage.jpg

Storage East - Rightside of Storage (Ventilation) (This term is mainly used to tell that people are coming in through that enterance rather than stating people are in ventilation and you are holding them back - https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/knSDjsbhucBqQpgCWFEablqh

Ventilation [Can be called shaft] (Usage: Humans Pushing Ventilation)

Processing-

Processing can be split into three parts.

Processing-Vent or Processing-V (The Part of Processing that is closest to the Ventilation area)

Processing (Middle Region of Processing)

Processing-C or Processing-Corridor (More on this later).

This is a Diagram of what I've said https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/NjMzHTzYdMehVYiwsmYiBtmI

Processing-C is the Processing Corridor. which links into the Human Base.

Human Base will just be called Human Base instead of the room name. There fore Level Access will mean the Room across Processing-C which is close to Main Corridor.

Call Outs

2021-01-31T18:47:38Z

Derek:

Callouts in Unvanquished are crucial. These were made by us for personal use and skill improvement.

What is a Call Out?

According to the Oxford Dictionary "a statement drawing critical attention to someone's unacceptable actions or behaviour."

A Call Out is a way to drag attention to a location ex: Humans are pushing Ventilation. here we can see the noun is "Humans" the verb is "Pushing" meaning that they are trying to take control of the region and the Call Out is "Ventilation" this system helps communication in the game grow and also enables the player to simplify the names of Places that are tightly woven. for example "Ventilation" is the room "Ventilation" and "Ventilation shaft" combined because we know that if a human is pushing into Ventilation they have to be inside the shaft to enter.

# Antares

Storage - Alien Spawn base https://i.ibb.co/G5W3w1m/Storage.jpg

Storage East - Rightside of Storage (Ventilation) (This term is mainly used to tell that people are coming in through that enterance rather than stating people are in ventilation and you are holding them back - https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/knSDjsbhucBqQpgCWFEablqh

Ventilation [Can be called shaft] (Usage: Humans Pushing Ventilation)

Processing-

Proccesing can be split into three parts.

Proccessing-Vent or Proccessing-V (The Part of Processing that is closest to the Ventilation area)

Processing (Middle Region of Processing)

Proccessing-C or Proccessing-Corridor (More on this later).

This is a Diagram of what I've said https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/NjMzHTzYdMehVYiwsmYiBtmI

Call Outs

2021-01-31T17:42:48Z

Derek: Due to afontain's request of adding a definition of Callouts: "Definitely add a definition for "call outs" in the wiki page, because I have no idea what you mean"

Call Outs

2021-01-31T15:48:25Z

Derek: Created page with "Callouts in Unvanquished are crucial. These were made by us for personal use and skill improvement. # Antares Storage - Alien Spawn base https://i.ibb.co/G5W3w1m/Storage.j..."

Callouts in Unvanquished are crucial. These were made by us for personal use and skill improvement.

# Antares

Storage - Alien Spawn base https://i.ibb.co/G5W3w1m/Storage.jpg

Storage East - Rightside of Storage (Ventilation) (This term is mainly used to tell that people are coming in through that enterance rather than stating people are in ventilation and you are holding them back - https://matrix-client.matrix.org/_matrix/media/r0/download/matrix.org/knSDjsbhucBqQpgCWFEablqh

Ventilation [Can be called shaft] (Usage: Humans Pushing

Drill

2021-01-10T11:31:55Z

Derek:

{{InfoBoxStart | name = Drill | image = Drill.png | caption = Why hasn't the floor collapsed yet?}}
{{InfoRow | caption = Cost | value = 0 Credits }}
{{InfoRow | caption = Unlock | value = - }}
{{InfoRow | caption = Health | value = 200 }}
{{InfoRow | caption = Build Time | value = 10 seconds }}
{{InfoBoxEnd}}

Drills the ground for materials.

== Tips ==

* Spread them apart for maximum mining efficiency. Keep in mind that two drills right next to each other will mine out less material than a single drill.

* Defend your drills well. If a drill is destroyed, you'll lose a portion of your stored material.

* If you feel a forward base with a drill in it isn't going to last for much longer, deconstruct the drill to prevent the loss of material.

* Drills mine out less and less material as the game progresses. Build them as early as possible.

[[Category:Humans]]

Building gameplay

2021-01-08T16:02:12Z

Derek: Grammar, and fixed wording

= Building gameplay =

Unvanquished is a game which adds RTS (Real Time Strategy) elements on top of relatively classic (despite the Alien's mechanisms) FPS (First Person Shooter) game-play.
It is derived from tremulous, which also had those RTS elements, but tried to improve by changing a lot the gameplay.

So, this page is for both tremulous' veterans and complete newcomers to Unvanquished. It aims at explaining the basics of how resources are gathered and spent, and what every player should know, without covering advanced base creation tips.

== Momentum ==

Completion of buildings increase a team's momentum.
Deconstructing a building reduces a team's momentum.

Destroying an enemy building increase your team's momentum and reduces enemy's momentum.

== Build Points ==

Each team have a shared (by the team) amount of Build Points (BPs).

BPs are gathered by building [[Drill|Drills]] for humans or [[Leech|Leeches]] for aliens.

Each gathering building of a team allows the team to gather resources in an area.
Resource areas of a team are merged.
Area "conflicting" with enemy team are shared with other team, giving both team half the volume.
Volume is multiplied by a specific value (as of 0.51, a gatherer at 100% efficiency provides 50 BPs) and that represents the amount of BPs available to the team.

When a team looses a gathering building, it looses the area and thus, BPs provided by said area are *lost*. This is important because without enough BPs, buildings except [[Overmind]], [[Reactor]], [[Egg]] or [[Telenode]] will be disabled, making bases defenseless.

Starting the construction of a building immediately spends the corresponding amount of the team's BPs stock.

Loosing a building makes the team which owned it *slowly* recovering build points (several minutes per BP).

== Basic building hints ==

Building efficient bases and outposts is very different depending on the team. Humans and Aliens having very different strategies.
I will try to explain the most basic hints here.

=== Humans ===

==== Outposts ====

Complete outpost (also called forward base), usually require at least 3 buildings:

* an [[Armoury]]
* a [[Telenode]]
* a [[Medistation]]

This imply a total cost of 26 BPs, which is a rather high cost, so it's usually better to first build defenses to cover while building.

==== Defensive build ====

Keep in mind that turrets need to rotate toward their target to start firing. This means a lone defense will be of little use, especially against a skilled alien player.

Defensive buildings will not fire if that would imply damage allied structures or players.

[[Machinegun_Turret|Machinegun Turrets]] have a short range.

[[Rocket_Pod|Rocket Pods]] have a minimum range: if enemy reach it, it's good for the scrapyard.

=== Alien ===

First and most important hint for aliens: your base is weak. Don't let any human find or enter it.
When you finally unlock advanced granger, do not hesitate to move as many buildings as possible on walls and roofs, if only to avoid grenades and flamers destroying everything in the blink of an overmind's eye.

Overmind can not, though, be built on walls and roofs.

==== Outposts ====

Aliens only requires 2 buildings to build an outpost: and [[Egg]] and, if evolved enough, a [[Booster]]. This allows aliens to spread bases everywhere and keep putting pressure on enemy's base.

Those outposts will also provide faster healing: x2 for any building, x4 for booster, which also poisons your weapons for 30s.

Those buildings have cost, though. Unlike [[Leech]], which still provide the healing bonus.

==== Defensive build ====

[[Barricade|Barricades]] are defensive and don't attack, humans can fly or jump over them. They also have a rather high cost, thus are mostly useful behind small doors.
They can't be built on walls and roofs.

[[Trapper]] can immobilize enemy, but for that, it needs to reach enemy, which means it can only be built in few places.

Clans

2021-01-08T09:50:20Z

Derek: Grammar and punctuation

Clans are groups inside the game. Clan tags are usually used in tournaments to identify players.

To add your clan tag go to menu>player and click on "nickname" then put <code>^1[Clan-Tag](another colour)your name</code>

= Current in-game clans: =

The first and only clan as of now is:

=== KING ===

King was founded by Derek and has two members:

# Derek
# RNGLatico

----
///Put other clans here and their description and list players

Server/Running

2021-01-08T00:22:58Z

Derek: Added server config template

Servers can be quickly setup over LAN by starting a match in-game, however this is not as powerful or efficient as running a dedicated server separately.

= Starting the Server =
Default binary directory is called <code>libpath</code>, default data directory is called <code>basepath</code>, default user directory is called <code>homepath</code>, optional package directory is called <code>pakpath</code>.

The executable <code>daemonded</code> ('daemon dedicated') should be included with your installation.
{{Game Locations}}

So, if you need to be explicit on every path, you can do that:

<code>./daemonded -libpath /usr/lib/unvanquished -basepath /var/lib/unvanquished -homepath ${HOME}/.local/share/unvanquished -pakpath /var/www/unvanquished/pkg</code>

The <code>pakpath</code> is an optional path for game packages, you can add as many as you want.

Quick list of useful options:
* <code>-curses</code> — enabled ncurses console interface (default behavior is to disable it so messages remain on-screen after crashes).
* <code>+map mapname</code> — without a map the server will kill itself

=Netiquette=
Unvanquished is currently a small community. Please don't aim to create a server in order to only compete for players — division of players will disallow larger matches.

=Specs=
Port <code>27960</code> (default Quake Ⅲ Arena server port), on udp only.

= Configuration and Operation =

To discover more commands than are listed here: type a first letter (eg 'g') and press '''Tab''' to list available options starting with that letter. If you are in a terminal: '''Shift+Page Up''' allows you to scroll and the opposite for down.

* [[Server/Map Rotation|Server/Map Rotation]]
* [[Server/Map layouts|Server/Map layouts]] — default building locations

==Server Config File==
Here is the template for the server config: https://github.com/Unvanquished/Unvanquished/blob/master/dist/configs/config/server.cfg

{| class="wikitable"
! Platform
! Location
|-
| Linux
| ~/.local/share/unvanquished/config
|-
| Windows
| C:\Users\*username*\Documents\My games\Unvanquished\config <--may be depreciated
|-
| macOS
| ???
|-
|}

Ensure your server mode is not set to '2' unless you want your server to be listed for other players.

# Server mode
# 0 - local server
# 1 - LAN server
# 2 - public server

Public servers will want to set sv_hostname to a non-default value

==Commands==
Please add common and useful commands, not every one

{| class="wikitable sortable"
|-
! Command
! Description
|-
| devmap
| Loads a map with <code>sv_cheats</code> enabled. <code>sv_cheats</code> cannot otherwise be changed during play
|-
| listadmins
| List current admins in-game
|-
| listlayouts
| List available layouts (for this map?)
|-
| listplayers
| List current players in-game
|-
| listmaps
| List maps available to the server
|-
|}

==Cvars==
Please add common and useful cvars, not every one

{| class="wikitable"
|-
! Cvar
! Description
|-
| g_dretchPunt
| Allow dretches to be pushes out of the way by bigger aliens?{{Verify}}
|-
| g_friendlyfire
| Allows players to hurt their team
|-
| g_gravity
| Gravity.
|-
| sv_maxclients
| Maximum number of joined players{{Verify}}
|-
| g_maxGameClients
| Maximum number of players in teams (ignoring spectators){{Verify}}
|-
| g_motd
| Message displayed to joining players (Message Of The Day)
|-
| g_needpass
| Whether passwords are enforced on game entry or not
|-
| g_password
| Password to enter game
|-
|}

==(wip) A short tutorial on how to make a dedicated server.(14/10/2017)==

====Linux:====
Tip: Please see [http://linuxcommand.org/learning_the_shell.php linux commands tutorial] and [http://www.openvim.com/ vim tutorial] (really recomended)
Install vim:
<code>sudo apt install vim -y</code>

#Download the latest update by running this command in the folder that you want to be your game directory: <code>wget https://github.com/Unvanquished/Unvanquished/releases/download/v0.51.1/unvanquished_0.51.1.zip</code>.
#Unzip the file by running: <code>unzip unvanquished_0.51.1.zip</code> (if you don't already have unzip you can get it by running <code>apt-get install unzip</code>)
#Create a folder called config in the unvanquished folder using the <code>mkdir config</code> command.
#create 2 cfg files inside the config folder using <code>touch server.cfg</code> and <code>touch maprotation.cfg</code>
#Create a script to ease starting a server:

Run: touch startsv.sh
Then give it proper perms: chmod +x startsv.sh

Edit it: vim startsv.sh

Press <code>i</code> to enter in insert mode, copy & paste this:
./daemonded -homepath ./ +exec server.cfg
Press esc and type <code>:wq</code> to save the file.

Go to <code>config/server.cfg</code> and edit it (<code>vim server.cfg</code>)
Copy & paste this, and edit to match your preferences: {{SourceFile|dist/configs/config/server.cfg}}

Run the server with <code>./startsv.sh</code>

Want to keep the server after closing a ssh session? See this [https://www.digitalocean.com/community/tutorials/how-to-install-and-use-screen-on-an-ubuntu-cloud-server tutorial]

====Windows:====
#Download the latest version of unvanquished from the GitHub releases page [https://github.com/Unvanquished/Unvanquished/releases here].
#Unzip the file into the directory you want your server to run from.
#Create a folder inside that directory called config

Clans

2021-01-07T22:14:16Z

Derek:

Clans are groups inside the game clan tags are usually used in tournaments to identify players

to add your clan tag go to menu>player and click on nickname then put <code>^1[Clan-Tag](anyother colour)your name</code>

Current in-game clans:

The first and only clan as of now is:

'''KING'''

King was founded by Derek and has two members
Description:

1. Derek
2. RNGLatico

----
///Put other clans here and their description and list players

Clans

2021-01-07T22:11:50Z

Derek: Created page with "Clans are groups inside the game clan tags are usually used in tournaments to identify players to add your clan tag go to menu>player and click on nickname then put ``^1[Cla..."

Clans are groups inside the game clan tags are usually used in tournaments to identify players

to add your clan tag go to menu>player and click on nickname then put ``^1[Clan-Tag](anyother colour)your name``

Current in-game clans:

The first and only clan as of now is:

'''KING'''

King was founded by Derek and has two members
Description:

1. Derek
2. RNGLatico

----
///Put other clans here and their description and list players

Spectating

2021-01-05T13:41:27Z

Derek:

Spectating is the act of viewing someone who is playing. currently the keybinds aren't set but to set it you just need to type this in the console whilst playing

/bind (yourkey) followprev
/bind (yourkey) follownext

and now you can spectate, to change the keys just run the command(s) and it will overwrite it

Spectating

2021-01-05T13:41:17Z

Derek:

Spectating is the act of viewing someone who is playing. currently the keybinds aren't set but to set it you just need to type this in the console whilst playing

/bind (yourkey) followprev /n
/bind (yourkey) follownext

and now you can spectate, to change the keys just run the command(s) and it will overwrite it

Spectating

2021-01-05T13:40:42Z

Derek: How to enable spectate