Minecraft Forums

I think what YMBrothers was trying to say is, you screwed up your example.

Quote from Robified >>

To explain how this works for everyone else who might see it:

x, y, and z arguments should be the lowest bottom corner of the area (towards the negative x and negative z). The reason for this, is because the dx, dy, and dz arguments are the number of blocks from that point. It isn't the number of blocks you want to protect.

If you wanted to protect a 10x10x10 block area going from these coordinates:

x=10,y=20,z=-50 <----- This is the "point" you refer to in italics

Your dx, dy, and dz would be:

dx=20,dy=30,dz=-40 (negative numbers get increased)

And NOT:

dx=10,dy=10,dz=10 <----- This WOULD be the "number of blocks from that point", in your own words, in the first paragraph, and then contradicted in your example.

This is misleading.

You can remember it as: d stands for "distance from" NOT "opposite point of a cuboid"

I am getting into /data modify and /data merge, but I am having trouble with UUID's.

You can get the UUID from a player with /data get entity @p UUID

But how can I use that data in another command?

For example, Summoning an ender pearl and setting a certain player (@p) as the Owner.

/summon ender_pearl ~ ~ ~ {Owner:[UUID]}

Or getting an villager mad at you

/data merge entity @e[type=minecraft:villager,limit=1] {Gossips:[{Target:[UUID],Type"minor_negative",Value:150}]}

Basically, I want to extract data from one point and use it at another.

I hope I explained clearly enough.

Thank you in advance!

Oh my god, what a huge replay, thank u so much for taking that much time to help me!

This is way complicated than i thought.

So the way u show me how to detect chest minecart beying opened looks good, but i dont really understand thiss UUID and loot table stuff so i will propably read it like 50 times until i try something, Removing unused chests looks pretty simple and there shouldnt be a problem with doing it.

Again thank you so much for that huge replay with good explanation, im at pretty advanced level of commands but i rarerly mess with UUID and loot tables so it might be hard for me.

UPDATE:

I fixed it.

Minecraft does not like entity types within entity types.

vile.json:

{
  "values": [
    "#minecraft:skeletons",
    "minecraft:zombie_villager",
    "minecraft:zombie",
    "minecraft:wither",
    "minecraft:phantom",
    "minecraft:husk",
    "minecraft:drowned"
  ]
}

It works after I remove #minecraft:skeletons

the if and unless statements from the /execute command are the new /testfor. You can count how many items (in entity form) there are like this:

/execute if entity @e[type=item,nbt={Item:{id:"minecraft:diamond"}},distance=..5]

^ this command will display the number of items in chat. You can also store this output into a scoreboard objective like this:

/execute store result score <objective_holder> <objective> run execute if entity @e[type=item,nbt={Item:{id:"minecraft:diamond"}},distance=..5]

Note that a stack of diamonds will be counted as 1 entity instead of 64 because that's how the game works. To get around this you can store the number of items in that stack into the stack's objective like so:

execute as @e[type=item,nbt={Item:{id:"minecraft:diamond"}},tag=!counted,distance=..5] store result score @s <objective> run data get entity @s Item.Count

increment a fake player's objective by the amount stored in the stack's objective (the stack size)

execute as @e[type=minecraft:item,distance=..5,tag=!counted] run scoreboard players operation global <objective> += @s <objective>

in this example, I'm using a fake player called "global" but you can use a player or entity if you want. And finally, tag the item so it doesn't constantly increment global's objective while the hopper is collecting the item/stack.

tag @e[type=minecraft:item,distance=..5] add counted

In case you have no idea what I'm saying, here is a world download: https://www.dropbox.com/sh/jq8de3qdzcu2yi2/AADFeflCJVXEG_JwAj8tqlZoa?dl=0

Context:

I was writing a datapack for MC 1.15.1 It worked after the update. The functions appeared in the auto-complete and the scores were updating correctly. It was working fine until I added one command line into a function that was called every tick: (playerupdate.mcfunction line 38)

execute as @a run execute at @s store result score @s Health run data get entity @s Health

It was intended to update a Health dummy variable to the player's health. It did not work despite working if it is executed by the player. I removed the line of code and began debugging. I placed the command "say hi" in the middle of the function to see if there was a failing command. It didn't say hi, so I moved it to the top of the function to see if the function was running at all. Even at line one, it wasn't running commands. Then, I reloaded again, but even tick.mcfunction wasn't running. In fact, no function, not even #minecraft:tick was in the auto-complete.

Problem:

My datapack still appears on the list, but none of the functions appear.

Download: https://www.dropbox.com/s/cvivuebh97tjxus/mmopack.rar?dl=0

Thanks guys

Yes, I figured I'd have to do something like that, as of right now I sort of combined them, so it checks for my minecraft.broken:minecraft.spawner score and also if there's a spawner entity nearby, that way I get exp if I just mine it but not if I mine it with silk touch

also (for anyone seeing this in the future) the tag for breaking something is "mined" not "broken"

these are the codes as of now;

once:

/scoreboard objectives add BrokeSpawner minecraft.mined:minecraft.spawner

every tick:

/execute at @a[scores={BrokeSpawner=1..}] as @e[type=minecraft:item,limit=1,nbt={Item:{id:"minecraft:spawner"}}] at @s run kill @e[type=minecraft:experience_orb,distance=..2]

/execute as @a[scores={BrokeSpawner=1..}] at @s run scoreboard players set @s BrokeSpawner 0

Quote from Qualthorn»

I added a loot table for the spawner block in minecraft by using the same loot table as redstone but changing redstone ore to spawner block and redstone to iron bars (so you can only get it through silk touch, otherwise you get 4-5 iron bars + fortune)

This works fine, only problem is that you still get experience even when you silk touch it

Is there a way of letting the loot table determin the EXP drop, or just a function or something saying something like:

if: silk touch

{

no_experience

}

Googled a little, seems like the block xp drop is hard-coded (i.e. not configurable). (current version: 1.14.2)

A crude workaround (assume you don't have one) is to use the loot table to make the spawner drop an extra custom item, where it'll /kill all the xp near it and /kill itself.

Quote from Robified»

I didn't mislead. You literally quoted text from another source that explains what happens.

If words can't explain, let's try video.

(Slight mistake of mine: Somehow the range is 11 x 11 x 11 instead of 10 x 10 x 10. Might be something to do with rounding down the coords)

Quote from Robified»

To explain how this works for everyone else who might see it:

x, y, and z arguments should be the lowest bottom corner of the area (towards the negative x and negative z). The reason for this, is because the dx, dy, and dz arguments are the number of blocks from that point. It isn't the number of blocks you want to protect.

If you wanted to protect a 10x10x10 block area going from these coordinates:

x=10,y=20,z=-50

Your dx, dy, and dz would be:

dx=20,dy=30,dz=-40 (negative numbers get increased)

And NOT:

dx=10,dy=10,dz=10

Hey, don't mislead :/

From https://minecraft.gamepedia.com/Commands#Selecting_targets_by_volume
Selecting targets by volume


[dx=DX,dy=DY,dz=DZ]


Selects only targets within the volume defined as starting from the location where the command was executed and extending DX blocks in the "x" direction (i.e., east/west), DY blocks in the "y" direction (i.e., upwards/downwards), and DZ blocks in the "z" direction (i.e., north/south). If an initial coordinate is specified with the x, y, and z arguments, that will be used instead of the position of the command's execution for the lower northwestern corner (dx, dy, and dz still specify distances from that coordinate; they do not specify a separate coordinate). All values are allowed, including negative and partial values.

• @e[x=1,y=2,z=3,dx=4,dy=5,dz=6] — targets only entities whose hitbox collects with the block region (1~5, 2~7,3~9) (or coordinates {(x,y,z)|x∈[1,6),y∈[2,8),z∈[3,10)}).
• @e[x=1,y=2,z=3,dx=0,dy=0,dz=0] — targets only entities whose hitbox collects with the block region (1,2,3).

It is possible to combine selection by distance and selection by volume, in which case the command will only select targets within the overlap of both regions (within certain radius/i of the volume's lower northwest corner and not outside the defined volume).

If you need some tl;dr, dx,dy,dz is not a 2nd pair of coordinates, it's the size of the box. Idk why people used to think like that. I once believed what us fellow forum members said, but proved it wrong by experiment.

I just checked that, use this. You can add more nbts for specification.

/execute as @a[nbt={RootVehicle:{}}] at @s run say foo

If you are wondering how did I get that...

First...ride a horse.

Use this to check all it's nbt data. /execute as @e[type=horse] run data get entity @s

Found nothing that's relate to passenger...

Use this to check all my nbt data. /data get entity @s

Look through the whole long list...and found this RootVehicle.

When player is not riding anything, this tag doesn't exist. When it does, it store information about your mount.

And that...should be how map maker check nbts...in general.