User panel stuff on forum
  40 posts on 2 pages  First page12Last page
Server Talk
2012-07-29, 12:20
Member
31 posts

Registered:
May 2008
Thanks. But how do I compile it. There is no .config and 'make' doesn't work.
--------
iO!
2012-07-29, 15:47
Moderator
1329 posts

Registered:
Apr 2006
Unfortunately the directory structure of the MVDSV sources was changed to shitty at some point when I was still in the project, but I didn't do anything about it and it is still anything but good (IMO of course). Anyway, after getting the source you can compile it by going to directory:


mvdsv/build/make


You should see configure, Makefile.BSD and Makefile.GNU there. So do the usual ./configure and then make and it should work.

(Edited 2012-07-29, 15:48)
Servers: Troopers
2012-07-29, 19:17
Member
31 posts

Registered:
May 2008
Thanks, it compiled. But now I am getting this error:
./mvdsv -port 27501 +gamedir ktpro
============= Starting MVDSV =============
32.0 megabyte heap
QuakeWorld Initialized
MVDSV 0.31-dev, (build 0) (Linux)
Build date: Jul 29 2012, 21:11:48
MVDSV Project home page: http://mvdsv.qw-dev.net

execing server.cfg
Unknown command "sv_aim"
execing maps.cfg
execing ktpro.cfg
usage: localinfo [ <key> <value> ]
execing vip_ip.cfg
VM_Load: "qwprogs"
ERROR: SV_Error: PR_ExecuteProgram: NULL function



(Edited 2012-07-29, 19:20)
--------
iO!
2012-07-29, 23:12
Moderator
1329 posts

Registered:
Apr 2006
KTPro? Almost every server uses KTX as standard QW-mod, you should be doing the same unless you have some reason in running KTPro.
Servers: Troopers
2012-07-30, 09:23
Member
31 posts

Registered:
May 2008
It looks like since the last time I was involved in QW (2005), all pages and download links died. qw-dev.net doesn't work, and even this forum went 5 steps backward with this new look like from q3 portals popular in mid-2000s created by 15-year-olds.

Anyway, I was unable to find any working link where I could download KTX.
--------
iO!
2012-07-30, 09:47
Moderator
1329 posts

Registered:
Apr 2006

git clone http://qw-dev.net/git/ktx

./configure & make dl

The qwprogs.so compiled goes to your qwserver/ktx directory (there are some cfgs too like ktx.cfg and mvdsv.cfg in the same directory).

By getting the source you will also get pre-configured server package (or "example configs" if you will) without any maps and obviously no PAKs are included due to copyrights. These files are located in:


ktx/resources/example-configs


Basically just copy that example-configs dir to something like qwserver or whatever you want. Unfortunately there is no help-file or readme included, it is in the "real" server package that obviously can't be downloaded at the moment.

I can help you with that anyway, you want to configure these files:

vip_ip.cfg
pwd.cfg (very important!)
port*.cfg (make sure sv_serverip is properly configured to your external ip address)


(Edited 2012-07-30, 09:49)
Servers: Troopers
2012-09-11, 15:33
Member
950 posts

Registered:
Apr 2006
QW-DEV is now fixed: http://qw-dev.net
2012-09-11, 15:36
Member
950 posts

Registered:
Apr 2006
Renzo wrote:
Unfortunately the directory structure of the MVDSV sources was changed to shitty at some point when I was still in the project, but I didn't do anything about it and it is still anything but good (IMO of course). Anyway, after getting the source you can compile it by going to directory:


Funny thing how people can't read a simple file in the root directory of a project.
Check the ABOUT content
2012-09-11, 15:45
Administrator
1022 posts

Registered:
Apr 2006
deurk wrote:
Renzo wrote:
Unfortunately the directory structure of the MVDSV sources was changed to shitty at some point when I was still in the project, but I didn't do anything about it and it is still anything but good (IMO of course). Anyway, after getting the source you can compile it by going to directory:


Funny thing how people can't read a simple file in the root directory of a project.
Check the ABOUT content

It looks pretty reasonable except for the fact that the build dir usually (as to what I'm used to) actually contain the _built_ stuff, and you place your configure scripts and Makefile in the root dir.
2012-09-11, 20:56
Member
950 posts

Registered:
Apr 2006
Seems to me that the "bin" directory usually has the built stuff in, but I guess there is not only one right way to do it here. It seemed better to me than everything thrown in the middle of the same directory.
  40 posts on 2 pages  First page12Last page