The new package can be found from the old place:

http://mvdsv.qw-dev.net/files

When installing, PAY ATTENTION to the included installation help files or read it online!

These packages are for:

Windows 32bit versions
Linux 32bit distributions

They contain the very latest configs and release versions of both MVDSV 0.28 (build 793) and KTX 1.35 (build 817).

quake-ffa = (presumably) FFA server
quake-install = ??

:-)

other comment, if you extract both .tar.gzs to a server then installation.txt from the second overwrites the first

no vwep models included in either package, should be included in both and enabled by default on FFA server

Will be when packs are officially on KTX websites.

ok, any ETA on that? :-)

also


no mvdfinish.qws script included in the pack?

I know, this has been there for ages... Will take it away or put an example there.

ETA for packs to be up is 2-3 days tops, let's say end of week-end

no worries, i guess you'll be busy watching the RWC 3rd Place Playoff on Friday ;-)

i'd suggest you get .mvd gzipping on the server installs via sv_onrecordfinish

at least add 'master.quakeservers.net:27000' to the master server list in the config, and probably may as well add the full list of active qw ones from here

also the FFA package needs a proper map rotation setup

for reference (from the xs4all thread)

Will do.

No. The package creates qwserver directory and the installation helps for both ffa and allround.

UPDATED: 26.1.2008

Perhaps the both packs should contain quake-install directory too, but I figured that FFA should be extracted on your existing server directory, not the home dir.

It is an optional script. There is no reason for everyone to use that script, only if they want to (not by default!).

Last time I checked from Mli, the QuakeServers.net master does not accept heartbeat from the servers as it only reads qs.net database, but I'll ask him.

About maps... every server admin should decide on the maps themselves. We could give them some map rotation, but in the end they would end up doing that on themselves -> let them just figure that part out, they have the example there.

Yep, master.quakeservers.net and asgaard.morphos-team.net do not accept heartbeats from servers. They just download a .txt file from QuakeServers.net and broadcast server addresses from that. You'll need to bug Bigfoot (asgaard) and Zalon (master.qs.net) to get heartbeat support to those masters.

What about me setting up a master server that accepts heartbeat from servers?

Would be great if it also could display servers from http://www.quakeservers.net/lists/servers/global.txt .

Taking any conf you want me to put up

Why do a new masterserver when we already got 2 custom ones already done. That would just be a complete waste of time.

We could easily make master.quakeservers.net take heartbeats, we just did not do that at first, since we did not think anyone would use it (the heartbeat function).

Well point was to allow heartbeat. I don't NEED to have one up.

The point was to make servers be able to give their info to the master server. If heartbeat is something else then I chose the wrong word. If it's the correct term then can you add the functionality?

Yes, we can make the masterserver accept heartbeat signals from servers, as i said before we discussed this when we did the server, we just did not think anyone would want to use it, since all servers was already in the quakeservers.net database.

any new on when these are coming now that 1.34 is out? are you waiting for matching stable mvdsv release before making them available?

Yes, I'd like to have a fixed mvdsv (even if it is tagged as unstable) before releasing the pack.

Completely missed this topic. I am the person who made the pseudo master server running on Zalon's VPS at master.quakeservers.net. I'll look into adding heartbeat support when I get the time, though right now it's just built as an alternative to keeping an updated server list on file. I made it mostly through reverse engineering with a packet sniffer plus some partial documentation that I found through Google. If this heartbeat functionality is simply acting like a "real" master server and adding/removing servers to the internal list as heartbeats come and go, I agree with Zalon. Not much point in it, since there is plenty of active master servers already, or am I mistaken? If it's not, what will this being "able to give their info to the master server" help? Please enlighten me.

Anybody?

can't get the package.. files doesn't exists

where can i get it now?

http://files.quakeonline.net/servers/linux_mvdsv-ktx.tar.gz

thanks...

i wanna create a KTX server in windows..

i have ...

-KTX 1.34 (qwprogs.dll)
-MVDSV 0.28-beta, build 714 (w) (Build date: Oct 31 2007, 23:58:14) (obs: I had to create a folder called QW with file qwprogs.dat, take it from other quake folder)
-have too, the configs files from the package...

the cmd line is --> mvdsv_i386_win.exe +gamedir ktx -mem 32

in the client side ..
-eZquake 1.8.2 Stable (build 2029)

but when i connect to the server.. it is not in ktx mode... can't see the MOTD.. can't write commands.. etc..etc..

what's happens??

i need other thing?

does it help to have this cmd line? mvdsv.exe +gamedir ktx -mem 32 (delete the _i386_win crap)

thkns for reply... i did it, but it was not the solution...
well.. finally i put the package (linux) in new folder ktx...
and launched with port1.bat

with this cmd line works... maybe the default port 27500 have a restriction

mvdsv.exe +gamedir ktx -port 27501 +logrcon +logplayers +exec port1.cfg

...
i have another question.. when i created the server and tried to connect.. in the console of ezquake shows "Failed to validate Client's IP"
what is this shit?

--- (sorry.. i have two years out the arenas... you have a lot of new things.. it is amazing!! Quakeworld doesn't stop!!!
gangster from sudamerica - Chile)

EDIT!!!
i found the problem..
when i set "sv_serverip 192.168.0.1:27501" with the real internal ip (lan 192.168.3.10:27501) the message "Failed to validate Client's IP" disappears ...

You probably have wrong sv_progtype in configs. It should be set to "0" for qwprogs.dat ("1" is for .so or .dll and "2" for .qvm).

so i guess sv_progtype 1

yes yes, perhaps if i looked better I might've seen the sticky with 'ktx 1.34 released' which eventually links to the ktx website. But I didn't and thought 1.34 was the latest version for a while now. Maybe put a link here to the KTX website as well and remove (or update) the KTX server packages from the mvdsv website.

But it is. There is no official or stable release of KTX 1.35 (even though my releases are stable).


Um, no.

The server package is recent enough with really new builds from SVN. If not, you can always 1) compile them yourself 2) download precompiled binaries from MVDSV or KTX downloads section.

And when we are talking about "server" then it has to mean MVDSV since KTX is only a mod. Therefore "server" packages can be downloaded from "server" downloads section in addition to the pre-built binaries.