multi_manager (Half-Life) Last edited 16 years ago2008-04-26 14:57:15 UTC

Multi_managers and looping note:

If your using an MM as a continuous loop (by having the MM call itself at the end of it's routine), it will only loop if you have the "multithreaded" flag checked!

"Maximum of 16 individual targets. "

More like 8, to keep it safe. Check out this thread for more info! = )

Pay attention to the "Game crash" warning as it is the usual case of map crashes when using this technique.

Also don't forget to make the start time 0.1 and not 0, as 0 can cause the map to crash and/or other game bugs.
That said, when deactivating something, lets say:

00laser1 0.1
00laser1#1 2.1
00laser1#2 ??

Do NOT start it after it is deactivated (00laser1#2 2.1), give it 0.1 seconds freeze time (or more if you need it):

00laser1 0.1
00laser1#1 2.1
00laser1#2 2.2

And remember not to use long entity names, for example (i use):

0lsrmm (Laser control multi manager)
0expmm (Explosion control multi manager)

Proper looping:

Proper looping is done with an env_beam repeatedly shooting through a func_button with health = 1. info_targets must sandwich the button. The button activates the multi.

The env_beam must have damage set to >=1. Change Strike again time to set the loop frequency.

Note: You'll lose the activator (current player) reference.

multi_manager supports triggerstates, by default its use-type is "Toggle".
Add a "#x" at the end of the value, where "x" is the triggerstate value:

"0.001#0" means to trigger via use-type Off after 0.001s
"0.001#1" means to trigger via use-type On after 0.001s
"0.001#2" means to trigger via "killtarget" triggerstate after 0.001s

multi_manager is basically a trigger_relay now with this knowledge!

I think that's Sven Co-op-specific, isn't it?
opens up the code
Yeah, there's nothing in HL SDK that points to the parsing of #N there. It is always USE_TOGGLE. Either way though, good to know!