Minecraft – How to test the command block contraptions for multiplayer compatibiltiy

minecraft-commandsminecraft-java-edition

I like making command block contraptions. Occasionally, I make a contraption that I want to use on a multiplayer server (or offer to server operators), but I don't know of a way to test that it'll actually work.

I don't run a server that I can test on, nor do I want to have to get friends/family on this non-existent server in order to do tests and debugging. I also don't have op privileges on another server where I could do these tests (nor would I want to since it could disrupt the server). Finally, I only own one Minecraft account, and I'm not really interested in buying a second account just for the purposes of testing command blocks.

So given that, what's the best way for me to perform my testing and debugging? Is there a simple (and legitimate) way for me to add one or more players that I can control to my otherwise single player command block world?

Best Answer

What you could do to make your testing as real as possible is target entities with the @e selector in replacement of real players, and try testing your command blocks with entities like villagers.

For an example if you were trying to tp a player with /tp @p (Coordinates) You could replace @p or @a with @e to teleport entities.

@e should be effective for most contraptions involving players.

Note: This is how I test my contraptions unless I'm with a friend.

Related Solutions

Minecraft – How to destroy a block from afar

Instead of building a bridge you can also build a pile. Position yourself underneath the floating block and start placing blocks below you.

After your done destroying the floating block start digging down till you reach the ground. This way you don't have to break any glass in your tower and you don't lose any resources beside some tool durability.

Minecraft – n easier way to detect for a block around the player

You can use a filtered /clone command that will copy blocks to their same position. The result is no difference visually, but the command can return a CommandStat value depending on its success.

Prerequisites:

Objective to hold the returned CommandStat value.

/scoreboard objectives add BLOCKS dummy

Applying the AffectedBlocks trigger to players, so that when they run commands, their own "BLOCKS" score will be set equal to the number of blocks affected. You may need this on a clock if new players can join at any time.

/stats entity @a set AffectedBlocks @a[c=1] BLOCKS

In order for CommandStats to modify a target's score, they must be tracked on the scoreboard prior. This may need to be on a clock as well.

/scoreboard players add @a BLOCKS 0

Clock commands:

The following must be run in order on a clock.

Cause players to run a /clone command around them, looking for grass specifically. It will be cloned to the same position that they're already in. This will return either the number of grass blocks found or 0. The target coordinates should be the same as the first specified corner.
```
/execute @a ~ ~ ~ /clone ~-10 ~-1 ~-10 ~10 ~10 ~10 ~-10 ~-1 ~-10 filtered force minecraft:grass
```

Players with a "BLOCKS" score of 1+ has grass around them. You can target them based on this value.

/say @a[score_BLOCKS_min=1] has grass blocks around them.
/say @a[score_BLOCKS_min=10] has at least 10 grass blocks around them.

Best Answer

Related Solutions

Minecraft – How to destroy a block from afar

Minecraft – n easier way to detect for a block around the player

Related Topic