There were a lot of syntax issues in your command, I recommend using a command generator such as MCStacker next time, I fixed all the issues for you and it all works.
give @p wither_skeleton_spawn_egg{EntityTag:{id:"minecraft:wither_skeleton",CustomName:'{"text":"Wither Boss"}',CustomNameVisible:1,Glowing:1,Health:100,Attributes:[{Name:"generic.max_health",Base:100},{Name:"generic.follow_range",Base:500},{Name:"generic.knockback_resistance",Base:0.49d},{Name:"generic.movement_speed",Base:0.4d},{Name:"generic.attack_damage",Base:2}],Fire:20,Silent:1,HandItems:[{id:"minecraft:diamond_sword",tag:{display:{Name:'{"text":"Fake Wither Sword (Trade)"}',Lore:['{"text":"vous devez donner cet item a un"}','{"text":"admin et il vous donnera le"}','{"text":"vrai item"}']},Enchantments:[{id:"knockback",lvl:2},{id:"fire_aspect",lvl:2}]},Count:1},{id:"minecraft:shield",tag:{display:{Name:'{"text":"Wither Shield"}',Lore:['{"text":"le bouclier maudit du wither..."}']},Enchantments:[{id:"unbreaking",lvl:3}]},Count:1}],HandDropChances:[2F,2F],ArmorItems:[{tag:{display:{Name:'{"text":"Bottes du Wither Boss"}',Lore:['{"text":"vous devez donner cet item a un"}','{"text":"admin et il vous donnera le"}','{"text":"vrai item"}']},Enchantments:[{id:"protection",lvl:4},{id:"unbreaking",lvl:3}]},Count:1,id:"minecraft:diamond_boots"},{tag:{display:{Name:'{"text":"Jambi\\\\u00e8re du Wither Boss"}',Lore:['{"text":"vous devez donner cet item a un"}','{"text":"admin et il vous donnera le"}','{"text":"vrai item"}']},Enchantments:[{id:"protection",lvl:4},{id:"unbreaking",lvl:3}]},Count:1,id:"minecraft:diamond_leggings"},{tag:{display:{Name:'{"text":"plastron du Wither Boss"}',Lore:['{"text":"vous devez donner cet item a un"}','{"text":"admin et il vous donnera le"}','{"text":"vrai item"}']},Enchantments:[{id:"protection",lvl:4},{id:"unbreaking",lvl:3}]},Count:1,id:"minecraft:diamond_chestplate"},{id:"minecraft:diamond_helmet",Count:1,tag:{display:{Name:'{"text":"Casque du Wither Boss"}',Lore:['{"text":"vous devez donner cet item a un"}','{"text":"admin et il vous donnera le"}','{"text":"vrai item"}']},Enchantments:[{id:"protection",lvl:4},{id:"unbreaking",lvl:3}]}}],ArmorDropChances:[2F,2F,2F,2F],ActiveEffects:[{Id:8,Amplifier:0,Duration:2147483647},{Id:24,Amplifier:0,Duration:2147483647}]}}
If you use MCStacker with proper parameters (it also has a nice way to insert NBT into the selling field) it should all work perfectly, at least it did for me.
Hello! To me everything seems perfect, I even tried it myself and it works flawlessly. So you have these commands in a ticked function or repeating command blocks:
/execute as @e[tag=NexusTestWaystone,tag=!inZone] at @s if entity @p[distance=..1] run tag @s add inZone
/execute as @e[tag=NexusTestWaystone,tag=inZone] at @s unless entity @p[distance=..1] run tag @s remove inZone
This works without problems, maybe you just made a small mistake when using the commands?
The first can be accomplished using repeaters and a command block to summon the rabbit, you can use the internet to calculate how many repeaters = how many seconds
As for the second, Java Edition is just way better for this sort of stuff.
You can store the player's starting armor damage in a score like this:
/execute store result score @p durability run data get entity @p Inventory[{Slot:102b}].tag.Damage
Of course, this is damage, not the durability value, but that does not matter for our use. You cannot directly modify the player's NBT (so their inventory), but you can other entities'. We will summon an armor stand holding an iron chestplate like so:
I gave it a damage value of 1 because then we can modify it (if there is no damage, we can't modify the value). We will now copy the scoreboard value to the damage of the armor stand's iron chestplate like this:
/execute store result entity @e[tag=chestplate,limit=1] HandItems[0].tag.Damage int 1 run scoreboard players get @p durability
Finally, we can copy the item from the armor stand to the player like so:
/item replace entity @s armor.chest from entity @e[tag=chestplate,limit=1] weapon.mainhand
Using all these commands and a simple command to decrease the durability value, you can do exactly that!
The 10 10 10 is the middle of your box, the 5 indicates how big the box is, it checks for players in the radius that size from that middle of the box and then teleports you to the box.
First off, instead of having multiple command blocks after each other with repeaters, you can use Chain command blocks to run multiple at once and put them on top of each other.
For your trading system you could just summon villagers with custom trades, use a command generator like MCStacker for this. But if you want to stick to your mechanism, here's what I think. If you use a command to specify players with carrot and count:2, the player has to have exactly that many carrots, no more, no less. To fix this I recommend you indeed make a scoreboard.
You can use this command to store the amount of an item someone has in their inventory in a scoreboard:
/execute as @a store result score @s carrotCount run clear @s carrot 0
(Put this in a forever repeating command block)
The '0' doesn't clear the carrots but instead returns the amount the player has.
Then to detect a minimum amount of carrots you can use two options:
1. /execute as @a if score @s carrotCount matches 2.. run (do all the carrot trading stuff)
2. /execute as @a[scores={carrotCount=2..}] run (do all the carrot trading stuff)
Hope this helps, let me know if you need more!
PS: For all of these things you're doing and to save space from command blocks, I highly recommend using datapacks, they're vanilla, easy to learn and incredibly useful. They allow you to run hundreds of commands at once and every single tick (like repeating command blocks). I think this will help in your map.
This seems to be a 'bug' that many are let down by (see https://bugs.mojang.com/browse/MC-98642). The horse does levitate if you summon it with the effect, but that won't really work in your case.
I tried everything, /effect, /data, nothing works. You've simply encountered a bug that has to be fixed.
You could find the coordinates for the corners of the block and use the target selector's dx, dy, and dz parameters to specify arrows that are on a side of a block. See this drawing:
You could store the book's text in an armor stand's name, then display its name using tellraw, but the name of an entity has different syntax, so it won't work. You could just force everyone or someone to run that command (/data get block ~1 ~ ~ Book.tag.pages[0]) to display it for them, but I don't think other things are possible.
This is quite simple, but not really. First you summon the Iron Golem with an AngerTime of 99999, so it will be angry for all eternity:
/summon iron_golem ~ ~ ~ {AngerTime:999999}
Sadly there is more necessary, we need to specify what player the Iron Golem is targeting. We do this by getting any player's UUID and merging that into the Iron Golem's data value like so:
/data modify entity @e[type=minecraft:iron_golem,limit=1] AngryAt set from entity @s UUID
0
There were a lot of syntax issues in your command, I recommend using a command generator such as MCStacker next time, I fixed all the issues for you and it all works.
0
You could make the command face a player like this and then use directional parameters (^) to place the wall in that direction.
This will copy the direction the player is looking at to the experience orb and make the experience orb place a wall in front of it in that direction.
0
If you use MCStacker with proper parameters (it also has a nice way to insert NBT into the selling field) it should all work perfectly, at least it did for me.
1
Hello! To me everything seems perfect, I even tried it myself and it works flawlessly. So you have these commands in a ticked function or repeating command blocks:
This works without problems, maybe you just made a small mistake when using the commands?
0
The first can be accomplished using repeaters and a command block to summon the rabbit, you can use the internet to calculate how many repeaters = how many seconds
As for the second, Java Edition is just way better for this sort of stuff.
0
You can use the /fill command for this, it's much more convenient.
0
I believe this might work:
Simply change the 1 to anything else and run this every tick using your datapack, this should then modify every warden in the world.
0
You can store the player's starting armor damage in a score like this:
Of course, this is damage, not the durability value, but that does not matter for our use. You cannot directly modify the player's NBT (so their inventory), but you can other entities'. We will summon an armor stand holding an iron chestplate like so:
I gave it a damage value of 1 because then we can modify it (if there is no damage, we can't modify the value). We will now copy the scoreboard value to the damage of the armor stand's iron chestplate like this:
Finally, we can copy the item from the armor stand to the player like so:
Using all these commands and a simple command to decrease the durability value, you can do exactly that!
0
This is simple, you can just add a team selector to the command like this:
0
Not sure why you are still using 1.12, the new /execute command would be amazing for this, like so:
/execute positioned 10 10 10 unless entity @p[distance=..5] run tp @s ~ ~ ~
The 10 10 10 is the middle of your box, the 5 indicates how big the box is, it checks for players in the radius that size from that middle of the box and then teleports you to the box.
0
First off, instead of having multiple command blocks after each other with repeaters, you can use Chain command blocks to run multiple at once and put them on top of each other.
For your trading system you could just summon villagers with custom trades, use a command generator like MCStacker for this. But if you want to stick to your mechanism, here's what I think. If you use a command to specify players with carrot and count:2, the player has to have exactly that many carrots, no more, no less. To fix this I recommend you indeed make a scoreboard.
You can use this command to store the amount of an item someone has in their inventory in a scoreboard:
/execute as @a store result score @s carrotCount run clear @s carrot 0
(Put this in a forever repeating command block)
The '0' doesn't clear the carrots but instead returns the amount the player has.
Then to detect a minimum amount of carrots you can use two options:
1. /execute as @a if score @s carrotCount matches 2.. run (do all the carrot trading stuff)
2. /execute as @a[scores={carrotCount=2..}] run (do all the carrot trading stuff)
Hope this helps, let me know if you need more!
PS: For all of these things you're doing and to save space from command blocks, I highly recommend using datapacks, they're vanilla, easy to learn and incredibly useful. They allow you to run hundreds of commands at once and every single tick (like repeating command blocks). I think this will help in your map.
0
This seems to be a 'bug' that many are let down by (see https://bugs.mojang.com/browse/MC-98642). The horse does levitate if you summon it with the effect, but that won't really work in your case.
I tried everything, /effect, /data, nothing works. You've simply encountered a bug that has to be fixed.
0
You could find the coordinates for the corners of the block and use the target selector's dx, dy, and dz parameters to specify arrows that are on a side of a block. See this drawing:
0
You could store the book's text in an armor stand's name, then display its name using tellraw, but the name of an entity has different syntax, so it won't work. You could just force everyone or someone to run that command (/data get block ~1 ~ ~ Book.tag.pages[0]) to display it for them, but I don't think other things are possible.
0
This is quite simple, but not really. First you summon the Iron Golem with an AngerTime of 99999, so it will be angry for all eternity:
/summon iron_golem ~ ~ ~ {AngerTime:999999}
Sadly there is more necessary, we need to specify what player the Iron Golem is targeting. We do this by getting any player's UUID and merging that into the Iron Golem's data value like so:
/data modify entity @e[type=minecraft:iron_golem,limit=1] AngryAt set from entity @s UUID