Guess who gets to take his work with him?

naa i cant.

Guess why were saying guess infront of everything we post

Guess which one will win, HDoan's H2 Pelican or Killas H2 Phantom

It flies, it faps its wings, blood explosion, and it moves its head. Now we know what the bird looks like close up in Halo 2.

See what I did there? Replaced flaps with faps

now it may seem stupid to ask but will you be using the Halo 3 masterchief bipeds and backpack weps? and will there be a flamethrower in the map

Just a little too boxy on the rifle. And put in lower in the HUD.

Yes, it was a stupid question, but I'm not going to be mean with you. I'll only say what Halo 3 team would use a Halo 2 biped? Backpack weapons are also being used according to pictures some time ago of a rigged Halo 3 Master Chief biped.

Your sentence was basically the same as what I said anyway.
Edited by ODX on Mar 16, 2008 at 08:43 AM

And you can send me one to. Mr kill360

WE WILL NOT BE USING BACKPACK SIDEARMS INSTEAD WE ARE USING PERMS.

I have also fixed boxyness on the rifle.
Edited by aklass on Mar 16, 2008 at 11:13 AM

so you would rather have to faultly weapons on your ass than be a jawsome new h3 chief with differnt armors like the eva?

yhea it was the first thing I noticed

WTF is that? a schnauzers retarded friend?

why have glitchy weapons that are still on your back when you die? When instead you can have a masterchief that has all the different armors available in h3?

The reason why it stays on your back is because you can't refer to a dead player using "players" to change the permutation back to having no weapon in the backpack, right? If that's the case, then I think you could use global variables to give each dead player something to be referred by:

(global object player0 (list_get (players) 0))
(global object player1 (list_get (players) 1))
(repeat for each player index)

(script continuous set_players
	(if
		(> (unit_get_health (unit (list_get (players) 0))) -1)
		(set player0 (list_get (players) 0))
	)
	(if
		(> (unit_get_health (unit (list_get (players) 1))) -1)
		(set player1 (list_get (players) 1))
	)
	(repeat for each player index)
)

Then, you could continuously check for each player's health to be <= 0 in a seperate script using the variable instead of (list_get (players) #), and change the permutation to having no backpack weapon.

If you can't set the permutation of a dead player, what makes you think you can set the permutation of an instance of a dead player? Your script is redundant because in the end, you're still referencing the same object you began with.

Isn't that what we want? The script is set up so that it only sets the variable if each player index is currently alive. That way, each variable remains set to the dead player until he respawns, which is enough time for a continuous script to set the permutation for the dead player.

When a player dies, the corpse loses its status as a "player" object, and therefore, the player effectively does not exist until he respawns. How are you going to assign a non-existant object to a variable in the first place?

Right, which is what I'm trying to counter with the variable. I can only assign the player object to the variable if it's alive, so the moment it dies, the script no longer sets the variable to the index, because it would return nothing. Instead, the variable was already set to the player's object before it died, meaning that the variable is still set to the dead player.

The variable won't lose its value based on the (players) index anymore because the script no longer assigns the variable once the index is considered non-existent for that moment until the player re-spawns.

A variable does not store an actual object, it stores a reference to an object (with the exception of primitive data types such as integers, etc). So, if you assign say, "(unit (list_get (players) 0))" to a variable, when you call that variable, the engine will evaluate what you assigned to it (more or less; it actually holds an address to the object)--in this case "(unit (list_get (players) 0))", which will return an undefined object as you called* it after the player died. It simply will not work. A variable will not hold an actual object. That would be far too costly at runtime and would be redundant anyways.

*fixed something
Edited by CtrlAltDestroy on Mar 16, 2008 at 02:51 PM

Oh, ok. I thought the purpose of those kinds of variable types was to actually store their value, not the reference to it. I see now.
Edited by Me KS on Mar 16, 2008 at 03:04 PM

Less backpack, moar birdie at the top.

Better shaders, again.

less challenging CAD to scripting contest. More...... WTF does that birdie have to do with MP?

We could have it flying in the sky and you can shoot it down but it cant get to you =D Like in Halo 3 on Guardien theres birds or this other level with sentinels.

He can be a spy pigeon. That can spy on the other team. :D Lol but seriously that bird has no purpose.

Just let it fly free in the sky until a sniper gets bored =/

But then that sniper is spotted and killed. Hmm more of a nuisance than a un-boarder>>

or maybe u could have a contest on who can shoot the most birds?

Duck Hunt ce

good idea

Actually the whole point that birds were invented were to shoot them. I like the idea of having them flying around in the air. Makes the map special.

i think it would be fun

how will the birds sync online though?