There is no need to install Xonotic! The zip file you downloaded from the homepage has everything. All binaries to run the game on Linux, Windows and macOS are inside of it. Just unzip the archive and run the appropriate executable for your OS.
For example, on Windows or macOS you can start the game by double-clicking the Xonotic logo. On Linux you can run xonotic-linux-glx.sh or xonotic-linux-sdl.sh - whichever one works better on your hardware.
Unfortunately, Xonotic is not in the Debian repositories yet. You can check the status of the bug report here. If you can help us expedite this process, please contact us!
There are two pronunciations, depending on where you live.
US people are more likely to pronounce it : zone + otic
European people are more likely to pronounce it : kso + notic
The logo design process took about a week, with a handful of people contributing designs, and constantly adjusting those designs based on feedback.
The phoenix image of the logo obviously refers to the concept of “rising from the ashes”.
Another aspect of the logo is the center ring, which has some similarities to the Quake logo; it has a fatter bottom edge and thinner top edge, though quake didn’t use a complete ring shape. This is intended as a pay of respect to the Quake origins of the game, as the Darkplaces engine was originally based on the Quake 1 engine.
The most likely reason Xonotic won’t start is that you’ve accidentally launched the dedicated server (e.g.
xonotic-linux64-dedicated) which runs silently in the background. It shares a lockfile (
~/.xonotic/lock) with the normal executable and prevents it from launching. Kill any processes which have xonotic in the name (you might also need to remove the lockfile manually) and try again.
Use the executables with sdl or glx in their name to launch Xonotic.
(Full error message: “You have reached this menu due to missing or unlocatable content/data. You may consider adding -basedir /path/to/game to your launch commandline.”)
In the Finder, control-click the app icon, then choose Open from the shortcut menu. Click Open on the dialog.
This happens because Xonotic is not signed using an Apple developer key.
This is probably because you don’t have the map that’s running on the server or it didn’t download correctly. Try clearing your dlcache (in <your config folder>/data/dlcache) and restarting Xonotic.
For Linux users: you need to have libcurl installed, otherwise you won’t be able to download any maps. libcurl should be available in any Linux distribution, just search for “libcurl” and install it in your distribution’s package manager.
This happens when the engine can’t load the data*.pk3 file or has trouble to initialize OpenGL. The reasons could be:
This happens when the engine has trouble initializing OpenGL. The reasons could be:
usermod -a -G video YOURUSERNAME. You need to logoff/in afterwards.
This is known to happen on Windows with Intel graphic chips and is a bug in the graphics drivers. A workaround is to set Flip-Policiy to blit. Open the control panel, there should be an icon called Intel® GMA driver (or something like that), double click it. Click on 3D Settings to find the screen with those settings.
You can choose predefined performance settings in the Settings->Video menu or you can enable/disable single features. The greatest performance boost can be achieved by turning off dynamic lights and shadows in the Settings->Effects menu. Bloom is also quite resource intensive. Other fps boots include disabling Deluxemapping and Coronas. On older graphics cards or on-board/notebook chips with little video ram you can try to lower the texture quality in the Settings->Video menu. Some graphic cards (mostly ATI or quite old cards) run A LOT faster if you disable the Vertex Buffer Objects in the Settings->Video menu. An other thing that can greatly help on such cards is to disable the OpenGL 2.0 Shaders. Having that option enabled is faster on most cards however, that is why both are active by default.
If none of that helps, you can try compiling Xonotic from source.
Try run xonotic-sdl.exe instead of xonotic.exe (on Windows). Adding the command line options -sndspeed 48000 and/or -sndstereo can also help on some systems (on Linux, Mac, Windows).
Mac: The default mouse acceleration on Mac is very high and strange. The Xonotic defaults work fine with it but some mouse drivers seem to ‘correct’ the mouse acceleration and conflict with the Xonotic defaults. Try to disable the option Turn off OS mouse acceleration in the Settings->Input menu. Or the same via console:
apple_mouse_noaccel 0; vid_restart (How do I open the console?)
Linux: A similar problem can arise on Linux. It’s also Turn off OS mouse acceleration in the Settings->Input menu but the console command is different (and only available in the glx executable):
vid_dga 0; vid_restart (How do I open the console?)
Check if your desktop color depth is set to 32 bits per pixel. If it’s just set to 16, Xonotic can’t switch to 32 bit mode.
Use our issue tracker on Gitlab.
If you want to investigate crashes further:
On Linux: In a xterm, cd into your Xonotic installation directory, start catchsegv ./xonotic-linux-686-sdl -condebug -developer > crash.txt 2>&1 and give the file crash.txt to the developers. Note that you can also use ./xonotic-linux-686-glx or if you have a 64bit system ./xonotic-linux-x86_64-sdl and ./xonotic-linux-x86_64-glx
On Windows: Click Start->Run, and enter drwtsn32, click Ok in the next window, run Xonotic and wait for the crash. Then go to C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson there should be a file called “drwtsn32.log”, give that file along with the engine’s build date to the developers. You’ll see that date when you open the ingame console (How do I open the console?). Note that some folders of that path may be hidden or have a translated name if you’re using a non-english windows.
Visit the official Xonotic forum, there is a support and bug report area. Or get on IRC to chat with others or ask for help. There is the normal users channel (irc://irc.quakenet.org/xonotic) and the developers channel (irc://irc.freenode.net/xonotic)
The install directory is what you get when you unzip the downloaded file. We usually call it Xonotic. Since Xonotic (the game) doesn’t need installation, Xonotic (the folder) can be anywhere you put it.
The config directory (sometimes called user directory) has a specific location depending on your OS but we usually call it ~/.xonotic since most players and devs are on linux. ~/.xonotic contains all your settings and it’s where you can put additional maps or assets when experimenting with the game or running your own server.
Maps usually ship as a .pk3 file. All you have to do is to copy this file to the <config folder>/data/ directory. To detect the new map, either restart Xonotic or run
fs_rescan in console.
Map packages that were downloaded from a server when playing on it end up in <your config folder>/data/dlcache/ and are only used till you exit Xonotic. If you want to play them locally or use them to setup a server of your own you can “accept” the packages by moving them one level up (right next to your config.cfg).
There are multiple unofficial map repositories.
Use the script xonotic-linux-sdl.sh or xonotic-linux-glx.sh instead of the binaries. The scripts will use the correct working directory, choose the right version (32 or 64 bit) and also allow you to start a extra X server.
Press [shift]+[escape]. To close it press [escape]. While playing ` or ^ will also open the console.
Colors can be used in nicknames and chat messages via two ways: Either the simple way by typing ^ followed by a number between 0 and 9 or by typing ^x followed by three hexadecimal numbers (0-F) representing red, green and blue components of the color before the text. The second way allows for much more colors. For example if you type ^xF00message the text “message” will be displayed in red color. Simple examples:
Demos are recordings of matches that you have played. To automatically record a demo each time you play enable the option Record demos while playing in Multiplayer->Media. Or if you just want to record some matches open the console and type
rec <demos/name> before playing. That is before starting a game or connecting to a server. The demo file will then be stored in your config folder/data/demos/<name>.dem. If you downloaded a demo, copy it to <your config folder>/data/demos/<name>.dem. You might have to create this directory if you have never recorded a demo before. To watch demos you can choose a demo file in Multiplayer->Media and click the play button. Also you can watch demos typing
ply <demos/name> in the console (How do I open the console?).
Use the Multiplayer->Create menu to start a listen server. You will always have to play yourself in a listen server. If you want to create a server without being forced to play yourself please take a look at the file readme.txt in the Xonotic/server/ directory where the dedicated server is explained.
The default port is 26000 UDP. You can change that in the Multiplayer->Create menu or by starting Xonotic with the parameter
-port <port> or having a line
port <port> in the server config file. If you follow the tutorial mentioned above you do not need this command line argument as it will be done in the config file created for the server. To add the command line argument on Windows, create a new shortcut to xonotic.exe or xonotic-dedicated.exe and right click on it. Select properties and
-port <port> in the “Target:” line. Be sure that the “Start in:” line contains the full path to your Xonotic folder and click “OK”. The parameter will be used if you start Xonotic via that new shortcut.
Yes there is a QuakeWorld compatible rcon. To use it you must enter
rcon_password <password> in the server console or server config file. The Xonotic client has to set the same password in the same fashion. You can then issue commands with
rcon <command> if you are connected to the server or will have to set
rcon_address <ip/hostname> or
rcon_address <ip/hostname>:<port> to point to the server. There are also external rcon tools but make sure you use a QW compatible rcon tool.
Enter status at the server console. You will see a list of all players. In front of their names you will see a number (the player id). You can kick the player you don’t like with
kick # <player id> <reason> (notice the space after #).
Lee Vermeulen, the Nexuiz project founder, decided to license the Nexuiz code (with LordHavoc licensing the Darkplaces engine) to a new game development company named Illfonic so that they could develop a closed-source version for the PS3. As part of this deal, IllFonic acquired the rights to use the name Nexuiz along with the domain nexuiz.com, and are under no obligation to contribute code back to the open-source Nexuiz project (and have stated that they have no intention of doing so).
When this was announced, the response from the Nexuiz community was overwhelming negative, even among the development team and main contributors. Vermeulen had not actively participated in the project for several years and all development had been done by the community. Most members have expressed a sense of betrayal and cited the project as an example of mushroom management. Vermeulen essentially cashed in on the hard work of others and sold the code, name and reputation that they had built up over years without him.
Despite attempts to reason with IllFonic, they have refused to change the name of their project to a derivative name even though they have directly stated that their “version” of Nexuiz is a completely different game. The hijacking of the Nexuiz project by its absentee founder and IllFonic made it clear that it had no future as it stood and thus the community left to found Xonotic.
It should also be noted that IllFonic’s code may be in violation of the GPL as most contributors to the Nexuiz codebase have not relicensed their work for inclusion in a closed-source project. This has been another source of outrage for many.
Update: The GPL concerns have been cleared up by a recent interview with LordHavoc.
Yes, many in the Nexuiz community tried to reach a compromise, such as having Illfonic contribute some artwork and/or gamecode back to Nexuiz GPL and for them to use a derivative name for their project, e.g. “Nexuiz Reloaded”.
Illfonic flatly refused all such suggestions. This, along with the clear stance that Alientrap has taken on this issue, made it clear that no compromise could be reached.
Update It has been clarified that, despite some of misleading wording in previous communication, Illfonic will be contributing some of the game code back to Nexuiz GPL, mainly having to do with bandwidth improvements and animation blending.
No! Without the past work of Vermeulen and LordHavoc, we would not have the game that we enjoy today. We wish them the best of luck in their endeavors. We hope Illfonic’s Nexuiz on PS3 is successful. We simply have a difference of opinion on project management and the result is going to be very positive; We’re forming a game project that matches what we wanted out of Nexuiz all along.