I just time it to 4 secs, but this sounds like an easier way. 

for the minpitch and maxpitch values that might come in handy someday 

then you life in a slow world, in my world they explode after 2.5 :) 

My input on quoth was almost nil, apart from a few maps.

Hope you like space hulk :) 

Example map using Quoth info_command
60 seconds of speed

http://www.mediafire.com/download.php?tb0t1vaw3bxhz67 

That's cool. People who have cl_sidespeed and cl_forwardspeed set low may not feel the full benefit of the powerup - but be careful about changing those values to fix it! The danger is in trying to restore them correctly to whatever the player prefers. I think the closest to a good way is to send "exec config.cfg" to the player at the end of the powerup - this restores the values to what they were at the start of the session (with the minor side-effect of also resetting anything else the player has changed this setting ...)

Finally, the powerup won't work correctly in co-op as it is. Is there a way to make it only affect one player? I'm hoping negke might take a punt at that question... 

Preach I agree. I was going to change fov also. fov 60-70 but what to set it back to? exec config.cfg is a good idea. Things like r_wateralpha I think are ok for a map to mess with but fov and others maybe not good. I also think the idea could be extended to a custom file exec custom.cfg to create a custom environment. Setting back to "normal" will be the trick. A way to write all cvar's to file before messing around would be good.

BTW Preach how is the Quoth update coming along? 

I know in darkplaces you can use variables and set command to temporarily save the value of a cvar.

here is an example:

//=============start of example==============
//save current user-set value of cvar
set fov_value $fov
set sen_value $sensitivity
set sound_volume $volume

//change cvar value to whatever you want
fov 999
sensitivity 1000
volume 9999
playdemo demo1

//restore user-set cvar value
fov $fov_value
sensitivity $sen_value
volume $sound_volume
//=============end of example============== 

Yeah, new version is feature complete, it's just the testing and fixing any bugs that have arisen. It's not helped that people keep releasing maps for Quoth faster than I can complete them twice on easy and nightmare. 

new quoth?

GIEF SHINY NEW TOYZ PLZ 

I want to say "the flashlight meter sucks anyway", no offense. Could make it faintly beep or flicker when the battery nears its end -- absorbing the UI element into the game itself.

I always found the flashlight meter to be one of the less polished elements of Quoth. Slapping that consolefont all over the middle of the screen seemed distracting to me.

The less HUD, the better, IMHO. 

flashlight would only be usefull in combination with a magnifying glass so you get a laser like weapon :) What the idea behind the flashlight anyway?i cant think of any uses for it except using it as a melee weapon (no i wont ever come down from my fullbight cloud) 

Does that mean you always play in Fulbright? 

is a little bit of a weird addition IMO.
I can't see myself ever making a flashlight map unless its functionality was more like Half-Life. 

Just an extra option. Agree with go re flickering rather than countdown bar on screen. 

dotn see any reason not to, if i want to see beautifull stuff its not a videogame :) 

This discussion about whether the flashlight should be removed or reworked is kind of getting away from the point I was trying to make, which makes me worried that I didn't explain myself well. The flashlight is one example - the most visible one but by no means the only one - where there is a contention between a resource the Quoth code assumes it controls and the resources that the SDA code assumes has sole control of. This is why they are hard to integrate together. 

I never run out of battery power anyway. 

you should make the battery one of those crank ones... that way you can add a battery crank mini-game using quicktime events. ;) 

zaikor