--- /dev/null
+*.md eol=lf
----\r
-title: Compiling Xonotic releases and autobuilds\r
----\r
-\r
-This page is about compiling the sources included in [stable releases](https://xonotic.org/download) and [beta autobuilds](Autobuilds), which you may want to do after [updating by rsync](https://xonotic.org/download#upgrading). \r
-For git builds and development tools please see [Repository_Access](Repository_Access) and [Git HOWTO](Git).\r
-\r
-The release Makefile is the most convenient way to compile for alternative CPU architectures, or to get a build fully optimised for a recent x86 CPU (the official binaries are generic x86_64). It would also allow you to run Xonotic on an OS too old to be supported by official binaries.\r
-\r
-To this end the Makefile default settings enable all optimisations that can be used on your current CPU without causing bugs, and compile using all available CPU threads.\r
-\r
-The engine builds will be dynamically linked except for d0_blind_id which is statically linked to ensure reliable player ID support and because OS distributions don't ship this library.\r
-\r
-### Commands\r
-\r
-Invoking `make` or `make help` in the Xonotic directory will print the supported targets and current config. \r
-\r
-**Most people will want `make update-stable client` or `make update-beta client`**\r
-\r
-## System package dependencies\r
-### Debian\r
-Build (client): `build-essential automake libtool libgmp-dev libjpeg-dev libsdl2-dev` \r
-Build (server): `build-essential automake libtool libgmp-dev libjpeg-dev zlib1g-dev` \r
-Runtime (client): `curl rsync libpng16-16 libfreetype6 libvorbisfile3` \r
-Runtime (server): `curl rsync libpng16-16` \r
+---
+title: Compiling Xonotic releases and autobuilds
+---
+
+This page is about compiling the sources included in [stable releases](https://xonotic.org/download) and [beta autobuilds](Autobuilds), which you may want to do after [updating by rsync](https://xonotic.org/download#upgrading).
+For git builds and development tools please see [Repository_Access](Repository_Access) and [Git HOWTO](Git).
+
+The release Makefile is the most convenient way to compile for alternative CPU architectures, or to get a build fully optimised for a recent x86 CPU (the official binaries are generic x86_64). It would also allow you to run Xonotic on an OS too old to be supported by official binaries.
+
+To this end the Makefile default settings enable all optimisations that can be used on your current CPU without causing bugs, and compile using all available CPU threads.
+
+The engine builds will be dynamically linked except for d0_blind_id which is statically linked to ensure reliable player ID support and because OS distributions don't ship this library.
+
+### Commands
+
+Invoking `make` or `make help` in the Xonotic directory will print the supported targets and current config.
+
+**Most people will want `make update-stable client` or `make update-beta client`**
+
+## System package dependencies
+### Debian
+Build (client): `build-essential automake libtool libgmp-dev libjpeg-dev libsdl2-dev`
+Build (server): `build-essential automake libtool libgmp-dev libjpeg-dev zlib1g-dev`
+Runtime (client): `curl rsync libpng16-16 libfreetype6 libvorbisfile3`
+Runtime (server): `curl rsync libpng16-16`
----\r
-title: Xonotic official Wiki\r
----\r
-Welcome to the Xonotic Wiki. If you wish to contribute, see [Editing](Editing).\r
-\r
-- You are looking at the [official wiki](https://gitlab.com/xonotic/xonotic/wikis/home) or its [mirror](https://github.com/xonotic/xonotic/wiki).\r
- - [Unofficial wiki](http://xonotic.wikia.com/wiki/Xonotic_Wiki) may contain dated but still helpful information.\r
-- [Website](http://xonotic.org)\r
- - [Forums](http://forums.xonotic.org) are a lively place for Xonotic players to discuss anything.\r
- - [Xonotic game stats](http://stats.xonotic.org/) show useful statistics information about servers, players, scores, maps, etc.\r
-- [Matrix and IRC channels](Chat-Rooms) are where most players ask/answer questions, exchange ideas, organize game events, etc. in **real time**. You can even chat with players in the game.\r
-- [Discord](Chat-Rooms#discord): there is also an unofficial Discord server that serves more or less the same purpose as the IRC channels.\r
-- [Facebook](https://www.facebook.com/xonotic/)\r
-- [Twitter](https://twitter.com/xonotic)\r
-\r
-## Gameplay\r
-\r
-### Tutorials\r
-- [HALOGENE’S NEWBIE CORNER](https://xonotic.org/guide/) has rich information for beginners. **Must read!** You will enjoy the game more!\r
-- [Overkill Tutorial](https://xonotic.org/okguide/)\r
-- [Creating bot waypoints](https://gitlab.com/xonotic/xonotic/-/wikis/Creating-bot-waypoints)\r
-\r
-### Unofficial map repositories\r
-- [xonotic.fps.gratis](http://xonotic.fps.gratis/) (or [dl.xonotic.fps.gratis](http://dl.xonotic.fps.gratis/) for a simple list that loads faster) - Run by [-z-](https://github.com/z/)/[detrate](https://gitlab.com/detrate).\r
-- [gnome.xonotic.in.ua](http://gnome.xonotic.in.ua/)\r
-- [xon.recombi.net](http://xon.recombi.net/) (or [xon.recombi.net/dl](http://xon.recombi.net/dl/) for a simple list that loads faster) - Has content from both [fps.gratis](http://xonotic.fps.gratis/) and [gnome](http://gnome.xonotic.in.ua/), [fps.gratis](http://xonotic.fps.gratis/) has precedence in case of conflict.\r
-- [naitlee.github.io/map-repo-poc](https://naitlee.github.io/map-repo-poc/) - Stylized Xonotic map repository. Better performance. Run by [NaitLee](https://github.com/NaitLee).\r
-\r
-### Unofficial Web-based Server Lists\r
-- [dpmaster.deathmask.net](http://dpmaster.deathmask.net/?game=xonotic)\r
- - one of the 2 active master servers, shows servers from only one master at a time (itself by default)\r
- - web interface not open source\r
- - see page source for list of URL parameters - e.g. [`master=dpmaster.tchr.no`](http://dpmaster.deathmask.net/?game=xonotic&master=dpmaster.tchr.no) to view the other master (which has no web interface)\r
-- [arena.sh/xo](https://arena.sh/xo/) - run by *nmc* on discord\r
-- [xonotic.lifeisabug.com](https://xonotic.lifeisabug.com/) - run by *incognico* on discord\r
-\r
-### Game Mechanics\r
-- [Maps](Maps)\r
-- [Players](Players)\r
-- [Items](Items)\r
-- [Vehicles](Vehicles)\r
-- [Weapons](Weapons)\r
-- [Monsters](Monsters)\r
-\r
-### Game Modes (or Game Types)\r
-In Xonotic, game modes and game types mean the same thing -- different modes/types have different goals to achieve in a game.\r
-\r
-The following modes are the more popular ones:\r
-\r
-- [Capture the Flag](Capture-the-Flag)\r
-- [Clan Arena](Clan-Arena)\r
-- [Deathmatch](Deathmatch)\r
-- [Duel](Duel)\r
-- [Freeze Tag](Freeze-Tag)\r
-- [Keepaway](Keepaway)\r
-- [Key Hunt](Key-Hunt)\r
-- [Mayhem](Mayhem)\r
-- [Race CTS](Race-CTS)\r
-- [Team Deathmatch](Team-Deathmatch)\r
-- [Team Mayhem](Team-Mayhem)\r
-- [Team Keepaway](Team-Keepaway)\r
-\r
-\r
-The following modes are available, although slightly less common than the above:\r
-\r
-- [Assault](Assault)\r
-- [Domination](Domination)\r
-- [Last Man Standing](Last-Man-Standing)\r
-- [Nexball](Nexball)\r
-- [Onslaught](Onslaught)\r
-- [Race](Race)\r
-- [Survival](Survival)\r
-\r
-Old/experimental modes:\r
-\r
-- [Invasion](Invasion) (experimental)\r
-- [Arena](Arena) (removed)\r
-\r
-The following modes are mods:\r
-- [Murder in Megaerebus Manor](Murder-in-Megaerebus-Manor)\r
-\r
-### Standard Mutators\r
-Mutators change the configuration of the game play, e.g. how weapon appears, which special weapons are availabale, or the physics in the game. This is usually set by the game admins who set up games for other players. Standard Mutators are available in the game menu.\r
-\r
-Gameplay mutators:\r
-\r
-- [Dodging](Dodging)\r
-- [Touch Explode](Touch-Explode)\r
-- [Cloaked](Cloaked)\r
-- [Buffs](Buffs)\r
-- [Midair](Midair)\r
-- [Vampire](Vampire)\r
-- [Blood Loss](Blood-Loss)\r
-- [Low Gravity](Gravity)\r
-\r
-Weapon/item mutators:\r
-- [Grappling Hook](Grappling-Hook)\r
-- [Jetpack](Jetpack)\r
-- [Invincible Projectiles](Invincible-Projectiles)\r
-- [New Toys](new-toys)\r
-- [Rocket Flying](Rocket-Flying)\r
-- [Piñata](Pinata)\r
-- [Weapons Stay](Weapons-Stay)\r
-\r
-Arena mutators:\r
-- [Weapon Arena](Weapon-Arena)\r
-- [InstaGib](InstaGib)\r
-- [NIX](NIX)\r
-\r
-Other mutators:\r
-- [Nades](Nades)\r
-- [Offhand blaster](Offhand-blaster)\r
-- [Dynamic handicap](dynamic-handicap)\r
-- [Relics](Relics) (experimental)\r
-\r
-### [Special Servers](Special-Servers)\r
-\r
-### [Mods](Mods)\r
-- [SMB modpack (contains git dev guide about how is built)](SMB-modpack)\r
-- [BaI mod](BaI-mod)\r
-- [Fresh Meat Mod](Freesh-Meat-Mod)\r
-\r
-### Misc\r
-- [Autobuilds](Autobuilds)\r
-- [Compiling](Compiling)\r
-- [Privacy and Security](privacy-and-security)\r
-- [Handicap](handicap)\r
-- [Camera for demos explained](Demo-Camera)\r
-- [Capturing video clips and using the demo camera](Democapture)\r
-- [Xonotic Bot Orchestra](Xonotic-Bot-Orchestra)\r
-- [Impulse map](impulse-map)\r
-- [Console Tips & Tricks](https://forums.xonotic.org/showthread.php?tid=2987) - introduction to console scripting (cvars, aliases, hooks, conditions, RPN)\r
-- [Hardware Requirements](Hardware-Requirements)\r
-\r
-\r
-## Server Administration\r
-### Tutorials\r
-- [Local test server on GNU/Linux](local-test-server-on-gnu-linux)\r
-\r
-### Configuration\r
-- [Basic server configuration](basic-server-configuration)\r
-- [Custom server votes](custom-server-votes)\r
-- [Custom user directory](custom-user-directory)\r
-- [The `info` command](https://forums.xonotic.org/showthread.php?tid=7474&pid=81277#pid81277)\r
-- [Random start weapons](Random-start-weapons)\r
-- [Automatic map downloads](Automatic-map-downloads)\r
-- [Event logging](Event-logging)\r
-- [Score logging](Score-logging)\r
-\r
-### Moderation\r
-- [Moderation tools](Moderation-tools)\r
-\r
-### Troubleshooting\r
-- [Performance](https://forums.xonotic.org/showthread.php?tid=7374&pid=80938#pid80938)\r
-\r
-### External Tools\r
-- [Xonotic Map Manager](https://github.com/z/xonotic-map-manager)\r
-- [Xonotic Server Management Suite](https://github.com/z/xonotic-server-management-suite)\r
-\r
-## Development\r
-- [Repository Access: Compiling and maintaining a Xonotic git build](Repository_Access)\r
-- [Requesting Push Access and Contributing](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md)\r
-- [Git: HowTo and Repository Structure](Git)\r
-- [Licensing / Legal](Legal)\r
-\r
-### Programming\r
-- [Introduction to QuakeC](Introduction-to-QuakeC)\r
-- [DarkPlaces Wiki](DarkPlaces-Index)\r
-- [Writing your first mutator](writing-your-first-mutator)\r
-- [Tips for new developers](Programming-Tips)\r
-- [Programming QuakeC stuff in Xonotic\r
-](Programming-QuakeC-stuff-in-Xonotic)\r
-\r
-### [Translating](Translating)\r
-- [Translation website](https://www.transifex.com/team-xonotic/xonotic/dashboard/)\r
-- [Translation guidelines](Translation-guidelines)\r
- - [List of translation placeholders](List-of-translation-placeholders)\r
- - [List of color codes](List-of-color-codes)\r
- - [List of translation prefixes](List-of-translation-prefixes)\r
-- [How to test your translations](Test-your-translations)\r
-\r
-### [Modeling](Modeling)\r
-- [Textures know-how](Textures)\r
-- [Normal Maps know-how](Normal-Maps)\r
-- [.framegroups](framegroups) file (allow self playing animations) know-how\r
-- [.sounds](Voices-and-sounds) file (player model sounds) know-how\r
-- [How to compile dpm models](dpmodel)\r
-- [Weapon modeling system](Weaponsystem)\r
-- [Exporting a weapon for Xonotic](Exporting-a-weapon-for-Xonotic)\r
-- How to get an animated mesh from [Blender to DPM](Blender-to-DPM)\r
-- [Inter-Quake Model (IQM) Format](http://sauerbraten.org/iqm/)\r
-- [Player Model Spec](Player-Model-Spec)\r
-- [Blender to IQM](Blender-to-IQM)\r
-\r
-### Texturing\r
-- [Tutorial](https://web.archive.org/web/20140328060504/http://www.cgtextures.com/content.php?action=tutorials)\r
-- [Recovering detailed normals from photo textures](https://web.archive.org/web/20140730154028/http://www.cgtextures.com/content.php?action=tutorial&name=normalmap)\r
-- [Hard Surface Texture Painting](http://forums.cgsociety.org/showthread.php?t=373024)\r
-- Some [tips](http://forums.xonotic.org/showthread.php?tid=63&pid=445#pid445) by *FruitieX*\r
-- [Q3A Shader Manual](http://toolz.nexuizninjaz.com/shader/)\r
-\r
-### Effects and particles\r
-- [Effectinfo Scripting](Effectinfo-Scripting)\r
-\r
-### [Mapping](Mapping)\r
-- [Creating Maps](Creating-Maps)\r
-- [Mapper resources](Mapper-resources)\r
-\r
-### Arts & Media\r
-- [Artistic Style](Artistic-Style)\r
-- [Xonotic Logo](Logo)\r
-- [Music](Music)\r
- - [Music contributions](Music-contributions)\r
-- [Sound FX](Sound-FX)\r
- - [Sound FX contributions](Sound-FX-contributions)\r
-- Story Themes\r
- - [Close to home](Close-to-home)\r
- - [Tech Conglomerate](Tech-Conglomerate)\r
-\r
-### Campaigns\r
-- [Creating campaigns](Creating-campaigns)\r
-\r
-\r
-## Misc\r
-\r
-- [Archive](Archive)\r
-- [Gitlab Markdown Reference](https://gitlab.com/help/user/markdown.md) (for editing this wiki)\r
+---
+title: Xonotic official Wiki
+---
+Welcome to the Xonotic Wiki. If you wish to contribute, see [Editing](Editing).
+
+- You are looking at the [official wiki](https://gitlab.com/xonotic/xonotic/wikis/home) or its [mirror](https://github.com/xonotic/xonotic/wiki).
+ - [Unofficial wiki](http://xonotic.wikia.com/wiki/Xonotic_Wiki) may contain dated but still helpful information.
+- [Website](http://xonotic.org)
+ - [Forums](http://forums.xonotic.org) are a lively place for Xonotic players to discuss anything.
+ - [Xonotic game stats](http://stats.xonotic.org/) show useful statistics information about servers, players, scores, maps, etc.
+- [Matrix and IRC channels](Chat-Rooms) are where most players ask/answer questions, exchange ideas, organize game events, etc. in **real time**. You can even chat with players in the game.
+- [Discord](Chat-Rooms#discord): there is also an unofficial Discord server that serves more or less the same purpose as the IRC channels.
+- [Facebook](https://www.facebook.com/xonotic/)
+- [Twitter](https://twitter.com/xonotic)
+
+## Gameplay
+
+### Tutorials
+- [HALOGENE’S NEWBIE CORNER](https://xonotic.org/guide/) has rich information for beginners. **Must read!** You will enjoy the game more!
+- [Overkill Tutorial](https://xonotic.org/okguide/)
+- [Creating bot waypoints](https://gitlab.com/xonotic/xonotic/-/wikis/Creating-bot-waypoints)
+
+### Unofficial map repositories
+- [xonotic.fps.gratis](http://xonotic.fps.gratis/) (or [dl.xonotic.fps.gratis](http://dl.xonotic.fps.gratis/) for a simple list that loads faster) - Run by [-z-](https://github.com/z/)/[detrate](https://gitlab.com/detrate).
+- [gnome.xonotic.in.ua](http://gnome.xonotic.in.ua/)
+- [xon.recombi.net](http://xon.recombi.net/) (or [xon.recombi.net/dl](http://xon.recombi.net/dl/) for a simple list that loads faster) - Has content from both [fps.gratis](http://xonotic.fps.gratis/) and [gnome](http://gnome.xonotic.in.ua/), [fps.gratis](http://xonotic.fps.gratis/) has precedence in case of conflict.
+- [naitlee.github.io/map-repo-poc](https://naitlee.github.io/map-repo-poc/) - Stylized Xonotic map repository. Better performance. Run by [NaitLee](https://github.com/NaitLee).
+
+### Unofficial Web-based Server Lists
+- [dpmaster.deathmask.net](http://dpmaster.deathmask.net/?game=xonotic)
+ - one of the 2 active master servers, shows servers from only one master at a time (itself by default)
+ - web interface not open source
+ - see page source for list of URL parameters - e.g. [`master=dpmaster.tchr.no`](http://dpmaster.deathmask.net/?game=xonotic&master=dpmaster.tchr.no) to view the other master (which has no web interface)
+- [arena.sh/xo](https://arena.sh/xo/) - run by *nmc* on discord
+- [xonotic.lifeisabug.com](https://xonotic.lifeisabug.com/) - run by *incognico* on discord
+
+### Game Mechanics
+- [Maps](Maps)
+- [Players](Players)
+- [Items](Items)
+- [Vehicles](Vehicles)
+- [Weapons](Weapons)
+- [Monsters](Monsters)
+
+### Game Modes (or Game Types)
+In Xonotic, game modes and game types mean the same thing -- different modes/types have different goals to achieve in a game.
+
+The following modes are the more popular ones:
+
+- [Capture the Flag](Capture-the-Flag)
+- [Clan Arena](Clan-Arena)
+- [Deathmatch](Deathmatch)
+- [Duel](Duel)
+- [Freeze Tag](Freeze-Tag)
+- [Keepaway](Keepaway)
+- [Key Hunt](Key-Hunt)
+- [Mayhem](Mayhem)
+- [Race CTS](Race-CTS)
+- [Team Deathmatch](Team-Deathmatch)
+- [Team Mayhem](Team-Mayhem)
+- [Team Keepaway](Team-Keepaway)
+
+
+The following modes are available, although slightly less common than the above:
+
+- [Assault](Assault)
+- [Domination](Domination)
+- [Last Man Standing](Last-Man-Standing)
+- [Nexball](Nexball)
+- [Onslaught](Onslaught)
+- [Race](Race)
+- [Survival](Survival)
+
+Old/experimental modes:
+
+- [Invasion](Invasion) (experimental)
+- [Arena](Arena) (removed)
+
+The following modes are mods:
+- [Murder in Megaerebus Manor](Murder-in-Megaerebus-Manor)
+
+### Standard Mutators
+Mutators change the configuration of the game play, e.g. how weapon appears, which special weapons are availabale, or the physics in the game. This is usually set by the game admins who set up games for other players. Standard Mutators are available in the game menu.
+
+Gameplay mutators:
+
+- [Dodging](Dodging)
+- [Touch Explode](Touch-Explode)
+- [Cloaked](Cloaked)
+- [Buffs](Buffs)
+- [Midair](Midair)
+- [Vampire](Vampire)
+- [Blood Loss](Blood-Loss)
+- [Low Gravity](Gravity)
+
+Weapon/item mutators:
+- [Grappling Hook](Grappling-Hook)
+- [Jetpack](Jetpack)
+- [Invincible Projectiles](Invincible-Projectiles)
+- [New Toys](new-toys)
+- [Rocket Flying](Rocket-Flying)
+- [Piñata](Pinata)
+- [Weapons Stay](Weapons-Stay)
+
+Arena mutators:
+- [Weapon Arena](Weapon-Arena)
+- [InstaGib](InstaGib)
+- [NIX](NIX)
+
+Other mutators:
+- [Nades](Nades)
+- [Offhand blaster](Offhand-blaster)
+- [Dynamic handicap](dynamic-handicap)
+- [Relics](Relics) (experimental)
+
+### [Special Servers](Special-Servers)
+
+### [Mods](Mods)
+- [SMB modpack (contains git dev guide about how is built)](SMB-modpack)
+- [BaI mod](BaI-mod)
+- [Fresh Meat Mod](Freesh-Meat-Mod)
+
+### Misc
+- [Autobuilds](Autobuilds)
+- [Compiling](Compiling)
+- [Privacy and Security](privacy-and-security)
+- [Handicap](handicap)
+- [Camera for demos explained](Demo-Camera)
+- [Capturing video clips and using the demo camera](Democapture)
+- [Xonotic Bot Orchestra](Xonotic-Bot-Orchestra)
+- [Impulse map](impulse-map)
+- [Console Tips & Tricks](https://forums.xonotic.org/showthread.php?tid=2987) - introduction to console scripting (cvars, aliases, hooks, conditions, RPN)
+- [Hardware Requirements](Hardware-Requirements)
+
+
+## Server Administration
+### Tutorials
+- [Local test server on GNU/Linux](local-test-server-on-gnu-linux)
+
+### Configuration
+- [Basic server configuration](basic-server-configuration)
+- [Custom server votes](custom-server-votes)
+- [Custom user directory](custom-user-directory)
+- [The `info` command](https://forums.xonotic.org/showthread.php?tid=7474&pid=81277#pid81277)
+- [Random start weapons](Random-start-weapons)
+- [Automatic map downloads](Automatic-map-downloads)
+- [Event logging](Event-logging)
+- [Score logging](Score-logging)
+
+### Moderation
+- [Moderation tools](Moderation-tools)
+
+### Troubleshooting
+- [Performance](https://forums.xonotic.org/showthread.php?tid=7374&pid=80938#pid80938)
+
+### External Tools
+- [Xonotic Map Manager](https://github.com/z/xonotic-map-manager)
+- [Xonotic Server Management Suite](https://github.com/z/xonotic-server-management-suite)
+
+## Development
+- [Repository Access: Compiling and maintaining a Xonotic git build](Repository_Access)
+- [Requesting Push Access and Contributing](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md)
+- [Git: HowTo and Repository Structure](Git)
+- [Licensing / Legal](Legal)
+
+### Programming
+- [Introduction to QuakeC](Introduction-to-QuakeC)
+- [DarkPlaces Wiki](DarkPlaces-Index)
+- [Writing your first mutator](writing-your-first-mutator)
+- [Tips for new developers](Programming-Tips)
+- [Programming QuakeC stuff in Xonotic
+](Programming-QuakeC-stuff-in-Xonotic)
+
+### [Translating](Translating)
+- [Translation website](https://www.transifex.com/team-xonotic/xonotic/dashboard/)
+- [Translation guidelines](Translation-guidelines)
+ - [List of translation placeholders](List-of-translation-placeholders)
+ - [List of color codes](List-of-color-codes)
+ - [List of translation prefixes](List-of-translation-prefixes)
+- [How to test your translations](Test-your-translations)
+
+### [Modeling](Modeling)
+- [Textures know-how](Textures)
+- [Normal Maps know-how](Normal-Maps)
+- [.framegroups](framegroups) file (allow self playing animations) know-how
+- [.sounds](Voices-and-sounds) file (player model sounds) know-how
+- [How to compile dpm models](dpmodel)
+- [Weapon modeling system](Weaponsystem)
+- [Exporting a weapon for Xonotic](Exporting-a-weapon-for-Xonotic)
+- How to get an animated mesh from [Blender to DPM](Blender-to-DPM)
+- [Inter-Quake Model (IQM) Format](http://sauerbraten.org/iqm/)
+- [Player Model Spec](Player-Model-Spec)
+- [Blender to IQM](Blender-to-IQM)
+
+### Texturing
+- [Tutorial](https://web.archive.org/web/20140328060504/http://www.cgtextures.com/content.php?action=tutorials)
+- [Recovering detailed normals from photo textures](https://web.archive.org/web/20140730154028/http://www.cgtextures.com/content.php?action=tutorial&name=normalmap)
+- [Hard Surface Texture Painting](http://forums.cgsociety.org/showthread.php?t=373024)
+- Some [tips](http://forums.xonotic.org/showthread.php?tid=63&pid=445#pid445) by *FruitieX*
+- [Q3A Shader Manual](http://toolz.nexuizninjaz.com/shader/)
+
+### Effects and particles
+- [Effectinfo Scripting](Effectinfo-Scripting)
+
+### [Mapping](Mapping)
+- [Creating Maps](Creating-Maps)
+- [Mapper resources](Mapper-resources)
+
+### Arts & Media
+- [Artistic Style](Artistic-Style)
+- [Xonotic Logo](Logo)
+- [Music](Music)
+ - [Music contributions](Music-contributions)
+- [Sound FX](Sound-FX)
+ - [Sound FX contributions](Sound-FX-contributions)
+- Story Themes
+ - [Close to home](Close-to-home)
+ - [Tech Conglomerate](Tech-Conglomerate)
+
+### Campaigns
+- [Creating campaigns](Creating-campaigns)
+
+
+## Misc
+
+- [Archive](Archive)
+- [Gitlab Markdown Reference](https://gitlab.com/help/user/markdown.md) (for editing this wiki)
-Mapping - Setup\r
-===============\r
-\r
-How to get your system all set up to start mapping\r
---------------------------------------------------\r
-\r
-### Step 1 (optional): Obtain the mapping support\r
-\r
-If you didn’t already, download the [mapping support zip](http://dl.xonotic.org/xonotic-0.8.6-mappingsupport.zip). \r
-This is only needed if you use an old version of NetRadiant or another map editor (including NetRadiant-custom, which is a fork of NetRadiant). \r
-If you download NetRadiant from the [NetRadiant website](https://netradiant.gitlab.io) or compile it from source, you can ignore the following steps and proceed to step 5 directly.\r
-\r
-### Step 2 (optional): Extract the zip\r
-\r
-Extract the zip archive using your favorite archiving tool\r
-\r
-### Step 3 (optional): Locate the folder for userdata\r
-\r
-Locate your userdata folder, note that this is **NOT** the install location. This is the place where Xonotic saves your userdata.\r
-\r
-- **Windows**: `C:\users\user\saved games\xonotic\data`\r
-- **Linux**: `~/.xonotic/data`\r
-- **Mac**: `~/Library/Application Support/xonotic/data`\r
-\r
-This folder has a similar layout as the game folder. Game wise these data folders are treated similarly, however, it is best to save your work in the userdata folder so that you don’t accidentally mess up your Xonotic install, or so that your work doesn’t get lost in an update.\r
-\r
-### Step 4 (optional): Move the mapping support pk3\r
-\r
-The mapping support zip contains a file called `xonotic-<timestamp>-maps-mapping.pk3`. Move this file to the userdata folder (see step 3), **NOT** `data/data`.\r
-This folder should also contain your `config.cfg`.\r
-\r
-### Step 5: Get NetRadiant working\r
-\r
-- **Windows**: Windows users can download a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/). \r
-The mapping support zip also contains a compiled version of NetRadiant in the `mapping` folder but while it may works, it is fairly outdated and lacks a lot of updates.\r
-- **Linux**: Linux users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/). \r
-(_NOTE: Archlinux users can also use the [netradiant-git](https://aur.archlinux.org/packages/netradiant-git/) PKGBUILD_)\r
-- **macOS**: macOS users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/). \r
-- **FreeBSD**: FreeBSD users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/). \r
-\r
-People wanting to compile NetRadiant themselves can look at the [NetRadiant Repository](https://gitlab.com/xonotic/netradiant).\r
-\r
-### Step 6: Set up NetRadiant\r
-\r
-When you first start up radiant it may ask where the engine path is. Simply point it to the Xonotic install location. Then NetRadiant should start and the lower right pane should have a list of texture packs. If there are no texture packs, then you may need the mapping support, please refer back to step 4.\r
-\r
-\<\< [Introduction](mapping-Introduction) | [NetRadiant](mapping-NetRadiant) \>\>\r
-\r
+Mapping - Setup
+===============
+
+How to get your system all set up to start mapping
+--------------------------------------------------
+
+### Step 1 (optional): Obtain the mapping support
+
+If you didn’t already, download the [mapping support zip](http://dl.xonotic.org/xonotic-0.8.6-mappingsupport.zip).
+This is only needed if you use an old version of NetRadiant or another map editor (including NetRadiant-custom, which is a fork of NetRadiant).
+If you download NetRadiant from the [NetRadiant website](https://netradiant.gitlab.io) or compile it from source, you can ignore the following steps and proceed to step 5 directly.
+
+### Step 2 (optional): Extract the zip
+
+Extract the zip archive using your favorite archiving tool
+
+### Step 3 (optional): Locate the folder for userdata
+
+Locate your userdata folder, note that this is **NOT** the install location. This is the place where Xonotic saves your userdata.
+
+- **Windows**: `C:\users\user\saved games\xonotic\data`
+- **Linux**: `~/.xonotic/data`
+- **Mac**: `~/Library/Application Support/xonotic/data`
+
+This folder has a similar layout as the game folder. Game wise these data folders are treated similarly, however, it is best to save your work in the userdata folder so that you don’t accidentally mess up your Xonotic install, or so that your work doesn’t get lost in an update.
+
+### Step 4 (optional): Move the mapping support pk3
+
+The mapping support zip contains a file called `xonotic-<timestamp>-maps-mapping.pk3`. Move this file to the userdata folder (see step 3), **NOT** `data/data`.
+This folder should also contain your `config.cfg`.
+
+### Step 5: Get NetRadiant working
+
+- **Windows**: Windows users can download a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/).
+The mapping support zip also contains a compiled version of NetRadiant in the `mapping` folder but while it may works, it is fairly outdated and lacks a lot of updates.
+- **Linux**: Linux users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/).
+(_NOTE: Archlinux users can also use the [netradiant-git](https://aur.archlinux.org/packages/netradiant-git/) PKGBUILD_)
+- **macOS**: macOS users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/).
+- **FreeBSD**: FreeBSD users can use a precompiled version downloadable from the [NetRadiant website](https://netradiant.gitlab.io/page/download/).
+
+People wanting to compile NetRadiant themselves can look at the [NetRadiant Repository](https://gitlab.com/xonotic/netradiant).
+
+### Step 6: Set up NetRadiant
+
+When you first start up radiant it may ask where the engine path is. Simply point it to the Xonotic install location. Then NetRadiant should start and the lower right pane should have a list of texture packs. If there are no texture packs, then you may need the mapping support, please refer back to step 4.
+
+\<\< [Introduction](mapping-Introduction) | [NetRadiant](mapping-NetRadiant) \>\>
+
… [Creating_Maps](Creating-Maps) …
\ No newline at end of file
-### Faster compiling and reloading of QuakeC\r
-\r
-You can use `QCCFLAGS_WERROR=""` to let the build succeed even with some warnings and `ZIP=:` to skip compressing the resulting csprogs.dat (client gamecode) into a pk3. A compressed csprogs.dat is only useful to increase download speed of such file if you host an online dedicated server.\r
-\r
-`QCCFLAGS_WERROR="" ZIP=: ./all compile`\r
-\r
-Server and menu code produce progs.dat and menu.dat respectively.\r
-\r
-Compiling the Xonotic game code without trying to compile the engine code reduces compile time a little bit, in the case you aren't interested in changing the engine code. You can do so by running this command from the xonotic-data.pk3dir directory:\r
-\r
-`make qc -j4`\r
-\r
-where `-j4` is an option that lets you use up to 4 CPU cores for the compilation (it's enabled by default in `./all compile`). If you want you can run `make all -j4` to enable csprogs.dat compression.\r
-\r
-To test the QC client and server programs you don't need to restart Xonotic, you just have to start a new game with `map <mapname>` (depending on how you launch Xonotic you may need to use `fs_rescan; map <mapname>`).\r
-\r
-To test the QC menu program, you just have to restart the menu by executing `menu_restart` in the console.\r
-\r
-### Debug prints\r
-\r
-Use `con_notify 4` together with `LOG_INFOF("my_var: %s", my_var);` (`%s` string, `%f` float, `%d` integer, `%v` vector) to see debug output without opening the console. Type `con_notify` and press `<TAB>` to see descriptions and more options (or use `apropos con_notify`).\r
-\r
-You can draw text anywhere on the map using `debug_text_3d(world_coords, message);` from `common/debug.qh`.\r
-\r
-### Multiple clients + clean config\r
-\r
-If you need 2 players for debugging, you can launch another client locally:\r
-- use -sessionid (e.g. `./all run -sessionid testing`) to keep your config\r
-- use -userdir (e.g. `./all run -userdir ~/.xonotic-testing +name tester +cl_allow_uid2name 0`) to get a clean config (if you delete the dir before each use)\r
- - you can set any cvar or run any command on start with `+cvar_name value`\r
- - `+name tester` avoids the nick selection dialog\r
- - `+cl_allow_uid2name 0` avoids an annoying popup \r
-\r
-### Testing with bots\r
-\r
-You can prevent bots from firing with `bot_nofire 1` or stop them completely with `bot_cmd * pause` (unstop them with `bot_cmd * continue`). With `sv_cheats 1` (takes effect next match), you can drag them around (default key V, if not bound you can bind 'drag object (sandbox)' in menu, Settings/Input window).\r
-\r
-Note that `sv_cheats 1` prevents bots from spawning in the campaign (should you decide to put it in your `autoexec.cfg` and later wonder why the campaign is broken).\r
-\r
-### Debugging\r
-\r
-Useful commands to debug qc code:\r
-```\r
-prvm_breakpoint : marks a statement or function as breakpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear breakpoint\r
-\r
-prvm_edict : print all data about an entity number in the selected VM (server, client, menu)\r
-prvm_edictget : retrieves the value of a specified property of a specified entity in the selected VM (server, client menu) into a cvar or to the console\r
-prvm_edicts : prints all data about all entities in the selected VM (server, client, menu)\r
-prvm_edictset : changes value of a specified property of a specified entity in the selected VM (server, client, menu)\r
-prvm_edictwatchpoint : marks an entity field as watchpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear watchpoint\r
-\r
-prvm_global : prints value of a specified global variable in the selected VM (server, client, menu)\r
-prvm_globalget : retrieves the value of a specified global variable in the selected VM (server, client menu) into a cvar or to the console\r
-prvm_globals : prints all global variables in the selected VM (server, client, menu)\r
-prvm_globalset : sets value of a specified global variable in the selected VM (server, client, menu)\r
-prvm_globalwatchpoint : marks a global as watchpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear watchpoint\r
-```\r
-\r
-Examples: \r
-Print to console origin of entity number 1: `prvm_edictget server 1 origin` \r
-Save to a cvar origin of entity number 1: `prvm_edictget server 1 origin my_cvar` \r
-Set a custom origin for entity number 1: `prvm_edictset server 1 origin "100 200 0"`\r
-\r
-Setting view angles requires a particular trick, we also need to set fixangle to true in the same server frame:\r
-`prvm_edictset server 1 fixangle 1; prvm_edictset server 1 angles "20 -90 0"`\r
-\r
-Print to console vid_conheight client global: `prvm_edictget client vid_conheight`\r
-\r
-"Break" on statement: `prvm_breakpoint server 12345` \r
-"Break" on function: `prvm_breakpoint server ClientConnect` \r
-Watch for global change: `prvm_globalwatchpoint server time` \r
-Watch for entity field change: `prvm_edictwatchpoint server 1 health` \r
-\r
-There can be only one of each kind. To clear, do:\r
-```\r
-prvm_breakpoint server\r
-prvm_globalwatchpoint server\r
-prvm_edictwatchpoint server\r
-```\r
-\r
-As of Xonotic 0.8.6 many of those commands are available via shorter aliases:\r
-\r
-```\r
-// breakpoint\r
-alias ps_b "prvm_breakpoint server ${* ?}"\r
-alias pc_b "prvm_breakpoint client ${* ?}"\r
-alias pm_b "prvm_breakpoint menu ${* ?}"\r
-\r
-// entity\r
-alias ps_e "prvm_edict server ${* ?}"\r
-alias pc_e "prvm_edict client ${* ?}"\r
-alias pm_e "prvm_edict menu ${* ?}"\r
-\r
-// field get\r
-alias ps_fg "prvm_edictget server ${* ?}"\r
-alias pc_fg "prvm_edictget client ${* ?}"\r
-alias pm_fg "prvm_edictget menu ${* ?}"\r
-// field set\r
-alias ps_fs "prvm_edictset server ${* ?}"\r
-alias pc_fs "prvm_edictset client ${* ?}"\r
-alias pm_fs "prvm_edictset menu ${* ?}"\r
-// field watchpoint\r
-alias ps_fw "prvm_edictwatchpoint server ${* ?}"\r
-alias pc_fw "prvm_edictwatchpoint client ${* ?}"\r
-alias pm_fw "prvm_edictwatchpoint menu ${* ?}"\r
-\r
-// global get\r
-alias ps_gg "prvm_globalget server ${* ?}"\r
-alias pc_gg "prvm_globalget client ${* ?}"\r
-alias pm_gg "prvm_globalget menu ${* ?}"\r
-// global set\r
-alias ps_gs "prvm_globalset server ${* ?}"\r
-alias pc_gs "prvm_globalset client ${* ?}"\r
-alias pm_gs "prvm_globalset menu ${* ?}"\r
-// global watchpoint\r
-alias ps_gw "prvm_globalwatchpoint server ${* ?}"\r
-alias pc_gw "prvm_globalwatchpoint client ${* ?}"\r
-alias pm_gw "prvm_globalwatchpoint menu ${* ?}"\r
-```\r
-\r
-\r
-### Doxygen\r
-\r
-Incomplete [Doxygen documentation](https://timepath.github.io/scratchspace/index.html) is generated as part of CI on [xonotic-data.pk3dir](https://gitlab.com/xonotic/xonotic-data.pk3dir) - you can search functions, "classes", globals, etc.\r
-\r
-Note that it might be incomplete or incorrect because [Doxygen](https://www.doxygen.nl) doesn't understand all of QC's constructs and our code heavily uses macros. See the `doxygen` section of the [CI file](https://gitlab.com/xonotic/xonotic-data.pk3dir/blob/master/.gitlab-ci.yml) for details what's missing.\r
-\r
-### Tool to find C symbols, functions, declarations and definitions inside source code\r
-\r
-For this purpose it's possible to use a text-based tool called [Cscope](https://en.wikipedia.org/wiki/Cscope) together with a GUI (it can be either an application or a plugin for a text editor).\r
-\r
-##### Download / Installation\r
-\r
-* Download and install cscope with `pacman -S cscope` \r
-Windows users must download the Windows version of cscope from https://code.google.com/archive/p/cscope-win32/downloads and put it into the main xonotic repo directory. The mingw version can't be used as it puts Unix paths into the generated indices, making them unusable.\r
-\r
-* Download and install a cscope GUI or a plugin for your text editor / IDE.\r
- * For [jEdit](http://www.jedit.org) there is a plugin called [CscopeFinder](http://plugins.jedit.org/plugins/?CscopeFinder).\r
- * For [SublimeText](https://www.sublimetext.com) there is [SublimeCscope](https://github.com/jgust/SublimeCscope)\r
- * For [Atom](https://atom.io/) there is [atom-cscope](https://atom.io/packages/atom-cscope)\r
-\r
-* If you don't use Atom, you also need to copy ~~[cscope_createindex.sh](uploads/17c725e19be8f4935c30c2506e168405/cscope_createindex.sh)(old version)~~ [cscope_createindex.sh](uploads/451835f6b1894145af06050915256048/cscope_createindex.sh) into the main xonotic repo directory.\r
-\r
-\r
-##### Configuration\r
-\r
-* Configure your plugin if needed: \r
- * jEdit's CscopeFinder settings: \r
- set cscope.out as cscope index filename. \r
-\r
- * SublimeCscope user settings (with Windows executable as example):\r
- ```\r
- "executable": "C:\\xonotic\\cscope.exe",\r
- "prompt_before_searching": false,\r
- ```\r
-\r
- * atom-cscope settings:\r
- 1. set the full path of cscope binary, e.g. C:\xonotic\cscope.exe (with Windows executable as example) \r
- 1. add .qc and .qh to source file extensions (".c .cc .cpp .h .hpp .qc .qh")\r
- 1. you also need to create projects for darkplaces and xonotic/data/xonotic-data.pk3dir/qcsrc folders (toggle tree-view with `Ctrl + \`, right-click there and select "Add Project Folder")\r
-\r
-* Run `cscope_createindex.sh` to build cscope indices for both game (QC code) and Darkplaces (C code). This step must be repeated every time you do some code changes.\r
-\r
-* Some plugins assume that your index file is generated with compression turned on (SublimeCscope's case). In this case `cscope_createindex.sh` can be instructed to use compression by changing `compress=false` to `compress=true`.\r
-\r
-* With Atom you can build cscope indices in the atom-cscope window (open with `Ctrl + Alt + o`) by clicking the flash icon.\r
-\r
-##### Usage\r
-\r
-* jEdit: select a word in the editor, right-click and select "Find this C symbol" or another "Find ..." entry (if you don't see these entries you should add them in the context menu settings).\r
-* SublimeText: select a word in the editor, right-click and select "Look up symbol" or another "Look up ..." entry.\r
-* Atom: open atom-cscope window (`Ctrl + Alt + o`) and type a symbol that you want to search.\r
-\r
-\r
-### QC syntax highlighting:\r
-\r
-* terencehill's version for jEdit: [qc.xml](https://gitlab.com/terencehill/qc-syntax-highlighting-for-jedit/blob/master/qc.xml)\r
+### Faster compiling and reloading of QuakeC
+
+You can use `QCCFLAGS_WERROR=""` to let the build succeed even with some warnings and `ZIP=:` to skip compressing the resulting csprogs.dat (client gamecode) into a pk3. A compressed csprogs.dat is only useful to increase download speed of such file if you host an online dedicated server.
+
+`QCCFLAGS_WERROR="" ZIP=: ./all compile`
+
+Server and menu code produce progs.dat and menu.dat respectively.
+
+Compiling the Xonotic game code without trying to compile the engine code reduces compile time a little bit, in the case you aren't interested in changing the engine code. You can do so by running this command from the xonotic-data.pk3dir directory:
+
+`make qc -j4`
+
+where `-j4` is an option that lets you use up to 4 CPU cores for the compilation (it's enabled by default in `./all compile`). If you want you can run `make all -j4` to enable csprogs.dat compression.
+
+To test the QC client and server programs you don't need to restart Xonotic, you just have to start a new game with `map <mapname>` (depending on how you launch Xonotic you may need to use `fs_rescan; map <mapname>`).
+
+To test the QC menu program, you just have to restart the menu by executing `menu_restart` in the console.
+
+### Debug prints
+
+Use `con_notify 4` together with `LOG_INFOF("my_var: %s", my_var);` (`%s` string, `%f` float, `%d` integer, `%v` vector) to see debug output without opening the console. Type `con_notify` and press `<TAB>` to see descriptions and more options (or use `apropos con_notify`).
+
+You can draw text anywhere on the map using `debug_text_3d(world_coords, message);` from `common/debug.qh`.
+
+### Multiple clients + clean config
+
+If you need 2 players for debugging, you can launch another client locally:
+- use -sessionid (e.g. `./all run -sessionid testing`) to keep your config
+- use -userdir (e.g. `./all run -userdir ~/.xonotic-testing +name tester +cl_allow_uid2name 0`) to get a clean config (if you delete the dir before each use)
+ - you can set any cvar or run any command on start with `+cvar_name value`
+ - `+name tester` avoids the nick selection dialog
+ - `+cl_allow_uid2name 0` avoids an annoying popup
+
+### Testing with bots
+
+You can prevent bots from firing with `bot_nofire 1` or stop them completely with `bot_cmd * pause` (unstop them with `bot_cmd * continue`). With `sv_cheats 1` (takes effect next match), you can drag them around (default key V, if not bound you can bind 'drag object (sandbox)' in menu, Settings/Input window).
+
+Note that `sv_cheats 1` prevents bots from spawning in the campaign (should you decide to put it in your `autoexec.cfg` and later wonder why the campaign is broken).
+
+### Debugging
+
+Useful commands to debug qc code:
+```
+prvm_breakpoint : marks a statement or function as breakpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear breakpoint
+
+prvm_edict : print all data about an entity number in the selected VM (server, client, menu)
+prvm_edictget : retrieves the value of a specified property of a specified entity in the selected VM (server, client menu) into a cvar or to the console
+prvm_edicts : prints all data about all entities in the selected VM (server, client, menu)
+prvm_edictset : changes value of a specified property of a specified entity in the selected VM (server, client, menu)
+prvm_edictwatchpoint : marks an entity field as watchpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear watchpoint
+
+prvm_global : prints value of a specified global variable in the selected VM (server, client, menu)
+prvm_globalget : retrieves the value of a specified global variable in the selected VM (server, client menu) into a cvar or to the console
+prvm_globals : prints all global variables in the selected VM (server, client, menu)
+prvm_globalset : sets value of a specified global variable in the selected VM (server, client, menu)
+prvm_globalwatchpoint : marks a global as watchpoint (when this is executed, a stack trace is printed); to actually halt and investigate state, combine this with a gdb breakpoint on PRVM_Breakpoint, or with prvm_breakpointdump; run with just progs name to clear watchpoint
+```
+
+Examples:
+Print to console origin of entity number 1: `prvm_edictget server 1 origin`
+Save to a cvar origin of entity number 1: `prvm_edictget server 1 origin my_cvar`
+Set a custom origin for entity number 1: `prvm_edictset server 1 origin "100 200 0"`
+
+Setting view angles requires a particular trick, we also need to set fixangle to true in the same server frame:
+`prvm_edictset server 1 fixangle 1; prvm_edictset server 1 angles "20 -90 0"`
+
+Print to console vid_conheight client global: `prvm_edictget client vid_conheight`
+
+"Break" on statement: `prvm_breakpoint server 12345`
+"Break" on function: `prvm_breakpoint server ClientConnect`
+Watch for global change: `prvm_globalwatchpoint server time`
+Watch for entity field change: `prvm_edictwatchpoint server 1 health`
+
+There can be only one of each kind. To clear, do:
+```
+prvm_breakpoint server
+prvm_globalwatchpoint server
+prvm_edictwatchpoint server
+```
+
+As of Xonotic 0.8.6 many of those commands are available via shorter aliases:
+
+```
+// breakpoint
+alias ps_b "prvm_breakpoint server ${* ?}"
+alias pc_b "prvm_breakpoint client ${* ?}"
+alias pm_b "prvm_breakpoint menu ${* ?}"
+
+// entity
+alias ps_e "prvm_edict server ${* ?}"
+alias pc_e "prvm_edict client ${* ?}"
+alias pm_e "prvm_edict menu ${* ?}"
+
+// field get
+alias ps_fg "prvm_edictget server ${* ?}"
+alias pc_fg "prvm_edictget client ${* ?}"
+alias pm_fg "prvm_edictget menu ${* ?}"
+// field set
+alias ps_fs "prvm_edictset server ${* ?}"
+alias pc_fs "prvm_edictset client ${* ?}"
+alias pm_fs "prvm_edictset menu ${* ?}"
+// field watchpoint
+alias ps_fw "prvm_edictwatchpoint server ${* ?}"
+alias pc_fw "prvm_edictwatchpoint client ${* ?}"
+alias pm_fw "prvm_edictwatchpoint menu ${* ?}"
+
+// global get
+alias ps_gg "prvm_globalget server ${* ?}"
+alias pc_gg "prvm_globalget client ${* ?}"
+alias pm_gg "prvm_globalget menu ${* ?}"
+// global set
+alias ps_gs "prvm_globalset server ${* ?}"
+alias pc_gs "prvm_globalset client ${* ?}"
+alias pm_gs "prvm_globalset menu ${* ?}"
+// global watchpoint
+alias ps_gw "prvm_globalwatchpoint server ${* ?}"
+alias pc_gw "prvm_globalwatchpoint client ${* ?}"
+alias pm_gw "prvm_globalwatchpoint menu ${* ?}"
+```
+
+
+### Doxygen
+
+Incomplete [Doxygen documentation](https://timepath.github.io/scratchspace/index.html) is generated as part of CI on [xonotic-data.pk3dir](https://gitlab.com/xonotic/xonotic-data.pk3dir) - you can search functions, "classes", globals, etc.
+
+Note that it might be incomplete or incorrect because [Doxygen](https://www.doxygen.nl) doesn't understand all of QC's constructs and our code heavily uses macros. See the `doxygen` section of the [CI file](https://gitlab.com/xonotic/xonotic-data.pk3dir/blob/master/.gitlab-ci.yml) for details what's missing.
+
+### Tool to find C symbols, functions, declarations and definitions inside source code
+
+For this purpose it's possible to use a text-based tool called [Cscope](https://en.wikipedia.org/wiki/Cscope) together with a GUI (it can be either an application or a plugin for a text editor).
+
+##### Download / Installation
+
+* Download and install cscope with `pacman -S cscope`
+Windows users must download the Windows version of cscope from https://code.google.com/archive/p/cscope-win32/downloads and put it into the main xonotic repo directory. The mingw version can't be used as it puts Unix paths into the generated indices, making them unusable.
+
+* Download and install a cscope GUI or a plugin for your text editor / IDE.
+ * For [jEdit](http://www.jedit.org) there is a plugin called [CscopeFinder](http://plugins.jedit.org/plugins/?CscopeFinder).
+ * For [SublimeText](https://www.sublimetext.com) there is [SublimeCscope](https://github.com/jgust/SublimeCscope)
+ * For [Atom](https://atom.io/) there is [atom-cscope](https://atom.io/packages/atom-cscope)
+
+* If you don't use Atom, you also need to copy ~~[cscope_createindex.sh](uploads/17c725e19be8f4935c30c2506e168405/cscope_createindex.sh)(old version)~~ [cscope_createindex.sh](uploads/451835f6b1894145af06050915256048/cscope_createindex.sh) into the main xonotic repo directory.
+
+
+##### Configuration
+
+* Configure your plugin if needed:
+ * jEdit's CscopeFinder settings:
+ set cscope.out as cscope index filename.
+
+ * SublimeCscope user settings (with Windows executable as example):
+ ```
+ "executable": "C:\\xonotic\\cscope.exe",
+ "prompt_before_searching": false,
+ ```
+
+ * atom-cscope settings:
+ 1. set the full path of cscope binary, e.g. C:\xonotic\cscope.exe (with Windows executable as example)
+ 1. add .qc and .qh to source file extensions (".c .cc .cpp .h .hpp .qc .qh")
+ 1. you also need to create projects for darkplaces and xonotic/data/xonotic-data.pk3dir/qcsrc folders (toggle tree-view with `Ctrl + \`, right-click there and select "Add Project Folder")
+
+* Run `cscope_createindex.sh` to build cscope indices for both game (QC code) and Darkplaces (C code). This step must be repeated every time you do some code changes.
+
+* Some plugins assume that your index file is generated with compression turned on (SublimeCscope's case). In this case `cscope_createindex.sh` can be instructed to use compression by changing `compress=false` to `compress=true`.
+
+* With Atom you can build cscope indices in the atom-cscope window (open with `Ctrl + Alt + o`) by clicking the flash icon.
+
+##### Usage
+
+* jEdit: select a word in the editor, right-click and select "Find this C symbol" or another "Find ..." entry (if you don't see these entries you should add them in the context menu settings).
+* SublimeText: select a word in the editor, right-click and select "Look up symbol" or another "Look up ..." entry.
+* Atom: open atom-cscope window (`Ctrl + Alt + o`) and type a symbol that you want to search.
+
+
+### QC syntax highlighting:
+
+* terencehill's version for jEdit: [qc.xml](https://gitlab.com/terencehill/qc-syntax-highlighting-for-jedit/blob/master/qc.xml)
* EACFreddy's version for Kate: [qc.xml](https://gist.github.com/DefaultUser/998f030ab41a9e8edf4a9f8e703c6350)
\ No newline at end of file
----\r
-title: Xonotic git builds\r
----\r
-\r
-Git builds have higher system requirements and are more work to compile and maintain than [autobuilds](Autobuilds) but are needed to develop and/or test Merge Requests.\r
-\r
-To get push access and contribute please read [CONTRIBUTING](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md). \r
-For assistance with using `git` and the `all` script for development please see the [git howto](Git). \r
-\r
----\r
-\r
-Xonotic uses [several Git repositories](Git). The `all` script in the main repo manages them, builds Xonotic and runs it. Each repo can also contain feature branches next to the stable `master` branch, check them out for WIP features.\r
-\r
-\r
-# Build Requirements\r
-\r
-Make sure you have at least 2GB memory to compile. This is enough to run a git dedicated server, but 6GB is required to play using a git client (it uses more memory than regular release and auto builds). \r
-\r
-The git client will perform poorly (compared to regular release or auto builds) on GPUs with limited VRAM, such as integrated GPUs.\r
-\r
-[About 12GB of disk space is required for the git repositories.](Git)\r
-\r
-### Linux\r
-\r
-Note: `curl` isn't required but it's strongly recommended for downloading maps when playing online, `wget` is not supported for this. \r
-\r
-Note: The `all` script requires either `wget` or `curl`.\r
-\r
-\r
-**Ubuntu** dependencies:\r
-\r
- sudo apt-get install autoconf automake build-essential curl git libtool libgmp-dev libjpeg-turbo8-dev libsdl2-dev libxpm-dev xserver-xorg-dev zlib1g-dev unzip zip\r
-\r
-Note: On Debian, use `libjpeg62-turbo-dev` if `libjpeg-turbo8-dev` isn’t available in the package repositories.\r
-\r
-Note: `libasound2-dev libxext-dev libxxf86vm-dev p7zip-full unzip wget x11proto-xf86vidmode-dev` might be needed but are probably already installed. `libclalsadrv-dev libsdl2-image-dev libxcb-xf86dri0-dev libxxf86dga-dev x11proto-xf86dga-dev x11proto-xf86dri-dev` should no longer be needed.\r
-\r
-**Fedora** and other **RPM based** distro dependencies:\r
-\r
- autoconf automake gcc-c++ gmp-devel libjpeg-turbo-devel libtool SDL2-devel curl libXext-devel alsa-lib-devel libXxf86vm-devel\r
-\r
-Note: `x11-proto-devel` or `xorg-x11-proto-devel` might be needed but might be already installed.\r
-\r
-**Archlinux** dependencies:\r
-\r
- sudo pacman -S alsa-lib curl git libjpeg-turbo libmodplug libpng libvorbis libxpm xorgproto libxxf86vm sdl2 unzip zip\r
-\r
-### Windows\r
-\r
-By default, Windows has no real environment to handle the necessary scripting and compiling tools for building Xonotic. So, what we have to do is install something called [MSYS2](http://www.msys2.org) to allow us to have a similar environment as on Linux. Download 64 bit version of MSYS2 (msys2-x86_64-xxxxxx.exe) and follow installation instructions.\r
-\r
-Once you have completed the installation, close the current MSYS2 shell and launch a MSYS2 MINGW64 shell by running mingw64.exe (instead of the default msys2.exe) located at C:\msys64 and install the needed dependencies with this command:\r
-\r
- pacman --needed -S git curl zip unzip p7zip make automake autoconf libtool gcc gmp-devel mingw-w64-x86_64-{curl,freetype,toolchain,gmp,SDL2,libjpeg-turbo,libpng,libogg,libtheora,libvorbis}\r
-\r
-It is recommended that you make a shortcut to MSYS2 MINGW64 shell (simply right click mingw64.exe and hit “Create Shortcut”) for easier access on your desktop or in your start menu.\r
-\r
-You can now use this shell to continue on with the guide and clone the Xonotic repositories.\r
-\r
-### macOS\r
-\r
-You must first install **XCode** which comes on your installation DVD or can be downloaded from the Apple website. This package provides tools like **Git and GCC**, which are needed for successful checkout and compilation of Xonotic. Some versions of XCode come with Git and others don’t - if you don’t have Git after installing XCode get it here: [XCode installer](http://sourceforge.net/projects/git-osx-installer/files/)\r
-\r
-\r
-# Cloning the Repository and Compiling\r
-\r
-To begin downloading:\r
-\r
- git clone https://gitlab.com/xonotic/xonotic.git # download main repo\r
- cd xonotic\r
- ./all update -l best # download all other repos (data + game logic, maps, etc.)\r
-\r
-Now the game can be compiled and run with the following commands:\r
-\r
- ./all compile\r
- ./all run\r
-\r
-**Note:** if you encounter en error similar to darkplaces#111, try `./all clean && ./all compile -0`.\r
-\r
-You can use `./all compile -d` to create a slower unoptimized build with debug symbols.\r
-\r
-The `./all run` or `./all compile` line can be followed by `dedicated` to build or run the executable for server hosting. E.g. `./all compile dedicated`.\r
-\r
-The `run` command can also be followed by standard DarkPlaces commandline arguments:\r
-\r
- ./all run +vid_fullscreen 0\r
-\r
-To update your Git clone:\r
-\r
- cd xonotic\r
- ./all checkout # switch to main branch on all repos (usually master)\r
- ./all update # pull and prune\r
- ./all compile # recompile what changed\r
-\r
-**Note:** If you intend to play on public servers, you should probably also enable the nexcompat repo to download additional textures that are used on some older unofficial maps. Use `touch data/xonotic-nexcompat.pk3dir.yes` and `./all update`. For mappers: these textures should NOT be used on new maps.\r
-\r
-***\r
-\r
-If you run into issues with the latest version you can easily revert to an older one. Since most bugs are caused by the game code rather that the engine, you just need to downgrade that repository. Inside the main xonotic repository, use `cd data/xonotic-data.pk3dir` and then `git checkout <some older commit>`. After that go back `cd -` and `./all compile`.\r
-\r
-\r
-# ./all script commands (Windows/Linux/macOS)\r
-\r
-Get a checkout (see above), and do:\r
-\r
- ./all keygen\r
-\r
-and follow the instructions that are shown. Be sure that you've done:\r
-\r
- ./all update -p\r
-\r
-After that, you can write to the repositories using the usual git commands (commit, push, ...).\r
-\r
-Alternatively, you can use the helper script `all`.\r
-It supports the following commands:\r
-\r
- ./all update\r
-\r
-This command updates all the Xonotic repositories.\r
-\r
- ./all branch\r
-\r
-Lists the branches you are currently on, in the respective repositories.\r
-\r
- ./all branches\r
-\r
-Lists all the branches known for all the respective repositories.\r
-\r
- ./all compile\r
-\r
-Compiles the game, assuming that you have the required libs installed.\r
-\r
- ./all checkout BRANCH\r
-\r
-Switch to that branch in all repositories where its available.\r
-\r
- ./all commit\r
-\r
-This command commits and pushes your local changes.\r
-\r
- ./all run\r
-\r
-Starts the Xonotic client\r
-\r
- ./all run dedicated\r
-\r
-Starts a Xonotic dedicated server\r
-\r
-\r
-# Git guides\r
-\r
-Git howto on [this wiki page](Git).\r
-\r
-About tracking remote branches:\r
-https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\r
-\r
-A tutorial to Git for SVN users:\r
-https://git.wiki.kernel.org/index.php/GitSvnCrashCourse\r
+---
+title: Xonotic git builds
+---
+
+Git builds have higher system requirements and are more work to compile and maintain than [autobuilds](Autobuilds) but are needed to develop and/or test Merge Requests.
+
+To get push access and contribute please read [CONTRIBUTING](https://gitlab.com/xonotic/xonotic/-/blob/master/CONTRIBUTING.md).
+For assistance with using `git` and the `all` script for development please see the [git howto](Git).
+
+---
+
+Xonotic uses [several Git repositories](Git). The `all` script in the main repo manages them, builds Xonotic and runs it. Each repo can also contain feature branches next to the stable `master` branch, check them out for WIP features.
+
+
+# Build Requirements
+
+Make sure you have at least 2GB memory to compile. This is enough to run a git dedicated server, but 6GB is required to play using a git client (it uses more memory than regular release and auto builds).
+
+The git client will perform poorly (compared to regular release or auto builds) on GPUs with limited VRAM, such as integrated GPUs.
+
+[About 12GB of disk space is required for the git repositories.](Git)
+
+### Linux
+
+Note: `curl` isn't required but it's strongly recommended for downloading maps when playing online, `wget` is not supported for this.
+
+Note: The `all` script requires either `wget` or `curl`.
+
+
+**Ubuntu** dependencies:
+
+ sudo apt-get install autoconf automake build-essential curl git libtool libgmp-dev libjpeg-turbo8-dev libsdl2-dev libxpm-dev xserver-xorg-dev zlib1g-dev unzip zip
+
+Note: On Debian, use `libjpeg62-turbo-dev` if `libjpeg-turbo8-dev` isn’t available in the package repositories.
+
+Note: `libasound2-dev libxext-dev libxxf86vm-dev p7zip-full unzip wget x11proto-xf86vidmode-dev` might be needed but are probably already installed. `libclalsadrv-dev libsdl2-image-dev libxcb-xf86dri0-dev libxxf86dga-dev x11proto-xf86dga-dev x11proto-xf86dri-dev` should no longer be needed.
+
+**Fedora** and other **RPM based** distro dependencies:
+
+ autoconf automake gcc-c++ gmp-devel libjpeg-turbo-devel libtool SDL2-devel curl libXext-devel alsa-lib-devel libXxf86vm-devel
+
+Note: `x11-proto-devel` or `xorg-x11-proto-devel` might be needed but might be already installed.
+
+**Archlinux** dependencies:
+
+ sudo pacman -S alsa-lib curl git libjpeg-turbo libmodplug libpng libvorbis libxpm xorgproto libxxf86vm sdl2 unzip zip
+
+### Windows
+
+By default, Windows has no real environment to handle the necessary scripting and compiling tools for building Xonotic. So, what we have to do is install something called [MSYS2](http://www.msys2.org) to allow us to have a similar environment as on Linux. Download 64 bit version of MSYS2 (msys2-x86_64-xxxxxx.exe) and follow installation instructions.
+
+Once you have completed the installation, close the current MSYS2 shell and launch a MSYS2 MINGW64 shell by running mingw64.exe (instead of the default msys2.exe) located at C:\msys64 and install the needed dependencies with this command:
+
+ pacman --needed -S git curl zip unzip p7zip make automake autoconf libtool gcc gmp-devel mingw-w64-x86_64-{curl,freetype,toolchain,gmp,SDL2,libjpeg-turbo,libpng,libogg,libtheora,libvorbis}
+
+It is recommended that you make a shortcut to MSYS2 MINGW64 shell (simply right click mingw64.exe and hit “Create Shortcut”) for easier access on your desktop or in your start menu.
+
+You can now use this shell to continue on with the guide and clone the Xonotic repositories.
+
+### macOS
+
+You must first install **XCode** which comes on your installation DVD or can be downloaded from the Apple website. This package provides tools like **Git and GCC**, which are needed for successful checkout and compilation of Xonotic. Some versions of XCode come with Git and others don’t - if you don’t have Git after installing XCode get it here: [XCode installer](http://sourceforge.net/projects/git-osx-installer/files/)
+
+
+# Cloning the Repository and Compiling
+
+To begin downloading:
+
+ git clone https://gitlab.com/xonotic/xonotic.git # download main repo
+ cd xonotic
+ ./all update -l best # download all other repos (data + game logic, maps, etc.)
+
+Now the game can be compiled and run with the following commands:
+
+ ./all compile
+ ./all run
+
+**Note:** if you encounter en error similar to darkplaces#111, try `./all clean && ./all compile -0`.
+
+You can use `./all compile -d` to create a slower unoptimized build with debug symbols.
+
+The `./all run` or `./all compile` line can be followed by `dedicated` to build or run the executable for server hosting. E.g. `./all compile dedicated`.
+
+The `run` command can also be followed by standard DarkPlaces commandline arguments:
+
+ ./all run +vid_fullscreen 0
+
+To update your Git clone:
+
+ cd xonotic
+ ./all checkout # switch to main branch on all repos (usually master)
+ ./all update # pull and prune
+ ./all compile # recompile what changed
+
+**Note:** If you intend to play on public servers, you should probably also enable the nexcompat repo to download additional textures that are used on some older unofficial maps. Use `touch data/xonotic-nexcompat.pk3dir.yes` and `./all update`. For mappers: these textures should NOT be used on new maps.
+
+***
+
+If you run into issues with the latest version you can easily revert to an older one. Since most bugs are caused by the game code rather that the engine, you just need to downgrade that repository. Inside the main xonotic repository, use `cd data/xonotic-data.pk3dir` and then `git checkout <some older commit>`. After that go back `cd -` and `./all compile`.
+
+
+# ./all script commands (Windows/Linux/macOS)
+
+Get a checkout (see above), and do:
+
+ ./all keygen
+
+and follow the instructions that are shown. Be sure that you've done:
+
+ ./all update -p
+
+After that, you can write to the repositories using the usual git commands (commit, push, ...).
+
+Alternatively, you can use the helper script `all`.
+It supports the following commands:
+
+ ./all update
+
+This command updates all the Xonotic repositories.
+
+ ./all branch
+
+Lists the branches you are currently on, in the respective repositories.
+
+ ./all branches
+
+Lists all the branches known for all the respective repositories.
+
+ ./all compile
+
+Compiles the game, assuming that you have the required libs installed.
+
+ ./all checkout BRANCH
+
+Switch to that branch in all repositories where its available.
+
+ ./all commit
+
+This command commits and pushes your local changes.
+
+ ./all run
+
+Starts the Xonotic client
+
+ ./all run dedicated
+
+Starts a Xonotic dedicated server
+
+
+# Git guides
+
+Git howto on [this wiki page](Git).
+
+About tracking remote branches:
+https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches
+
+A tutorial to Git for SVN users:
+https://git.wiki.kernel.org/index.php/GitSvnCrashCourse
projects / xonotic / xonotic.wiki.git / commitdiff