Alright, so in a multiplayer map, if I wanted to create a script in which it sleeps until two players are inside a trigger volume, how would I set up the if part of the script?

well um i would usume that you known about dormant scripts and it is kinda hard to explain and i havnt tried scripting trigger volumes in mp and so ill just give a example script of what ide think sould work:



but the thing is im not sure on how to make it so both players have to be at the exact time unless the trigger was infront of a locked door and there was no gap between the door and the trigger volume like so:



and you could add more dormant script if you wanted it to have more players to be in the trigger volume, but this would work with 2 players at best because with more players like 3 or 4 and player 3 made it to the trigger volume before player 1 (0) it would not wake player 2 so it would have to be in order player 1, 2, 3, 4 to reach the trigger volumes so i would reccommend using just 2 players and even then it would not work always like player2 could beat player1 to the trigger and it wont wake. (if only Bungie added script that would sleep a woken script)

PS. You may have to change the script a bit and fiddle around with it to get the best result and of course to make extra stuff happen.

Isn't there an "and" command? Something you can use after an if? Because I want to create a continuous script (don't ask why).

i think there is... If there is ive never used it before and wait no i dont wanna ask why

I would assume you would use something similar to the door opening script for multiplayer campaign. I am not a scripter so I don't know the basics.

thats the device_set_power and device_set_postition that i used in my 2nd quote. 1.0 mean open and 0.0 mean closed or locked

Doesn't matter now. I found it. For anyone who's interested, it's this:

(script continous script
(if
(and
([parameter])
([parameter])
(true
(begin
([stuff])
)
)
)

keeping that for reference.

If you actually want to test for any two players at the exact same time, you'd have to use a combination of "and"s and "or"s for each possible combination of players from 0 to 15. Which means 16 players possible as the first player in the trigger times 16 players possible as the second player in the trigger = 256 tests....

Of course, nobody in their right mind has the patience to copy-paste the same lines of code 255 times and change the numbers. Neither do I. I forgot I made this when I read the topic a while back:

(global short plyrnum 0)
(global boolean first_is_in 0)

(global object first_in (list_get (players) 0))
(global object second_in (list_get (players) 0))

(script continuous "name"
	(if
		(and
			(volume_test_object "volume" (list_get (players) plyrnum))
			(= first_is_in 0)
		)
		(begin
			(set first_in (list_get (players) plyrnum))
			(set first_is_in 1)
		)
		(if
			(and
				(volume_test_object "volume" (list_get (players) plyrnum))
				(= first_is_in 1)
			)
			(begin
				(set second_in (list_get (players) plyrnum))
				(if
					(!= first_in second_in)
					(begin
						(set first_is_in 0)
						"insert any commands here"
					)
				)
			)
		)
	)
)
		

(script continuous plyrnum_manage
	(set plyrnum (+ plyrnum 1))
	(if
		(> plyrnum 15)
		(set plyrnum 0)
	)
)

It uses the plyrnum idea from the backpack script and waits for one player to enter, then sets a variable to that first player. Then it waits for a second player, sets another variable to that player, and then checks to make sure both variables aren't set to the same player in order to conclude that two different players are in the volume and then take action. It then repeats the test over and over by setting the boolean back to false. You can make it test only once if you want by getting rid of the line (set first_is_in 0) near the end of the last "begin".

It doesn't check for two players at the exact same time since it has to cycle through the player indexes with the whole plyrnum deal, but it's still fast enough to be reliable.

I'm not sure if the (!=) test works with "object" variables, this isn't tested, I just thought it through. If you think it might be useful, test it out. If it actually works, sweet.
Edited by Me KS on Mar 6, 2009 at 11:23 PM