Minecraft – How to replace multiple items with same count of a different item

minecraft-commandsminecraft-java-edition

I am trying to make a custom food recipe. I'm using spawn eggs with /replaceitem because spawn eggs are not obtainable in survival. This works fine when the player crafts only one spawn egg, but when I scroll over multiple spawn eggs, I receive only 1 of the custom food. BTW this food uses custommodeldata, so I can't simply add it into the crafting recipe. I cannot seem to find a way around this. If I make the item non-stackable, such as a piece of armor, mass crafting would be impossible. If I make an item.dropped scoreboard, the player could keep the item and use it to spawn mobs (griefing or for own profit.)

My command:

execute as @a[nbt={SelectedItem:{id:"minecraft:villager_spawn_egg"}}]
run replaceitem entity @s weapon 
minecraft:melon_slice{CustomModelData:10000101,display:{
Name:"{\"text\":\"Blue Melon Slice\",\"italic\":\"false\"}"}}

My problem is that the command does not see item count, as it is often used for weapons and armor only.

One way I thought to fix this issue is by storing the amount of custom food crafted in a scoreboard item and then giving the player that same count of the custom food, but I do not know how to do this; consequently, I don't know if this works.

Is there a way to do this method, or is there another, simpler method possible?

Best Answer

You can summon the melon slice at the player's position in item form (with a small pickup delay) and then use /data to modify the Count property

To summon the item:

/execute at @a[nbt={SelectedItem:{id:"minecraft:villager_spawn_egg"}}] run summon item ~ ~ ~ {PickupDelay:10,Item:{id:"minecraft:melon_slice",Count:1,tag:{CustomModelData:10000101,display:{Name:"{\"text\":\"Blue Melon Slice\",\"italic\":\"false\"}"}}}}

to modify the Count property:

/execute as @a[nbt={SelectedItem:{id:"minecraft:villager_spawn_egg"}}] at @s store result entity @e[type=minecraft:item,limit=1,sort=nearest,distance=..0.2] Item.Count int 1 run scoreboard players get @s <objective_with_count_data>

and then clear the spawn egg from the player's inventory. There's the concept.

Related Solutions

Minecraft – Detect a dropper with items in it without /testfor

The detect function of /execute does not accept NBT data, only an ID and Damage value.

You will instead need to use /testforblock, and if needing multiplayer-friendliness, mixing it with CommandStats.

Prerequisites:

Objective to hold the CommandStats value.

/scoreboard objectives add CraftSuccess dummy

Applying the AffectedBlocks trigger to players, which will set the player's score based on the success of commands that specifically affect blocks, such as /testforblock. This may need to run on a clock in the event new players can join at any time.

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

In order for CommandStats to modify a target's score, that target must be tracked on the scoreboard prior. This may also need to run on a clock for the same reason as before.

/scoreboard players add @a CraftSuccess 0

Detection:

The following must be run in numerical order.

Cause players to run the necessary /testforblock command.

/execute @a ~ ~ ~ /testforblock ~ ~-1 ~ minecraft:dropper 1 {Items:[{id:"minecraft:blaze_rod",Slot:1b,Count:1b,Damage:0s},{id:"minecraft:blaze_rod",Slot:4b,Count:1b},{id:"minecraft:stick",Slot:7b,Count:1b}]}

As a result, the executing player will have their own "CraftSuccess" score set equal to the number of blocks found by the /testforblock command. If the command failed, their score is set to 0. If the command succeeded, their score is set to 1. You'd then target players based on their score.
```
/scoreboard players set @a[score_CraftSuccess_min=1] LSC 1
```

As a side-note, you should never mix @a as an executor and @p as the nested command's target if you're intended to target the same player. While @a can target dead players, @p cannot. That means that while the executor can run /execute while they're dead, they will not target themselves and instead target the nearest-living player. This can severely hurt accuracy and possibly break a target-sensitive mechanism.

The solution is to use the same selector when needed. For dead player targeting, you'd use @a as the executor with @a[c=1] as the nested selector:

/execute @a ~ ~ ~ /say @a[c=1]

For living-only players, you'd use @e[type=Player] with @p:

/execute @e[type=Player] ~ ~ ~ /say @p

It is also for this reason that CommandStat targets should use @a[c=1] when working with players, as this ensures there will not be an unintended target having their score modified.

Minecraft – Decrease Stack Size in Chest

This is possible somewhat easily since 1.13 thanks to /execute store.

As a preparation, you need some scoreboard:

/scoreboard objectives add temp dummy

Then you need the value 1 somewhere. Here I set it for the dummy player #1 (which can't be a real player name and does not appear in scoreboard displays):

/scoreboard players set #1 temp 1

When you actually want to decrease the item count, first store the amount in a scoreboard:

/execute store result score @s temp run data get block ~ ~ ~ Items[{Slot:0b}].Count

I specifically check for Slot:0b instead of simply using the index (Items[0]) as a workaround of a bug.

Now you need to subtract 1:

/scoreboard players operation @s temp -= #1 temp

And store it back to the chest's NBT.

/execute store result block ~ ~ ~ Items[{Slot:0b}].Count byte 1 run scoreboard players get #1 temp

Best Answer

Related Solutions

Minecraft – Detect a dropper with items in it without /testfor

Minecraft – Decrease Stack Size in Chest

Related Topic