On Player Join

Introduction ​

Sourced By Bedrock Commands Community Discord

This system will run your desired commands on the event that a player joins the world.

Setup ​

To be typed in Chat:

/scoreboard objectives add joined dummy

If you are working with functions and prefer to have the objective added automatically on world initialisation, follow the process outlined in On First World Load.

System ​

## Register Players to 'joined' Objective Who Joined For First Time or Were Cleared from 'joined' Previously
scoreboard players add @a joined 0

## Your Commands Here (Example)
tp @a [scores={joined=0}] 0 65 0

### Mark Players as Joined
### Clear 'joined' score of online and offline players
scoreboard players reset * joined
### Set online players score to 1
scoreboard players set @a joined 1

Here, we have used a /tp command as an example, but you can use any command you prefer and as many as you need.

Just make sure to follow the given order and properly apply the scores={joined=0} selector argument as shown for your desired commands.

Explanation ​

When the player joins, a score of 0 is added to their joined objective. This allows us to run commands from them using the scores selector argument.

Immediately after the commands are run, we reset all the scores on the objective using wildcard *. And only the players who stayed online will have their score set to 1.

This way, since our commands only target players with a score of 0, the commands won't repeat for the players who stayed, unless they leave and rejoin or if we run:

/scoreboard players set <player> joined 0

This is because adding a score of 0 to a score of 1 will have no change. But adding a score of 0 to players with no score will set their score to 0.

Tick JSON ​

If you are using functions instead of command blocks, the on_join function must be added to the tick.json in order to loop and run it continuously. Multiple files can be added to the tick.json by placing a comma after each string. Refer to Functions documentation for further info.

{
  "values": [
    "events/player/on_join"
  ]
}

If using functions, your pack folder structure will be as follows: