c!Tommy my Webkinz

Part 1 - One-time Commands

These are all commands you only have to type once, and can do so using the server console or by logging a player with op powers into the server and typing / directly whilst online.

Worldborder

Find a seed with a good location, set the center of the worldborder at the location you want, then set the worldborder itself. The Life series uses a worldborder diameter of 750 blocks for about 14 players.

/worldborder center [x-position z-position] /worldborder set [diameter]

Example: We create a square world border centered at x-coordinate 100, z-coordinate 200, with a diameter of 750 blocks, using

/worldborder center 100 200 /worldborder set 750

Note: If you change your worldborder center to something that isn’t the world spawn, you should also change your world spawnpoint to the same location or somewhere nearby, using

/setworldspawn [x-position y-position z-position]

Examples:

/setworldspawn 100 60 200 -> sets the world spawnpoint at the x-coordinate 100, y-coordinate (height) 60, z-coordinate 200 /setworldspawn -> only works if it’s being set by a player in the world; sets the world spawnpoint at where the player sending the command is standing

Teams

Teams allow you to change the players’ name colors in the tab list, chat, and the IGNs that float over other players’ heads when playing multiplayer.

! Warning ! Using teams to code this means that all players of the same team can communicate with each other in secret using /teammsg or /tm (so a yellow life could send another message to a yellow life without any green or red lives seeing the message). I don’t think there’s a way to disable this setting, so we worked around it by declaring it in server rules that you can’t use the /teammsg or /tm functionality.

Create three teams.

/team add Green /team add Yellow /team add Red

Then use the modify command to change their display colors.

/team modify Green color green /team modify Yellow color yellow /team modify Red color red

When all players are online for the first time, you need to manually add them to the Green team using:

/team join Green @a

You can also add each player that’s playing beforehand (especially if you have a whitelist) so that all players are already on the Green Team before they log on:

/team join Green [player]

Example: To add Grian to the Green team, we use

/team join Green Grian

Note: If you want to replace a player’s team with a new one, simply use /team join [newTeam] [player], which will override the previous team.

Scoreboard

The scoreboard functionality allows you to track each player’s number of deaths (which we’ll be using to determine how many times they’ve died and set them to the correct team according to that) as well as check when a player dies (which triggers the other command blocks to put players on new teams as necessary).

/scoreboard objectives add Deaths deathCount /scoreboard objectives add hasDied1 deathCount /scoreboard objectives add hasDied2 deathCount /scoreboard objectives add hasDied3 deathCount

The hasDied1-3 objectives will be used to check if any player has just died; the Deaths objective is to keep track of each player’s unique amount of deaths.

If you are testing in your server and want to set a certain amount of deaths, or if during the game something goes wrong and you want to restore a life to a player, you can use

/scoreboard players set [player] Deaths [num]

Example: To reset Grian to Green life, I would use the following combination:

/scoreboard players set Grian Deaths 0 /team join Green Grian

Keep in mind that the first death sets a player to yellow, the second sets a player to red, and the third eliminates a player completely! So on Green life, a player will have 0 deaths (Deaths = 0), on Yellow life, they will have 1 death (Deaths = 1), and so on.

Changing the scoreboard does not change the player’s team, so as I demonstrated above, to change a player’s team you will need both the scoreboard command and the teams join command.

Part 2 - Command Blocks

These are commands you place in command blocks, and can only be placed by a player in-game (can’t do it via console). Place the command blocks in a bedrock box near the world spawnpoint (I did mine at the bottom of the world), since the world spawnpoint’s proximity will keep the command blocks loaded and working at all times.

Use a /give command to give yourself command blocks.

/give @p command_block

I’ll put a picture of my setup first, then describe how to build it.

This is what my setup looks like: I color coded each line of command blocks so that it was visually clear what each line did, and you can see the arrows on the top and sides all point in the same direction. Each repeat (purple) command block flows into a chain (blue) command block.

To build this: Place three command blocks down against a wall, so that the arrows on top and on the sides of the command block are pointing away from the wall. On two of these, place another command block pointing away from the first (so the arrows both point in the same direction, one into the second); on the third, place two command blocks in the chain.

In the first of each chain, enter the command block interface by right-clicking, then toggle the options so that they read “Repeat - Unconditional - Always Active”. “Repeat” means that they are continually running the command every tick of the game; “unconditional” means that the block will activate no matter what; and “always active” means that the command block does not need a redstone signal to activate. These purple command blocks will be continually checking whether or not a player has just died.

In the rest of the command blocks, toggle the options so they read “Chain - Conditional - Always Active”. “Chain” means that the command block only runs the command if the previous command block in the chain (the block whose arrow points into this one), and “conditional” means that the previous command block must be successful (in this case, it will be successful if it successfully checks that a player just died).

Copy-paste the following commands exactly as listed:

In the first chain of command blocks (1 purple, 1 blue):

PURPLE: /execute if entity \@a[scores={hasDied1=1..}] run scoreboard players reset @a hasDied1 BLUE: /execute as @a at @s if score @s Deaths matches 1 run team join Yellow @s

In the second chain of command blocks (1 purple, 1 blue):

PURPLE: /execute if entity @a[scores={hasDied2=1..}] run scoreboard players reset @a hasDied2 BLUE: /execute as @a at @s if score @s Deaths matches 2 run team join Red @s

In the third chain of command blocks (1 purple, 2 blue):

PURPLE: /execute if entity @a[scores={hasDied3=1..}] run scoreboard players reset @a hasDied3 First BLUE: /execute as @a at @s if score @s Deaths matches 3.. run gamemode spectator @s Second BLUE: /execute as @a at @s if score @s Deaths matches 3.. run team leave @s

Elaboration on the /execute command

For the purple command blocks: /execute if means “if [condition is true] then [trigger an event to happen]”. In this case, the code reads “if, across all players (@a), the hasDied score is 1 or greater (1..), then reset every player’s hasDied score to 0”. Since hasDied is linked to the deathCount in-game statistic, this checks if any player’s death count has increased to 1 (ie, a death has just occurred), and if that’s true then the command block resets everyone’s hasDied score to 0 (which wipes the scores for the next time someone dies) AND also outputs a “success” signal (ie, the condition under the “if” was met), triggering the blue command blocks to run their commands.

For the blue command blocks: the code reads “Across all players (as @a), if a player (@s)’s Death score matches a certain number of deaths, then have that player join the team matching that number of deaths (or leave all teams, if the number of deaths means they are out of the game)”; if the number of deaths means they’re eliminated, we also turn that player to spectator mode.

We use several hasDied objectives because each individual purple command block wipes its own hasDied count after running a success. If, for instance, you want four teams - Dark Green, Green, Yellow, and Red - you would need to create a fourth hasDied objective and another chain of command blocks like above.

If you want to change the total number of lives a player has, you can edit the “if score @s Deaths matches run team join ” in each command block. Calculate the number of deaths needed as following:

Yellow NumDeaths = # lives - 2 Red NumDeaths = # lives - 1 Spectator/Eliminated NumDeaths = # lives