Ok I know how to Play other Characters but, I want to play more than 1 biped. So do u respawn as a different character each time u die or something?

Short and, simple No.

so u mean i cant do that?
But like what about the red team a biped and the blue team a different biped?

You, sir, are a complete moron. You know absolutely nothing about modding, so shut your damn trap before someone really good at flaming comes in here and rips you apart. Do not EVER do that again.

@ Notaru

Yes, it is possible. You create permutations in the GBXmodel tag, each permutation being a separate biped. I know there is another way to do it, but I'm not sure.

As for having a separate biped for each team, it is possible only for games where there the team index on spawn points is used. For instance, team slayer would not work, but CTF would. This also requires a lot of scripting I would rather not go on about in length.

You, sir, are a complete moron. You know absolutely nothing about modding, so shut your damn trap before someone really good at flaming comes in here and rips you apart. Do not EVER do that again.

@ Notaru

And you I dont care because im new at modding so just shut up and listen to the code of conduct before u think about posting something like that. (@ Headhunter09)

Headhunter09... chill. You didn't exactly help him any yourself. The cyborg's permutations are locked, and I think they only change the colour anyways. Permutations seem to be variants of the model, not bipeds.

I don't think you actually know the scripting that is required (if any), if you didn't have time then why bother saying you could?

prove me wrong. post some details.

Eh, you know the top part was directed at PVT Jenkins, and not at you. The stuff below the @ Notaru was for you to read.

Anyway, to make it random, you'll need separate permutations, and set them to random. It's a pain to make a permutation for an elite and a cyborg, because both use different bones and animations, so it's rather hard to do. But for Halo 3 permutations, it's easy, because they all use the same bones.

Oh yes I shall listen to the Dumb Butt.

Oh Im gonna do that.
Should i separate permutations using guerrilla?

What.

Convention is that below the @ is the message. Just saying.



And... what is up with you? You are not going to gain any respect by stating facts when you don't even know anything about the subject, and then continuing to be ignorant by throwing horribly constructed insults at me that just show you are an immature little kid.

Both of you, calm it. Even though Jenkins was wrong again, doesn't mean you should flame him. Just tell him that he's wrong. Calling him a complete moron was uncalled for. And Jenkins, your retaliation was hardly appropriate.

Gamma...I must say, you are truly wise beyond your years.

And you should just grow up. Did you really have to post that?

Its absolutely amazes me how some guy can post a simple question, and end up getting tarred and feathered here...

OK then, so how do i separate permutations?

What do you mean? All permutations are already "separated". They will randomly be chosen, unless you set them not to be chosen.

To many A's I'm confused Lolwut. Ahhh scaring me.

*edited by admin: deleted repeat characters
Edited by Dennis on Jun 28, 2009 at 08:44 PM

System glitch or something >.<

For your problem, permutations are variations of the tag. So, if I split a model into 2 permutations, Permutation A and Permutation B, and I don't specify a permutation it should be set to, it will randomly choose either A or B.

For having different bipeds for different teams, Gamma once came up with an idea somewhere where you have Red team and Blue team's spawn points in different areas and close together. Each team's spawn points will be contained in a trigger volume. A continuous script will set the permutation for the blue spawn points to the perm for blue, and the red for red.

In b4 ban

you should. you might learn something. now since dacheif was so KIND AS TO POST 5000 As, i will have to make this short so its easy to read
headhunter is right. you do this via permutations, however as of now there is NO way to differentiate between red team and blue team as far as scripting and tagging is concerned.
without an external app or something of that sort, different biped for each team is impossible.
Edited by Donut on Jun 28, 2009 at 04:28 PM

No, I think I can do it. Have red team spawn in an area hidden away, and blue team in another.
Create a boolean for every player, like plyr0begin, and set that to true.
I'll get back to that later. Then, put a trigger volume over the red team spawn.
Same with the blue. Detect whether a player is in the red team spawn or blue.
If for example, player 0 is inside red team, set the boolean like plyr0red to true.
Do that for all people. By the time that's done, you should be able to determine what player spawned where. Then, the easy part. Change permutations.
If the player's red, swap perm to whatever you want, same for blue.
Then, once that's done, generate a random number, and teleport the player
to the corresponding area on the battlefield.
Now, once that's done, set the boolean for plyr0begin to false, so that they don't repeat the cycle again.
When they respawn, they won't have to go through the perm changing thing again, and are teleported to the battlefield.
I'm sorry if this is kinda confusing, but I'm in a rush, so I can't explain it perfectly right now.

They will spawn with a randomly chosen permutation unless you go through the process each time they respawn.

It actually makes it easier because you don't need the booleans that make sure it doesn't happen again. All you need is a continuous script that checks for all 16 players in either trigger and then changes the permutation and teleports them out based on which trigger they're in.

In addition, keep in mind that it will only work in CTF, and that it will NOT sync when players first join. Since there will be players that are already outside in the battlefield when the player initially joins, their client randomly selects perms for them until they die and respawn and the script takes over.

You COULD make separate server and client scripts and use 16 biped-hog combos to sync each player's perm at all times. The scripting wouldn't be difficult, but having to use 16 bipeds and 16 hogs is kind of crazy...

Oh right, I forgot about the random perm when respawn.
When most people play team games, they play on CTF,
so that normally isn't that much of a problem.

What happens when a player switches teams?

They die and respawn on the other team, and so they respawn in the other team's trigger volume and will be given the other team's permutation. No problem there.

But I still dont get how I do the Biped thing I asked a while ago. But were getting somewhere

Ok do you mean the permutations tab when i open up any biped?

The permutations for a .gbxmodel, not a .biped

where is the .gbxmodel

It's referenced in the biped, under "Model".

i can't do anything under the permutation tab.

You can check the checkboxes "Not initially chosen", or something like that. That determines whether the permutation can be chosen or not. If you check the check box, it won't be chosen at random, but you can refer to it via scripts.

so I have to make a script for it?

Only if you check the checkbox. Then, if you wish to refer to it, you'll need a script.