Running list of things Quake should do but doesn't

[Baker]

Boredom warning; leave now if you want to be entertained

Running list of things Quake should do but doesn't.

These aren't very important for the most part, but I wanted to have a list sitting around.

1. Have certain commands disallowed by the server. Unbindall, for example. Probably others. Since few ppl write mods, the risk of something nasty being sent from the client to the server is low.

Plus, unbindall (keys) which does very infrequently get abused can be setup by the engine to either ignore it or request confirmation. For example, ProQuake 3.99r pops confirmation box up on unbindall if a client is connected to a server and a gamedir isn't being used (mod compatibility) and it isn't being done by the startup (exec default.cfg) or from the menu (reset to defaults).

2. Have aliases and cvars set by servers cleared upon disconnect. The former (aliases) can on rare occasions have weird effects when switching from server to server. The latter (cvars) can change player settings in a way they don't want or expect. One example is how servers (ProQuake in cheat-free mode) or mods (CAx) can set r_wateralpha to 1. Then if you connect somewhere WITH transparent water, it is gone and you would have to restore it back.

3. Add to #2, keybinds. Like Gunters "t" rebind.

4. Add to all of the above: settings should be reset after viewing demos.

I think Quakeworld clears server assigned aliases on disconnect.

/Just notes, nothing exciting. I don't pretend the above is interesting, but I want to store it somewhere.

[PapaSmurf]

How about setting up some sort of weapon switching hierarchy on weapon/backpack pickup. For example, I would want my weapon to automatically switch to supershotgun, supernailgun, or rocket launcher when I first pick up that weapon, in that order. I do not want to switch to lightning gun or grenade launcher upon weapon pickup.

Most servers use the default setting, which I believe is the higher the weapon number gets priority. However, on runequake servers it won't switch you to rocket launcher on pickup.

[Baker]

How about setting up some sort of weapon switching hierarchy on weapon/backpack pickup. For example, I would want my weapon to automatically switch to supershotgun, supernailgun, or rocket launcher when I first pick up that weapon, in that order. I do not want to switch to lightning gun or grenade launcher upon weapon pickup.

Most servers use the default setting, which I believe is the higher the weapon number gets priority. However, on runequake servers it won't switch you to rocket launcher on pickup.

Definitely. I hate it when I have the RL and get switched to the LG *OR* don't have the RL and don't get switched to it, but others have the opposite preferences.

[Baker]

Another:

1. Should be able to start fullscreen GLQuake on monitor #2 if dual monitor system
2. Should be able to move WinQuake onto 2nd monitor
3. Ability to detect 2nd monitor, GLQuake uses a rather solid method. I don't know if it will always work.

[IEEE 802.11]

Another:

1. Should be able to start fullscreen GLQuake on monitor #2 if dual monitor system

I vote for this one. My only workaround for that was to change my primary monitor to the monitor I wanted to play Quake on, but it's annoying when I want to go mobile on my laptop. My solution has been to just not play Quake as often.

[MH]

Problem with dual monitor systems is that there are so many different configurations possible, with each vendor having their own interface that (from my admittedly limited experience with them) looks not too far off proprietary.

Two cards.
Single "dual head" type card.
Laptop with secondary output (same as above?)

Hardware accelerated.
Not hardware accelerated.

Stretched across both screens.
A second "virtual" desktop (that just happens to be visible).
Replicated on the second screen.

Requires use of a degraded video mode.
Doesn't require use of a degraded video mode.

Portrait mode vs landscape mode.

That's 36 combinations I make it, purely off the top of my head, and ignoring the last one. The fact that OpenGL leaves this kind of stuff to the OS means a lot of platform specific code in a situation where every setup could reasonably be classed as an "esoteric setup".

[Baker]

Yeah, I briefly looked into ideas for a dual monitor fix and realized it would be super onerous.

Add to list of things Quake should do, but doesn't:

If you play online, I find it super irritating that binds are triggered while in console and in messagemode. This happens ONLY IF it is a -bind.

I don't want any binds being triggered if I am in the console or in message mode.

Consequentially, I have a fix for this that I coded and will be documented later this week. It flags keys where +binds are triggered (+attack, etc.) and only executes the corresponding -bind if the key executed the +bind.

[=peg=]

GREAT! that shit is annoying as hell indeed.. especially with the silly menu in runequake (whoever came up with the idea to use impulse 1-8 for a menu need his head examined )

here is the scenario: you are playing a match and you get killed while firing the nailgun in short bursts to save ammo.. u have a best non explosive bind that happens to be on the nailgun.. and you have an alias for it like +bestnonexp "beastweapon 8 5 4 3 2 1;+attack" .. you die.. you hit the +bestnonexp key and all of a sudden you are in observer mode.. lost all your frags and the match is f*cked up.. (impulse 4 triggers the menu when dead -> obsever).. similar scenario for +quickgrenade -> admin mode.. god i hate that silly menu!!

[Baker]

GREAT! that shit is annoying as hell indeed

Yes, very true. Annoying as hell.

[Baker]

Also:

I think Quake should have a built-in mouse driven Quake name maker.

/But I just finished writing one, so I'll have to remove that one from consideration

[=peg=]

sweet!