• 1

    posted a message on Need help converting this command.
    Quote from Crazy_Dave»

    You're trying to set nbt and a score using /scoreboard

    That's like fitting a car into woodchipping machine

    You do not need a score to determine when the tnt will blow up.

    Just use this

    kill @e[type=tnt,nbt={Fuse:1b}]



    Actually, no. The direct equivalent command to the one in the first post is:

    1.12: scoreboard players set @e[type=tnt] TNTGoBoom 1 {Fuse:0b}
    1.13: scoreboard players set @e[type=tnt,nbt={Fuse:0b}] TNTGoBoom 1 


    A lot of 1.12 commands have this setup, where NBT was not included inside a target selector, and NBT is specified as the last command argument.

    I agree though that the asker should consider a simpler method if possible.

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Need help with scoreboards and teams

    /execute if score […] = […] is to compare a score with another player's score. In this case, you are basically saying "execute if my Kills score is equal to the Kills score of the player named 1."

    You can fix this by using /execute if score […] matches 1 instead.

    In addition, remove run execute from your command: it does basically nothing.

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Redstone ATM with 2-Step Verification

    I am happy to announce that this machine now supports 40 accounts! Download the updated version today!

    Posted in: Redstone Creations
  • 1

    posted a message on Expected curly bracket where it shouldn't

    It expects a closing bracket because the quotation marks are ending the Command string. Escape quotation marks with a \:

    {BlockState:{Name:\"minecraft:command_block\"}}

    You'll also need to do this with a few other quotation marks.

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Button Combination Lock

    Commands is the better way to go if you're making a map. This will make your machine more efficient.

    The way I'd do it is use a score for the correct number of buttons pressed so far. Then, when they press a button, based on the score, see which button they were supposed to push next, and if the actually pressed button matches, increase the score by 1, otherwise reset it to 0.

    First setup the scoreboard objective:

    scoreboard objectives add code dummy


    For example, say your combination is Spruce, Birch, Acacia, Dark Oak, Crimson, Warped. The Spruce button would run the following commands:

    execute if score @p code matches 0 run scoreboard players add @p code 1
    execute unless score @p code matches 0 run scoreboard players set @p code 0
    Posted in: Redstone Creations
  • 1

    posted a message on Killing entity based on sign data

    Try tags. Tag the player, and reference it in both the sign and the command:

    tag @e[name=target] add test
    data modify block 80 43 -182 Text1 set value '{"selector":"@e[tag=test]"}'
    kill @e[tag=test]
    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Item Frame Detection
    00: [
    01: type=minecraft:item_frame,
    02: limit=1,
    03: sort=nearest,
    04: distance=1,
    05: nbt={
    06:   Item:{
    07:     id:"tripwire_hook"{
    08:       display:{
    09:         Name:'[{"text":"Loot Box Key","italic":false}]'
    10:       },
    11:       Enchantments:[{id:loyalty,lvl:1}]
    12:     }
    13:   }
    14: }



    A few problems with your code:

    • Line 07: That is invalid syntax. Unlike commands, NBT data for items is stored in a tag tag that is nested at the same level as the ID. For example:
    • Item:{
       id:"minecraft:tripwire",
       tag:{
       Enchantments:[…]
       }
      }

    • Line 07: You need to specify the namespace (minecraft:tripwire ) for it to work.
    • Line 14: Did you forget to close the end of the target selector with a ]?
    Posted in: Commands, Command Blocks and Functions
  • 2

    posted a message on Redstone ATM with 2-Step Verification

    This is a redstone banking machine that I made a while ago. Unlike other ATMs, this ATM includes an extra security feature, requiring users to submit two items to access their account: a user ID and their own secret passkey item, mimicking the username and password situation on most websites.

    Features

    • Simple UI: Just a minecart, a button, and a dropper.
    • Light indication system: Shows users whether their transactions are accepted or not.
    • Security: Providing an incorrect passkey will cause their transaction to be declined. This includes trying to use a different account's passkey; the user ID and passkey must be tied to the same account.
    • Flexibility: The most advanced feature of this machine is the ability for it to automatically change a user's passkey without the user going behind the scenes. It all happens from the UI in the front.

    This Minecraft map works best in 1.16.x. Download it from MediaFire, and be sure to only move the Map folder into your world saves, not the documentation.

    Posted in: Redstone Creations
  • 1

    posted a message on Give all of one type

    Not all in one command. There are some alternatives though:

    • Using multiple commands in a chain:
    • give @s sandstone
      give @s chiseled_sandstone
      give @s sandstone_slab


    • Using a function to run those commands
    • Placing them in a chest, then on command, clone and break the chest on the player
    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Hoppers and Droppers

    That's due to a bug called quasi-connectivity. It affects droppers, dispensers, and pistons, and the bug is that anything that can power the block above it will also power the dispenser/dropper/piston itself. In your example, the dropper is powered because the space above it (a hopper) is being powered.

    The dropper doesn't realize the redstone block is powering it until is powered once, and then it becomes locked.

    Posted in: Redstone Discussion and Mechanisms
  • To post a comment, please .