Minecraft : Problem with 1.9 command blocks

minecraft-commandsminecraft-java-edition

I'm planning to make a map with custom classes and special abilities in Minecraft with the "new" 1.9 command blocks (although its been 2 years since 1.9 came out, the last time I fiddled with commands was on 1.8, so I'm confused).

Cutting to the chase, I was utterly confused due to the new types of command blocks and how to use them respectively.Here were my issues :

I planned to detect a Giant named Dinnerbone that is on the ground, but for some reason the /testfor @e[type=Giant,name=Dinnerbone] {onGround:1b} command didn't work at all.Perhaps the onground tag was removed after 1.9?
I planned to do a chain of commands on the Giant once it's score on a scoreboard named GiantTimer reaches 0 from 200, with it's score is constantly decreasing by a Repeated command block. I don't know how you could make a single line of command blocks to set the score to 200, remove it 20ticks/s using the repeated command block, and once it reaches zero activate a chain of commands on the Giant with a score of 0. I know the commands to do all these, but I don't get how you can detect when the score reaches 0 and then activate a line of command blocks; I do not know the right combination of the various command blocks to do these. Do you need more columns of command blocks to do that? Set it to Repeat or Conditional? I want the effects from the chain of commands after it detects the score is 0 to happen only once, not repeatedly.

Best Answer

This wasn't a 1.9 change, but types have to be lowercase now: giant instead of Giant. A full list is here.

If you want to activate a line of command blocks conditionally, put a testing command (testfor, testforblock, testforblocks or anything else that can succeed or fail) into a repeating command block and place another repeating command block, this one conditional, so that its back faces the first command block (because that's how "conditional" works). A normal straight line of command blocks also works. Then you just continue normally with chain command blocks, they don't have to be conditional (but can be if you want to make them depend on the previous one).
How this works: The first repeating command block tests the condition in every tick, the second repeating command block checks for the success of the first one every tick, but only runs if the first one was successful and only then it also activates the chain command blocks in front of it.

For the future: Please only ask one question per question. I've answered both now because the first one is really trivial.

Related Solutions

Minecraft – way to determine whether a player is online or offline with command blocks

For this problem, you don't actually need to modify the players score when they are offline (which is possible, but finicky), you should be able to change their score as soon as they log back in.

First, create a scoreboard objective of type stat.leaveGame:

scoreboard objectives add quits stat.leaveGame

You should then have two command blocks on some kind of clock, one activated after another. In the block that is activated first, put this command:

scoreboard players set @a[score_quits_min=1] timer -1

Then, in the one that is activated second:

scoreboard players set @a[score_quits_min=1] quits 0

The quits score increments when the player leaves. So, when they log back on, it will be at 1 and their timer score will be set to -1. Their quits score then has to be set back to 0, so that it can be used for the next logout and also so that timer isn't repeatedly set to -1,

Minecraft – /testfor troubles in 1.9

In 1.9, the r parameter has undergone some major changes. Prior to 16w07a, the produced radius and entity selection was very inconsistent. MC-95352 resulted in various different fix attempts.

For comparison, in 1.8 r=0 would target entities within the whole blockspace. As well, it would latch onto the block grid even when executed by an entity.

In 16w07a, the radius was fixed to be consistent and execute from the center of the block, but there was no offset to the input value. For example, r=0 would literally mean "these exact coordinates with no leniency". If any entity was not in the exact center of a block, it could not be targeted.

In 16w07b, the radius was changed to execute from the bottom face of the blockspace rather than the center, and the offset to the radius was set to 0.25. This meant that with r=0 (which essentially meant r=0.25), an entity had to be within a small part of the center of the block, rather than the whole blockspace in 1.8.

In 1.9 pre-release 3, the radius offset was changed to 0.015625 (r=0 meant r=0.015625).

And finally in 1.9 pre-release 4, the offset was removed again and r=0 meant "exactly at this location" once more. However, a major changed occurred here: the radius, when executed by an entity, no longer latches onto the block grid and instead used the entity as the origin. This means that with entities, you'd actually be searching around the entity rather than the block that they're in. See MC-97316 for details.

Since r=0 means "exactly at these coordinates" rather than "within this blockspace", you will not be able to use it absolutely anymore. You will need to change it to r=1 (which indeed means 1 block exactly in each direction, reaching to the center of the neighboring blocks).

Best Answer

Related Solutions

Minecraft – way to determine whether a player is online or offline with command blocks

Minecraft – /testfor troubles in 1.9

Related Topic