Is there any bundle available for very easy installation on new server?
Like latest mvdsv + latest ktx + decent ktx config (all modes unlocked) + all modern maps + qwfwd ?

Sometimes there are different admins who agree to install qw server but they do not want to read a lot of manuals and just want to do /make install .

Right now I am looking for this package to install it on Red Hat Enterprise Linux 5.x .

Both KTX and MVDSV have their own git repository for the latest source code. Afaik QWFWD is still placed in a sub-dir of mvdsv SVN repo.

In the KTX git repo there are example configs, the only thing you need is a map pack.
I dont think there is a bundle with the latest stuff since the repo is updated almost daily.

#qw-dev , look for deurk, he can help you out

Good luck, shoot if you have any questions.

//dimm

Let say tomorrow I will buy a linux virtual server.
I am able to download putty and do ssh to it.

What should I write in console to install couple of 1on1/2on2/4on4 ports on 28001 and 28002 and qwfwd on port 30000?

I have no clue what is git repository, SVN and vim.
I can just do couple of wget, ./make install and change rcon password and want to spend maximum 5 mins for the installation.

Is it possible?

Can some server admin host his cfgs, maps currently used on his server and wrote some installation tips?

Are you serious? You really didn't check the sticky topics on this forum before you made this thread?


The "latest" version is still MVDSV 0.29 and KTX 1.36, and yes, you have unzippable package that requires only changing some passwords and the configured ip-address. It is all well documented in the installation help that comes with the installation package AND on the KTX site.


As for the "latest", unreleased SVN builds, you are going to need to compile them on your own, or use deurk's builds that get done automatically after every commit. I don't remember where it is, so you are going need to ask him for the URL.


You are going to need both PAKs as we will not be sharing copyrighted material on the server package. The server package doesn't ship with maps either, as it would make the download really big and it's something we didn't want back in the day. It would only make getting the server package longer, as making any changes to it and repacking the files. As for some common map-pack, I can't remember if there's any, but I do remember sending one to the project people at some point.

I really did.
I just didn't believe that 2 years old archive contains all cool features like bloodfest, antilag, voice support and so on.
Renzo, can you share somewhere all maps which you use on your servers?

I can send the from my shell, for example using dcc on irc. Sending them via my own line would take an eternity, even if I pack them somehow.

Just checked my local map archive.
I have 84 maps 55mb. Compressed with 7zip to 14MBs.
Can you upload it to some resource like zalil.ru ?

And what about antilag version of mvdsv+ktx?
Is it available somewhere? (I don't think that "latest" version from sep 2009 have it)

And can you share qwfwd.cfg ?
There are no any cfg in qwfwd folder .
http://qw-dev.net/projects/qwfwd/files

http://qw-dev.net/projects/qwfwd/repository/entry/EXAMPLE_qwfwd.cfg

It doesn't, since its the latest "release". If you want the other you just do as Renzo said.

I mean, you can't expect people to help you if you don't care to learn something new at all?

There is also the possibility of getting latest code already compiled (if it fits your environment though);

MVDSV: http://build.qw-dev.net/mvdsv (don't get Windows one, it doesn't work yet)
KTX: http://build.qw-dev.net/ktx

Maybe those urls need to be added to the project sites, as I don't see it there.

Also a word of caution: using MVDSV or KTX that has been compiled on a foreign system can cause issues. Unlike you would think, they might not even start at all. We have seen problems with certain armor pickups (at least) on systems that use binaries compiled elsewhere. I personally have seen totally unworking builds on many occasions when I was forced to use one system to build binaries for 5 servers.

The safest bet is to always compile binaries on the system you intend to run them.

Actually, it is not about me. New servers will not help me personally.

I started this topic because it is third time during last year when different people agreed to install new qw server but I was unable to find any source with installation package of antilag version of mvdsv+ktx.
In both previous cases I just thought "OK, lets wait a couple of months and it will be updated with some stable build", but it never does.

I just think that if someone create a small manual of how to install uptodate version of qw server and proxy, it will helps the community.

OK. There are a small installation instructions.
Any comments, links for maps or ktx cfg will be very useful.

Get latest official bundle of mvdsv and ktx:
http://qw-dev.net/attachments/download/214/mvdsv_0.29-ktx_1.36-server_pack-glibc_2.3.5.tgz

tar zxfv mvdsv_0.29-ktx_1.36-server_pack-glibc_2.3.5.tgz

update qwserver/mvdsv:
http://build.qw-dev.net/mvdsv/latest/linux_x86/mvdsv

or build it:
svn co http://qw-dev.net/svn/mvdsv/trunk mvdsv (MVDSV + QWfwd sources)
After this navigate to mvdsv/source/
Use ./configure && make to compile

replace qwserver\ktx\qwprogs.so with
http://build.qw-dev.net/ktx/latest/linux_x86/qwprogs.so

Any ktx config update to enable antilag, bloodfest and voice support?

Edit qwserver\ktx\pwd.cfg to change rcon_password, master_rcon_password and k_admincode.

Download a mappack fro the server from: NEED URL.

execute 2 ports:

./port1 > /dev/null &

./port2 > /dev/null &

download http://qw-dev.net/projects/qwfwd/repository/entry/EXAMPLE_qwfwd.cfg
If you didn't build mvdsv from latest sources, you can download qwfwd from:

http://qw-dev.net/attachments/download/219/qwfwd_04_10_2009_SVN_glibc2.3.5.tar.gz
Copy EXAMPLE_qwfwd.cfg as qwfwd.cfg to the directory where qwfwd.bin is

Edit qwfwd.cfg file if required, you will probably wish to set a hostname at least

./qwfwd.bin >/dev/null &

It will be when it gets out of the setting-up phase. I am still working around it.
I actually started to put things directly on http://builds.qw-dev.net for the time being.