Help with Battle Royal

[jch10]

I need to set a specific team to not spawn in a certain spawn pad when game happens. BTW it is free for all.

[WhoAmI]

If it is free for all, then how do you have specific teams? Are you using psuedo teams?

[WolfTechnology]

So its like host spanws in a specifit area?

[California_Love]

Why not just change the spawn pad to a specific team? Is that what you did?

[jch10]

In beginning, everyone spawns randomy in different spots and when you die you end up at box.

[California_Love]

Using a knockout manager to send them to a teleporter?

[WhoAmI]

So you could just disperse spawn pads everywhere for randomized spawning, or have them spawn on a randomized teleporter.

[California_Love]

Yeah, do that, but have a checker checking the team’s number before spawning.

[jch10]

I did the spawn pad.

[jch10]

Btw how do you do when player dies they switch to spectator?

[California_Love]

Use a knockout manager and set it to a specific team using block code.
Then wire it to a team switcher that makes them spectators.
Player knocked out switch player to configured team
Need pictures?

[jch10]

On a scale of 1 to 10 on how much I understood that: 4

[jch10]

Yes, I do need pictures

[WhoAmI]

Using a knockout manager to run a task like such will instead set the player that is knocking out the other player to spectator.

You will need to use one lifecycle (The pink device) and set it to on player knocked out.
One team switcher (Blue device) and then set it to switch a player to spectator. Then wire the lifecycle to the team switcher.

EDIT: If you want it to function for a separate team, then simply take a wire repeater and make it so that it only lets in signals from your wanted team. Then wire the lifecycle to the wire repeater, and the wire repeater to the team switcher.

[California_Love]

[California_Love]

Wait a minute, he said a specific team.
It doesn’t give you the option. It’ll do that for any player.

[WhoAmI]

Then you can simply put in a wire repeater to block signals from all other teams.

[California_Love]

But wire repeaters can mess up sometimes. You’d have to use several wire repeaters, so instead just use a single block code.

[WhoAmI]

Why would you need only one repeater? A wire repeater also consumes less memory than the 500 memory required for block code.

[California_Love]

But----

@Shdwy

This is really important. I see so many people using repeaters, but they are literally THE MOST USELESS DEVICE IN THE GAME.

Everything about a repeater is inefficient.
Let’s start with their most basic functionality. Repeating a signal. Let’s say it sends out on channel X every second.
WOAH! We can do that with triggers too!
If it has a delay of one, sends on channel X, and receives on channel X, WOW! It’s literally the same exact thing but with TEN TIMES THE MEMORY EFFICIENCY.

Let me tell you about looping.

The most simple one is a trigger. It sends and receives on the same channel, and has a customizable delay. We can count the number of times it sends out on with a counter that increments on the channel. If we want to cap it at a certain amount, that’s easy to do. If we want to stop it after a certain amount of time, we can just use a trigger that counts in seconds and once it hits x time, it disables the other system.

Basically, you can do pretty much everything with the delay ability/activation states of triggers + the counting ability of counters.

Wow!

Ok, so now lets look at the abilities of repeaters.

After period of time? Can be done with a timer hooked up to a different system.

After number of repetitions? Easily done with a counter that tracks channel broadcasts.

After receiving on a channel? Magic, we just… turn off the trigger. Bonus points – we just turn it back on again right afterwards!

Max concurrent tasks?!!?!?!? Well, a trigger already has 300. (well, the wire/channel caps dictate that the limit is 300, at least)
Lets say the trigger has a delay of X seconds, and we want Y concurrent tasks for the trigger.
We simulate this by having a counter counting output broadcasts. It gets incremented every time the loop runs, and decremented every X/Y seconds. Then, if it ever goes over the limit of #Y per X seconds, it can just… turn off the trigger. If you want to store this stuff somehow, you’d need to use a property and then keep going back and forth and starting up new loops. For those of below average literacy

Repeater no good. Too much memory. Trigger can do same thing. Trigger start on X, trigger broadcast on X. Wow! Much good. If you want do more, you use counter to track things.

Okay, you know what, that’s a better alternative. Thanks.