FuhQuake

fluffy · Joined: 28 Feb 2004 Posts: 9

Have run a couple of servers with headhunters and Painkeep mods, but having difficulty serving the maps to users who connect and try to download the modfiles...
models, wavs etc all download fine, but the .BSP files are another matter.
The headhunters server.txt says that .bsp downloading is disabled by quake (to protect Commercial mods) unless the mods PAK files are unpacked into the mods gamedir. I've done this, and even chucked the maps dir into id1 and qw dirs also, but it still refuses to serve them to clients who connect !
server variables allow_download, allow_download_maps etc are all set to 1
tried with zqds, mvdsv and qwsv2.3x, all with same result

Any ideas as to the problem / a solution?

Mick · Joined: 05 Apr 2003 Posts: 151

because its a mod u need to have bought I think
_________________
mick.starthotel.dk
#zfl #quakeworld #fuhquake #serv-u

fluffy · Joined: 28 Feb 2004 Posts: 9

Mick, i dont think thats the case - both Painkeep (teamEvolve) and Headhunters are freeware.

The Headhunters server.txt specifically informs you of this so that you can overcome it to allow clients to download the bsp's...

"You must also unpak your pak0.pak in the hh directory so
clients can download the levels also. Quakeworld prevents the
downloading of bsp levels unless the pak file is unpaked due
to the commerical add-ons from Ritual and Rogue."

I've done the above yet .bsp's still cant be served to clients.

Spike · Joined: 19 Apr 2003 Posts: 144

It depends where quake finds the file first.
I'm not 100% sure, but I think quake will be finding the map within the pak file before it looks outside with the same game dir.

allow_download_pakmaps 1
is the simple solution...
But ideally you would remove the bsp files from the pak files entirly, as this maintains the commercialness of id's maps.

fuh · Almighty King Joined: 07 Sep 2002 Posts: 2086

ye go with allow_download_pakmaps 1

fluffy · Joined: 28 Feb 2004 Posts: 9

Cheers guys!

Wasn't aware of the allow_download_pakmaps variable, which worked just fine.

Also i hadn't considered the situation where if the mod pakfile was still present in the mod dir, Quake might not actually go so far as to check for the presence of unpacked versions of the maps - this turned out to be the main problem...
Remove/rename the mod pakfile after unpacking it and ... voila!

D'oh! what a twonk