need help URGENT


(Thanatos) #1

ok here’s what i want to do:

i want to bind a key and then that it says a vsay, then waits for few secs and then says another.

i got this far:

/bind x “vsay_team takingfire; vsay_team medic”

the problem is that it says both vsays at the same time.

then i tried:

/bind x “vsay_team takingfire; wait10; vsay_team medic”

and

/bind x “vsay_team takingfire; wait 10; vsay_team medic”

but the wait thing doesn’t seem to work anymore.

HELP ME PLS!!!


(Rockford) #2

I could be wrong, but aren’t the wait times in milliseconds? If so, you would need more than 10 to have both vsays play in full.


(Sauron|EFG) #3

I actually think the wait time is in frames, so “wait 76” would wait one second if you had a steady (capped) 76 FPS.

I could be wrong though…


(Rockford) #4

Yeah, I don’t know. At any rate, a number higher than 10 would be necessary.


(Kendle) #5

Try wait 100 at least. Might be able to get it down lower, like 60 - 80 maybe, but probably not less than that.

And yes, wait is in frames, so it’s entirely system dependent. I cap FPS at 43, so wait 43 would be 1 second for me. For someone with an FPS of 86, wait 43 would be half a second, etc.


(pack) #6

doesnt vstr +vstr worsk in et (some rtcw osp thing) ?


(Thanatos) #7

ok it’s indeed fps dependand.

wait 60 (yeah i’m one of the few that dont have fps problems) worked really fine for me.


(IPvD) #8

Doesn’t wait freeze your player when you do it, or somehow impair your movement? Is there a better way to dispose of timing functions in ET?


(Thanatos) #9

yes it does freeze you but that’s on such short time that it’s irrelevant.

and in my bind it doesn’t matter anyway. the bind i made is for when i died in combat and need medic.
final bind version:

/bind x “vsay_team takingfire; wait 80; vsay_team medic; wait 80; vsay_team ftreviveme”


(O2.iceman) #10

gawd would hate to be playing in a server with you, getting spammed with 3 vsay’s every time you die.


(BoomStick) #11

and this is urgent because?


(amazinglarry) #12

Well he got you to look at the thread right? I think that was the point.


(BoomStick) #13

eh guess ya gota point :banghead: