ProQuake 4.91 Beta

[Mr.Burns]

I think peg once asked me to add multiple urls for the autodl, so if 1 server didnt have a map then it could check another.

My apologies. Judging by some of the comments perhaps I didn't explain it clearly, but that was the same suggestion that I was trying to make. Just to be clear, I wasn't suggesting that the user should have to do anything, it wasn't intended as another option that they have to familiarise themselves with and set. Merely have the secondary URL, a pre-set failsafe if you will, already sitting in the background quietly minding it's own business until the user wishes to download content seemlessly. When that happens if they have put in their preferred download URL in (and enabled DLs) then it should try and DL the content from there. If it fails or if the user has no DL URL set and the client is going to try and DL content regardless (as is the case here) then perhaps it should revert to a default URL so it at least goes somewhere. Like I said, it doesn't make a lot of difference to me personally, I was just trying to be supportive in a constructive way.

I'm fully in agreement with the points about simplicity, load and go though and not overloading people with what could be considered as unnecessary options, I know from many years of personal experience how frustrating and thankless that can be at times from a developer's perspective.

But hey ho, twas but a humble suggestion perhaps I shouldn't have said anything, we'd better move on...

Kind regards

Monty

[R00k]

I think peg once asked me to add multiple urls for the autodl, so if 1 server didnt have a map then it could check another.

[MH]

The major problems with options are:

What should the default be?

For every one person who wants something enabled by default, there is guaranteed to be another who wants it disabled. No matter what you do you're going to have someone complaining at you. Even the tactic of "when in doubt do what id Quake did" doesn't work - people will still complain if e.g. r_wateralpha doesn't get saved to their config (and if it does they'll complain again next time they load a map that isn't vised for translucent water). And you'll find yourself explaining the very same thing over and over again. Providing options is the beginning of a slippery slope to being expected to be able to pull magic out of your ass.

How do you expose options to the user?

Unless users see that an option is available they won't know that it's there. Some people like command-line options, some like cvars, some like menu options, some like all, some or none of these. Others will be unaware that the option even exists and you'll be constantly asked to provide it. There's no point whatsoever in providing a readme file - people don't read readme files.

Option overload

If you have 50 options to configure something people will just get confused. What combinations do they need to use in order to get what they want? What options work well together? What options clash? What is the difference between sv_my_wonderful_option_do_this, sv_my_wonderful_option_do_that and sv_my_wonderful_option_do_t'other anyway?

[Baker]

It's just a thought but, whilst you're tinkering, perhaps it might be worth also considering trying primary and secondary URLs. For example if the DL fails on the user's prefered DL perhaps try a mirror, in this case the US?

/2 pence worth

Kind regards

Monty

I kinda of don't like the idea of 2 URLs. I don't even like the idea of the option to NOT download locs (and may try to avoid that).

Now here is why:

I don't like options. Less is more. Simpler is better. And I'm trying to keep it that way. I really don't want anyone loading it up to do anything except start playing.

I may load up the ProQuake connection handshake --- to give extra info to supporting clients on what the server settings are. The problem here is more that the client isn't able to act on server settings at connection time (right now).

At a minimum, I'll keep this thought in mind since --- well --- I'm already altering the ProQuake handshake in a both backwards (to prior version of ProQuake and compatible clients .... Qrack for sure) and a forwards-compatible way.

[Mr.Burns]

It's just a thought but, whilst you're tinkering, perhaps it might be worth also considering trying primary and secondary URLs. For example if the DL fails on the user's prefered DL perhaps try a mirror, in this case the US?

/2 pence worth

Kind regards

Monty

[Baker]

I'll put in the option to not try to download the locs, since you guys are doing more FFA DM and don't need them and don't use "our" map depot either.

[Polarite]

Download Link: ProQuake 4.91 Beta. Improvements include:

2. r_colored_bodies 0 turns colored dead bodies off (Polarite asked).
.

Again good job Baker!

That's what I call player input ,thanks for adding this option.

First it didn't work, but then I found out its r_colored_dead_bodies instead of r_colored_bodies.

I'm so accustomed with none colored dead bodies, otherwise I would shoot at the colored bodies the whole time.

All this time that you spend on updating this quakeclient, respect man!
The community can be proud of guys like you.

[Mr.Burns]

Download Link: ProQuake 4.91 Beta. Improvements include:

1. Sounds and .loc files download.

Hi Baker
Very well done on the update. If it wasn't for people like you and Rook keeping this going I wouldn't be able to play quake, so firstly, a big thank you. Secondly, a bit of feedback, I just connected to Shmack and noticed that the autodownload of e1m6.loc failed.

It looks like it's going to Bigfoot (my usual map download source) to get the loc files and couldn't find them.

cl_web_download "1"
cl_web_download_url "bigfoot.quake1.net/"

Update: I've noticed the same thing whilst playing at Bigfoot on custom maps, in fact on every map I try (as you would probably expect).

It's not a problem for me as with my ping / fps / lack of skill I'm usually wanting to run away from opponents like Pol rather than wishing to advertise my position , but other non US players may use them and I thought you should know Maybe have a word in Peg's ear and I'm sure he'll pop the appropriate files on the server for you.

Other than that it seems fine with the very moderate amount of testing that I've been able to do.

(cough, *Cl_mute*, cough )

Hope this helps

Monty

[MH]

Downloaded, did a quick test, all seems well from here.

[Baker]

Download Link: ProQuake 4.91 Beta. Improvements include:

1. Sounds and .loc files download.
2. r_colored_bodies 0 turns colored dead bodies off (Polarite asked).
3. Windows stickykeys is handled like DirectQ --- which means it is likely disabled when ProQuake is active.
4. The "Windows" key is handled in the same manner. Disabled while using ProQuake (cvar is gone)
5. Stripped out cd support, ipx support, serial port support, etc.
6. Switched some compiler settings to get the file sizes back down on par with 4.5x file sizes.

Next one will have server browser. Only delay is efess's ProQuake feed is bit a tough to parse, but I can deal with it.

Above should fix a problem Smokey seemed to have with Windows key.