Minecraft Forums

Quote from an_awsome_person»

execute at @e[type=armor_stand,name=ArmorStand11,limit=1,sort=random] run summon fireball ~ ~-1 ~ {direction:[0.0,-1.0,0.0],power:[0.0,-1.0,0.0],Life:4096,ExplosionPower:1}

I have a bunch of armor stands. Every time I run this command, I want to pick a random one and make it summon a ghast fireball. The fireball should move down if it doesn't hit some entity or block that's not air. When I try running it, none of the fireballs can move more than 10 or 11 meters. They just move downward for a brief time and then explode in mid-air.

Your power is too high. It's an acceleration rather than a velocity. So I assume when you see it move like 10 blocks, it already moved like 100 blocks and the game's too lazy to render it.

Set it maybe 1/10 of the number of direction.

Quote from taiwe2»

Thank you very much! I figured out the changes before seeing your message, but I wasn't sure if they were correct. Exactly the same, so thank you, now I know the 16 hours I ran this didn't go to waste

Unfortunately, now I need to get the same kind of command block pregenerator working in 1.13. My world is custom generated and won't convert correctly without command block pregen in a vanilla server, before I can use it in spigot. I tried using a 1.12 to 1.13 command converter, but I couldn't get that to work.

I did find a command block generator for 1.13, I couldn't get the command block to work, but it did come with a data pack. I was able to edit the datapack's center radius to -8000, -8000. It appeared to work, but it seems as if the X and Y coords slightly veer off over time. With my world being 8K x 8K, that offset is massive. There were comments from others that it also veered off for them, so I assume my small edit wasn't the cause of this.

The 1.13 world pregen is here: https://bluecommand.weebly.com/world-loader.html

How much would I have to change to get that 1.12 command working in 1.13? I suspect the cause of the gradual offset in the 1.13 might be harder to find than adjusting the 1.12 command to work in 1.13.

You have to change basically everything in your 1.12 command to make it work in 1.13. Just find another world pre-generator that works in 1.13+

Quote from taiwe2»

I'm trying to adjust a command block world pregenerator for 1.12.2 by Lorgon111. It works well, but it generates a world from 0,0 outwards. I need it to generate from -8000, -8000 outwards. I've tried to play around with it, but I can't seem to get it to do that. Would anyone be able to understand this? I am waiting on a response from the original author, so hopefully, if I don't get a response from him, someone else can identify what needs to change.

(It must be a command block pre-generator, the world is already pregened with a custom terrain generator. However, chunks will be corrupted/deleted when migrating to 1.13 if the appropriate light and terrain values within the chunks are not correct. No existing world generator does this, apart from a command block one.)

Here's the command:

summon falling_block ~ ~0.55 ~ {Block:command_block,Time:1,TileEntityData:{Command:"summon commandblock_minecart ~ ~1.5 ~ {Command:\"gamerule commandBlockOutput false\",Passengers:[{id:commandblock_minecart,Command:\"setworldspawn 0 80 0\"}, 
{id:commandblock_minecart,Command:\"gamemode 3 @a\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives add Dir dummy\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives add Iter dummy\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives add Remain dummy\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives add Info dummy\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives add Running dummy\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set Ticks Info 0\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set RadiusCompletedSoFar Info 0\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set @a Running -1\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set @a Dir 1\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set @a Iter 1\"}, 
{id:commandblock_minecart,Command:\"scoreboard players set @a Remain 1\"}, 
{id:commandblock_minecart,Command:\"scoreboard objectives setdisplay sidebar Info\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"AFK World Generator for Minecraft 1.12\\\",\\\"color\\\":\\\"green\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"by Dr. Brian Lorgon111\\\",\\\"color\\\":\\\"yellow\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"https://www.youtube.com/user/lorgon111\\\",\\\"clickEvent\\\":{\\\"action\\\":\\\"open_url\\\",\\\"value\\\":\\\"https://www.youtube.com/user/lorgon111\\\"}}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"This one-command contraption only works when placed near 0,0 (which is now the world spawn).\\\",\\\"color\\\":\\\"red\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"Set your render distance to 8 chunks!\\\",\\\"color\\\":\\\"red\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"To start, run this command:\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"/scoreboard players set @a Running 1\\\",\\\"color\\\":\\\"green\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"Once desired size reached, stop with:\\\"}]\"}, 
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"/scoreboard players set @a Running 0\\\",\\\"color\\\":\\\"green\\\"}]\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~35 ~0 command_block 0 replace {Command:\\\"scoreboard objectives setdisplay sidebar\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~34 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"gamemode 0 @a\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~33 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"gamemode 1 @a\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~32 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a 0 ~ 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~31 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"time set 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~30 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"fill ~ ~-33 ~ ~ ~5 ~ air\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~29 ~0 repeating_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Running 1 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~28 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-2 ~ {auto:1b}\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~27 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"tp @a 0 130 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~26 ~0 repeating_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Running * 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~25 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~1 ~ {auto:0b}\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~24 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players test @p Running 0 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~23 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~12 ~ {auto:1b}\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~22 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players add Ticks Info 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~21 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test Ticks Info 40 *\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~20 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players set Ticks Info 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~19 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-2 ~ {auto:1b}\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~18 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-1 ~ {auto:0b}\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~17 ~0 command_block 0 replace {Command:\\\"\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~16 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=1,score_Dir=1] ~100 130 ~0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~15 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=2,score_Dir=2] ~0 130 ~100\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~14 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=3,score_Dir=3] ~-100 130 ~0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~13 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=4,score_Dir=4] ~0 130 ~-100\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~12 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players remove @a Remain 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~11 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~10 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"execute @p[score_Dir_min=2,score_Dir=2] ~ ~ ~ scoreboard players add @a Iter 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~9 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~8 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"execute @p[score_Dir_min=4,score_Dir=4] ~ ~ ~ scoreboard players add @a Iter 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~7 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~6 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players operation @a Remain = @p Iter\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~5 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players add @a Dir 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~4 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players set @a[score_Dir_min=5,score_Dir=5] Dir 1\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~0 ~3 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players add RadiusCompletedSoFar Info 100\\\"}\"}, 
{id:commandblock_minecart,Command:\"setblock ~ ~-2 ~ command_block 0 0 {auto:1b,Command:\\\"fill ~ ~ ~ ~ ~2 ~ air\\\"}\"}, 
{id:commandblock_minecart,Command:\"kill @e[type=commandblock_minecart,r=5]\"}]}"}, 
Passengers:[{id:falling_block,Block:redstone_block,Time:1,Passengers:[{id:falling_block,Block:activator_rail,Time:1}]}]}

I made my changes in bold and red, not sure if it works. And remember, this one command is made for 1.12. If it said 1.12, do it in 1.12. This command will 100% not work in 1.13+.

summon falling_block ~ ~0.55 ~ {Block:command_block,Time:1,TileEntityData:{Command:"summon commandblock_minecart ~ ~1.5 ~ {Command:\"gamerule commandBlockOutput false\",Passengers:[{id:commandblock_minecart,Command:\"setworldspawn -8000 80 -8000\"},
{id:commandblock_minecart,Command:\"gamemode 3 @a\"},
{id:commandblock_minecart,Command:\"scoreboard objectives add Dir dummy\"},
{id:commandblock_minecart,Command:\"scoreboard objectives add Iter dummy\"},
{id:commandblock_minecart,Command:\"scoreboard objectives add Remain dummy\"},
{id:commandblock_minecart,Command:\"scoreboard objectives add Info dummy\"},
{id:commandblock_minecart,Command:\"scoreboard objectives add Running dummy\"},
{id:commandblock_minecart,Command:\"scoreboard players set Ticks Info 0\"},
{id:commandblock_minecart,Command:\"scoreboard players set RadiusCompletedSoFar Info 0\"},
{id:commandblock_minecart,Command:\"scoreboard players set @a Running -1\"},
{id:commandblock_minecart,Command:\"scoreboard players set @a Dir 1\"},
{id:commandblock_minecart,Command:\"scoreboard players set @a Iter 1\"},
{id:commandblock_minecart,Command:\"scoreboard players set @a Remain 1\"},
{id:commandblock_minecart,Command:\"scoreboard objectives setdisplay sidebar Info\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"AFK World Generator for Minecraft 1.12\\\",\\\"color\\\":\\\"green\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"by Dr. Brian Lorgon111\\\",\\\"color\\\":\\\"yellow\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"https://www.youtube.com/user/lorgon111\\\",\\\"clickEvent\\\":{\\\"action\\\":\\\"open_url\\\",\\\"value\\\":\\\"https://www.youtube.com/user/lorgon111\\\"}}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"This one-command contraption only works when placed near somewhere (which is now the world spawn).\\\",\\\"color\\\":\\\"red\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"Set your render distance to 8 chunks!\\\",\\\"color\\\":\\\"red\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"To start, run this command:\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"/scoreboard players set @a Running 1\\\",\\\"color\\\":\\\"green\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"Once desired size reached, stop with:\\\"}]\"},
{id:commandblock_minecart,Command:\"tellraw @a [{\\\"text\\\":\\\"/scoreboard players set @a Running 0\\\",\\\"color\\\":\\\"green\\\"}]\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~35 ~0 command_block 0 replace {Command:\\\"scoreboard objectives setdisplay sidebar\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~34 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"gamemode 0 @a\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~33 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"gamemode 1 @a\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~32 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a -8000 ~ -8000\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~31 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"time set 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~30 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"fill ~ ~-33 ~ ~ ~5 ~ air\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~29 ~0 repeating_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Running 1 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~28 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-2 ~ {auto:1b}\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~27 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"tp @a -8000 130 -8000\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~26 ~0 repeating_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Running * 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~25 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~1 ~ {auto:0b}\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~24 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players test @p Running 0 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~23 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~12 ~ {auto:1b}\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~22 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players add Ticks Info 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~21 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test Ticks Info 40 *\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~20 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players set Ticks Info 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~19 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-2 ~ {auto:1b}\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~18 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"blockdata ~ ~-1 ~ {auto:0b}\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~17 ~0 command_block 0 replace {Command:\\\"\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~16 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=1,score_Dir=1] ~100 130 ~0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~15 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=2,score_Dir=2] ~0 130 ~100\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~14 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=3,score_Dir=3] ~-100 130 ~0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~13 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"tp @a[score_Dir_min=4,score_Dir=4] ~0 130 ~-100\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~12 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players remove @a Remain 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~11 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~10 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"execute @p[score_Dir_min=2,score_Dir=2] ~ ~ ~ scoreboard players add @a Iter 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~9 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~8 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"execute @p[score_Dir_min=4,score_Dir=4] ~ ~ ~ scoreboard players add @a Iter 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~7 ~0 chain_command_block 0 replace {auto:1b,Command:\\\"scoreboard players test @p Remain 0 0\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~6 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players operation @a Remain = @p Iter\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~5 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players add @a Dir 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~4 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players set @a[score_Dir_min=5,score_Dir=5] Dir 1\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~0 ~3 ~0 chain_command_block 8 replace {auto:1b,Command:\\\"scoreboard players add RadiusCompletedSoFar Info 100\\\"}\"},
{id:commandblock_minecart,Command:\"setblock ~ ~-2 ~ command_block 0 0 {auto:1b,Command:\\\"fill ~ ~ ~ ~ ~2 ~ air\\\"}\"},
{id:commandblock_minecart,Command:\"kill @e[type=commandblock_minecart,r=5]\"}]}"},
Passengers:[{id:falling_block,Block:redstone_block,Time:1,Passengers:[{id:falling_block,Block:activator_rail,Time:1}]}]}

Quote from Hozque»

I am running the most simple command ever in a repeating command block, /execute if entity @a[x_rotation=175..-175]
But for some reason it's outputting "Failed test" no matter what i do.

Any advice?

You're probably putting in the wrong angle. Try 30..50 first, and slowly extend you angle. Then you'll find the answer by trial and error.

Quote from mun8mun»

Like, I assign a loot table to a chest, but items only generate when a player opens it. Any way to generate the random items without player interactions?
(I'm trying to make a randomizer in 1.12.2)

Long story short, go 1.14 and use /loot.

If you insist in using 1.12.2, it'll be way more complicated and inconvenient.

Of course, check the comments and you'll realize that people can post 1k comments in the first few seconds.

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.

Not bad. We better bump this thread before archive.

Quote from Ambiguous_Chameleon»

Maybe someone can help me out here. This has been driving me insane the past few hours.

For this project I'm doing, I'm basically trying to take an item from a player's slot, copy that over into an item I've summoned that acts as the "mold", and then delete that item from the player's inventory. The effect is that the player's item is dropped to the floor, and they are able to pick it back up. These are the commands I use to make this happen:

/execute as @p[nbt={Inventory:[{Slot:9b}]}] at @s run summon item ~ ~ ~ {Tags:["ItemMold"],Item:{id:"minecraft:rabbit_stew",Count:1b,tag:{CustomModelData:1b}},PickupDelay:60s}

/execute as @p at @s run data modify entity @e[tag=ItemMold,limit=1,sort=nearest] Item merge from entity @s Inventory[{"Slot":9b}]

/execute as @e[tag=ItemMold] at @s run data remove entity @s Item.tag.CustomModelData

/replaceitem entity @a inventory.0 air

I think the logic is pretty solid and should be working correctly and it does work initially, but I've been hitting a weird snag:

Placing an item in that slot over and over in succession fills up my hotbar with ghosts of that item (in this case, an apple). I know they are there because I can press Q to drop them to the floor, which causes them to materialize. But at the same time, there is no tooltip or any indication that they actually exist when I mouse over them, nor is my hand model hidden like it would be if I was holding an item.

When swapping between empty slots in your hotbar, your hand bobs up and down, as you can see with the three truly empty hotbar slots on the right. Swapping between the ghost slots, my hand remains steady, again indicating that something is supposedly there.

However, if I place a real item in a ghost slot instead of pressing Q over it, that outright DESTROYS the ghost item and removes it from my inventory. It's as if the ghost item is in an existential limbo and is capable of either fully becoming an item if I drop it with Q, or being destroyed if an item is placed in that slot.

Is this on me and the way I coded things, or is this just a bug? Any uh... insight would be greatly appreciated

Go Survival/Adventure mode and try again. If that works, then I'll say I encountered this issue before when I tried to lock player slots in a map.

Quote from s_leroux»

I'm playing with the ", courier, monospace">/data command for a while in MC14.2, but I can't find a way to access items by index when a NBT path selector matches several items.

Let's say for example I want to know which slot of a chest containing pumpkins. I can write that:

/data get block x y z Items[{id:"minecraft:pumpkin"}].Slot

However, it will work only if pumpkins are found in one slot. If the chest has several slots filled with pumpkins, ", courier, monospace">data get produces the error "only one NBT value accepted". So, is there a way to select only the first item (or at least only one item, being the first or not) matching an NBT path?

FWIW, I tried several variations with no luck:

Items[{id:"minecraft:pumpkin"}][0].Slot
Items[{id:"minecraft:pumpkin"}].[0].Slot
Items[{id:"minecraft:pumpkin"},0].Slot

Here's a slightly rough solution.

First, place another container under that target chest. Another chest can do. Or, summon an entity below. It has to hold the target item tho.

Second, either put that special item in the first slot of the chest under, or use /summon to include that item on the entity's hand.

That special item can be anything, not necessarily a pumpkin even if you're finding a pumpkin. But it just needs to have the tag:{} nbt tag.

Example: /setblock ~ ~ ~ chest{Items:[{id:"minecraft:stone",Count:1,tag:{}}]}

Third, use your command in a slightly different way.

Sth like this: /data modify block <coords of chest under> Items[0].tag.Slotz append from block <coords of target chest> Items[{id:"minecraft:pumpkin"}].Slot

After this, that item (stone in this case) has all the slots stored.

Lastly, get the first slot with sth like this:

/data get block ~ ~ ~ Items[0].tag.Slotz[0]

Ta-da!~ *cough* Here you go. Modify it so that it suits your situation.

I know it might be a bit late to reply to this thread, but i have found your answer:
For the llama spit to deal damage, it needs a proper llama as its "owner". Its a bit complicated but to simplify it, there must be a llama with the same uuidleast and uuidmost as the spit's owneruuidleast and owneruuidmost

Use this command to summon your llama spit (change the motion and coords as needed)
/summon llama_spit ~ ~1 ~ {Motion:[0.0,0.0,0.0],Owner:{OwnerUUIDLeast:13L,OwnerUUIDMost:13L}}

and this one to summon a nice llama to "own the spit

/summon llama ~ ~1 ~ {UUIDLeast:13L,UUIDMost:13L,Invulnerable:1,NoAI:1,Silent:1}

so long as the llama exists in the world, the spit with matching uuids with be able to deal damage! I hope this helped answer your question!

quote=YMbrothers

I'm not trying to fully copy the video's design, cuz I have to add sth else.
Lemme try to break it down...

1. Bottom of the main drop? which picture? Pics #2 & #3 ~3 up from the enchanting tables

2. Em, spawn rate is just saying guardians spawn per second I guess?

3. It's not fully made, in fact, since I wanna make this in a server, this is just a rough work. Hence, there is no hoppers below. If the corpse of the guardian rly have a great impact on the spawn rate, plz tell me.
The question ablout how you are determining spawn rate came from seeing threads where players infer spawn rates from the number of drops collected (which works IFF all the mobs die in positions where the drops are collected).
If you use something like carpet mod or watching the entity counts in the f3 screen this won't be an issue.
[Assuming you can summon a player to stand in the kill room(I know one can do this with carpet mod, but don't think it's possible in vanilla), watching in spectator mode will also work; otherwise being in spectator mode avoids triggering mob spawns.]

4. Well, I don't rly like the 2x4 one. I just want a 1x4 one.
The 1x shaft may lower efficiency as the guardians may be a bit less likely to be pushed into it... how much I don't know, much less whether the difference would be enough to be important to you.

5. I took a screenshot from the bedrock to show you there they aren't caves nearby to spawn mobs.
I understand... the perspective is unusual enough it took me a while to understand why it looked as it does.
RE the caves being lit: in pic #3 [4hLrs5P.png] there are an enderman, a spider, a skeleton and two zombies visible on the right. The shot was obviously taken in spectator mode, but this still implies they are with in 128 of the farm.

6. The floor and the "top water"(or water tank, whatever) is at y:39, so I stand at y:40. Does it have a big impact on the spawn rate if the bottom of the water tank is at y:39 instead of y:38? Another question that I've never pushed the optimization enough to be able to answer.... :sigh:

So yeah, again, thanks for the answer.
(The reason I made the floor at y:39 is because I heard that in the monument area, mobs don't spawn at y:40. So there won't be hostile mobs spawning at the platform other than guardians.)
No mobs (other than guardians) spawn within the 59x59 footprint of the OM from y=39 up to sea level; they will spawn in caves under it as well as in the area between the pillars (if dry)

I'm unclear about how much any of these effects the XP generation rate; what I did was try to find every differece between gnembon's desgign in his video and the test version you built with the idea that a number of minor differences might interact to produce the results you were seeing..

WRT the mention of view/render distance in the above posts, I'm unable to judge from the pics, but setting it to 12 (default) seems most likely to duplicate that part of gnembon's conditions.

I don't know Mr YMBrothers - it's puzzling!

I observe that there aren't very many water spaces in this design, so it won't compete that well with dark caves if you have left any around.

You might want to fly around in spectator mode and nail the rest of the caves within 128 of your AFK position, and make sure that you're AFK'ing 24+ spaces below or away from the water tank.

I have a guardian spawner that's working great even though apparently there are still hostile mobs around someplace (didn't do the spectator mode trick.) I believe it's likely doing well just because it's so huge - something like 8000 spawnable spots in it.

I tried setting view distance to 9 chunks under my guardian spawner and at least in my case there was little difference. So DuhDerp had generally a good point there. Still, try ten chunks!

Quote from YMbrothers»

If the definition of efficiency here is xp per hour, Design 2 is better?
Yes

Also, does that mean if there's some floating sand above the ocean monument, it reduces the spawn rate?Yes, when attempting to find a valid position on which to spawn mobs the game checks from bottom up so confining the build to the lowest few sections [16x16x16 volumes] decraeses the time per spawn check. Any non-transparent block in an upper section will result in the software checking up to and including that section.

Quote from YMbrothers»

Thanks for all the replies.

Lemme try to recall what you guys are saying, just in case I made them wrong:

1. The 2 block spacing is fine. (You know, if the wall is positioned incorrectly, idk whether guardians will spawn outside the wall or not)

2. The farm doesn't need to be centered in the monument structure. Yet if I'm using Gnembon's design, the kill chamber must be near the center of the farm itself, while the whole farm (The 十 shaped farm) can be on the edge of the monument.

3. So the light level (only sunlight) does affect the spawn rate. (Does that mean I can use pistons to move the covering block, so it can control the spawn rate?)

4. Well, Gnembon's design s the most efficient

5. Spawners do affect the spawn rate, so it's best to not put it below the kill chamber of the guardian farm. (Sad )

6. Y:39-63

If there's any mistake, please correct me.

1. Guardians only spawn within the 58x58 footprint of the farm, between Y39 and Y63 (according to the wiki). There is some ambiguity in the wiki about guardian spawns above sea level, so it's possible they may spawn higher (assuming there is water to spawn in), but I have not tested that myself. Note that no other hostile mobs will spawn in that area. So if you clear the volume the monument occupies of water you don't have to worry about lighting up rooms, as guardians are the only hostile mob that can spawn in the monument location. If you have any space outside the 58x58 footprint, or under the floor level (Y38), then normal hostile mob spawning rules apply.
2. Guardians have an equal chance of spawning anywhere within the monument volume, so whether or not you need to center anything will depend on the design of your farm.
3. Sky exposure affects spawning, not light level. If the spawn water block is exposed to the sky, either directly or indirectly (below liquid or fully transparent blocks) spawning will fail 95% of the time. Cover your spawn area.
4. Probably, he's pretty awesome.
5. Monster spawners themselves are not affected by the mob cap. They will happily keep spawning mobs until they crash your game or server. However, the mobs they spawn are added to the mobs cap, so if you have an active spawner nearby it can and will affect your guardian spawns. If you want a collection only dungeon grinder which quickly dispatches the spawned mobs, then it probably won't make too much difference. If you want an XP farm where you let the mobs accumulate, then that will slow down and possibly stop guardian spawns (if you want XP, then use your guardian farm for that, it's much faster than a dungeon grinder).
6. I'm pretty sure when I tested that, guardians also spawned at Y38, but it's been awhile so test that for yourself.

quote=YMbrothers;

Replies

1. The 2 block spacing is fine. (You know, if the wall is positioned incorrectly, idk whether guardians will spawn outside the wall or not)

Guardians will not spawn outside the monument footprint. So long as the only water within the monument volumn (58x58 & y=39-63) is in the guardian farm, the position of the exterior wall will affect only base design, not the farm.

2. The farm doesn't need to be centered in the monument structure. Yet if I'm using Gnembon's design, the kill chamber must be near the center of the farm itself, while the whole farm (The 十 shaped farm) can be on the edge of the monument.

"the kill chamber must be near the center of the farm itself" Only true for maximum rates, a farm (including gnembon's various designs) will work (albeit slower) with an off center kill chamber.

Because mobs do not spawn centered in a block, I would place the edge of a farm 1 block in from the edge of the monument for 'safety', but I am aware of no information that the one covered water space within the monument is favored over any other.

3. So the light level (only sunlight) does affect the spawn rate. (Does that mean I can use pistons to move the covering block, so it can control the spawn rate?)

Sky view (as is used to determine village houses) matters, not light level. (In this context, "sky view" means the topmost water block in a column has nothing but transparent blocks above it.)

[Adding an opaque block above a column will change the spawn rate for that column (removing the 95% fail constraint), but barely reduce the light level (from 15 to 14 when standing directly beneath a single solid block).]

I've not seen a design using rate control pistons (oddly enough, pistons are considered transparent ), but this should work… [A similar mechanic is used in Tango Teks' self assembling village iron farm designs.]

4. Well, Gnembon's design s the most efficient

Correct, to the best of my knowledge.

5. Spawners do affect the spawn rate, so it's best to not put it below the kill chamber of the guardian farm. (Sad )

True.

6. Y:39-63

Correct, to the best of my knowledge.

Couple links for general reference:

https://minecraft.gamepedia.com/Guardian

https://minecraft.gamepedia.com/Ocean_monument

https://minecraft.gamepedia.com/Tutorials/Guardian_farming [old but may still be somewhat useful]

Your questions:

1: Not sure what you are asking; this appears to show that you have placed your initial walls (for draining the monument exterior) so as to leave a two block gap between the walls and the monument proper. While important for any base you construct, the exact positioning of the walls does not matter for Guardian farming, so long as all the spawnable water is removed.

2: Centering the killroom in the Ocean Monument footprint is unimportant so long as the killroom is centered in the farm footprint to minimise the mean [arithmatic average] distance spawning guardians need to be moved and thus the maximize the throughput. [Few guardian farms take up even a major fraction of the 58x58 footprint of the Monument.]

3: From the Gaurdian page "they can spawn only if the spawning block and the block below the spawning block are water (regardless of stationary water or flowing water), and the block above the spawning block has no collision mask (air, water, sign, etc.)."

[The wiki has been known to contain errors however and I seem to recall spawns in 1 deep water so I'd want to test that before relying on it.]

Note that removing all solid blocks will not be effective.

4: Mumbo Jumbo's build [the linked video] appears to be based on a gnembon design the last update of which I am aware is LINK .

The main changes involve:

• increasing the air gap under the water and above the lava
• swapping the glass for Redstone Blocks. (Later comments indicate Observers also work.)

5: Hostile mobs in the world will occupy part of the mob cap, whether they spawn 'naturally' or from a spawner makes no difference. Assuming there is a spawner near where you want to locate your guardian farm, arranging things so that you are >16 blocks from the spawner is advised. [While not optimal, a few mobs from the spawner created when you pass by it on the way to the guardian farm will not have too great an effect as these will despawn normally. More likely, the guardian farm will impact the rates if you try to use the spawner.]

6: The guardian page states "Most of them will spawn in between Y=39(floor of the ocean monument) to Y=63", but does not define "most". Given that Guardians must spawn in water, it should not be difficult to prevent spawns in undesirable areas.

[Anecdotally:

I've never seen one spawn above Y=63 (although I've also never tried to create that situation)

Spawns do not appear to occur in the water based item transport system near the killroom in this video (@~12m00). q.v. LINK ]

The design you're attempting has been made for maximum efficiency; I've never used that design as the added complexity of the build process has been off-putting and I've never had the need/desire for that much prismarine.

Good luck, looking forward to the progress reports…

1.13 snapshots are going to be available "soon". And I've gotta say, it's one of the more contested updates in Minecraft's history. The back-end technical changes, such as removing the block limit, seem to be uncontroversial. Data Packs, which may eventually become a considerable alternative to Forge, are very much underhyped in my opinion, but there's no considerable dislike for this addition.

However, there's one big change that seems to have a sizable portion of the playerbase disgruntled: The Default Resource Pack is being redone, to have the textures look nicer and have more consistency with one another. Many seem to dislike this, and I think the reasoning that many have for this is very much flawed.

The 2 big complaints you'll hear are "It doesn't look like Minecraft!" or the more blatant "We're used to this! It shouldn't be changed!". This is grumpy old man talk, yet it comes from people my age. Minecraft is a changing game. It is growing and evolving and will continue to do so for as long as people are playing it. Just because you're used to something doesn't mean it can't be improved. The Default Resource Pack is quite inconsistent, with different blocks looking like they really don't belong in the same game. Obsidian gets a mention for looking completely out-of-place in Minecraft. With this retexturing, the game will look smoother, and overall nicer. It's not what you're used to, but it's an improvement, and you should become used to it. Minecraft is changing and evolving and it shouldn't stop doing so, just because something has went unchanged for an extended period of time. Simply put, people need to take off their nostalgia goggles and view these new textures with no bias towards what one is used to. If people do this, they'll quickly realize that this new default Resource Pack is an improvement to the game.

This same sort of thing happened when 1.9, the Combat Update, was revealed. People got upset because it changed things. People were used to the equipment-based combat system, so when it was being reworked into skill-based combat system that was overall an improvement to the old one, people got upset because they didn't want to have to get used to the change. But then, after a while nobody minded the new combat system, because it wasn't actually bad, it was better than the old one, AKA the click mashing contest. Quite simply, people hated it simply because it changed things, which is a terrible mentality to have when playing a game that's constantly evolving.

TL;DR I think people should stop being so against the idea of Minecraft evolving into a better game, and be more willing to embrace these sorts of changes.

Quote from zccyfiberglass»

They will defeat the Witherstorm, at the cost of someone's life.
Characters will argue. And hopefully, Petra and Lukas will be a thing.

┳|
┳┻| _
┻┳| •.• ) -Daddy,are all the copy-pasters gone?
┳┻|⊂ﾉ
┻┳|


/﹋\
(҂`_´) -NOT YET SON,THEY'RE GETTING STRONGER EVERYDAY !! AGHHH
<,︻╦╤─ ҉ - - - - - - - - - - - - - - - -/﹋\