Frequently asked questions¶
I'm getting one of these error messages when trying to enable certain game mode:¶
- Server configuration lock this command (KTX r872 or older)
- Server disallows this command (KTX r873 or newer)
Not all game modes are allowed by default in our server packages. In order to enable the game mode you want to, you have to do the following:
- Check your KTX.CFG (line 59)
- The setting is set k_allowed_free_modes and it obeys a bitmask
- Modes Are:
- 1on1 = 1
- 2on2 = 2
- 3on3 = 4
- 4on4 = 8
- 10on10 = 16
- FFA = 32
- CTF = 64
- Example 1: Server with all possible modes allowed:
- 1 + 2 + 4 + 8 + 16 + 32 + 64 = 127
- set k_allowed_free_modes 127
- Example 2: Server with 2on2 and FFA allowed:
- 2 + 32 = 34
- set k_allowed_free_modes 34
I'm getting "failed to validate client ip" error message from my server, what should I do?¶
By default our package/example configs use method called getrealip to resolve real ip-addresses of the players. This behaviour can be changed from the MVDSV.CFG and the variable is called SV_GETREALIP. With the default configuration you need to make changes to your portX.cfg files, otherwise people can't connect to your server.
- Files that require changes: qwserver/ktx/portX.cfg or qwserver/ffa/ffa.cfg files
- Setting that requires changes: sv_serverip:port
- LAN: Specify the local ip-address
- WAN: Specify public ip-address (internet address)
- PORT: Specify the same port as you used to launch the server
- Examples:
- LAN: sv_serverip 192.168.0.10:27500 (an example, LAN ip-addresses can vary from 10. to 192. etc)
- WAN: sv_serverip 91.121.30.193:27500 (qw-dev.net ip-address, do not use this but your own ip-address)
- SV_GETREALIP can be disabled, HOWEVER:
- 1) If you ban real IP, player using proxy will bypass the ban (not a good thing)
- 2) You can't check real IP from logs or from console leaving abusers anonymous (retarded)
- 3) If you ban proxied player, you ban the whole proxy (just plain stupid)
What does this all mean? It means that you should NEVER disable getrealip, instead configure your server properly with your server's IP-address like it was described above. If you have NAT, then use the public IP-address and not your local IP-address so people can join.
sv_logdir doesn't seem to work?¶
NOTE: THIS ARTICLE APPLIES TO MVDSV VERSION 0.28-RC1 OR OLDER! MVDSV release 0.28 or newer does not have this limited functionality, but changes to the command line are required! The old way: ./mvdsv +gamedir ktx +sv_logdir logs +logcommand1 +logcommand2 The new way: ./mvdsv -game ktx +logcommand1 +logcommand2 (specify sv_logdir somewhere in your configs)
There are some limitations about logging and changing the logdir. Basically you should specify the logdir first and then the logging commands. We are thinking about this issue and what to do with it but in the meantime one should do the following to get the logdir work properly
- On the cmdline, specify sv_logdir before log-commands
- Example: command line
./mvdsv +gamedir ktx -port 27500 +sv_logdir logs +logplayers +logrcon
- Use server.cfg, add the items in particular order
- Example: server.cfg
exec mvdsv.cfg // server settings exec ktx.cfg // mod settings exec pwd.cfg // password settings exec vip_ip.cfg // vip ip settings exec listip.cfg // BANS :) setmaster qwmaster.ocrana.de:27000 satan.idsoftware.com:27000 kubus.rulez.pl:27000 sv_logdir logs logplayers logrcon
How do I compile KTX on Linux 64bits?¶
- For now use the command
make dl32
after configure when compiling.
It does not compile under 64bit OS after all!¶
- If the error message refers to missing stubs-32.h
- Required libraries are: libc6-dev-i386, possibly ia32-libs