X

NOTICE

Are you sure you want to report this?

We've split up the commands, scripting and mods, and add ons category! Please be sure you get your thread in the right place.

80

Add @~

15 Comments

Post a new comment:

Please sign in to leave a comment.

  • 0
    brenn boyer commented
    Comment actions Permalink

    I like this. Voted!

  • 0
    Comment actions Permalink

    Oh, hey again Brenn Boyer.

  • 0
    Comment actions Permalink

    I like this idea. I mean, you don't know the players' Gamertag and the command block might be closer to another player. I like this idea. Voted.

  • 0
    Comment actions Permalink

    Muchos es goodante! Very good idea!

  • 1
    tryashtar ⁣ commented
    Comment actions Permalink

    Hello, good idea, but you can already do this! Try these commands:

    /tag (the player) add selected
    /give @a[tag=selected] dirt
    /tp @a[tag=selected] 0 64 0

    After you tag the player you want, you can select them in subsequent commands in your selectors.

  • 0
    Comment actions Permalink

    Neat idea would be helpful too!

  • 0
    Comment actions Permalink

    No actually this is suggested for Minecraft Bedrock there isn't tags yet*

  • 0
    tryashtar commented
    Comment actions Permalink

    In that case you should make a parity post to add tags, rather than this

  • 0
    Comment actions Permalink

    Neat idea. But it would be more helpful to me if @~ did for example the fisrt command block:/execute @p ~ ~ ~ detect ~ ~-1 ~ glass the second command block would target the players that had a block of glass underneath them and that had a returned value of success. This would make almost any creation multiplayer compatible.

  • 0
    FVbico commented
    Comment actions Permalink

    How exactly is this for java parity? No such selector exists in java edition.

  • 0
    OrcaSpiderJay commented
    Comment actions Permalink

    Bedrock too

  • 0
    tintin10q commented
    Comment actions Permalink

    Nice they added this in the form of @s

  • 0
    Guzio MG commented
    Comment actions Permalink

    It should be expanded to detect basic input, too.

    For example, if the button is connected straight to commandblock, then it should trigger on the user, who pressed it, not the closest one. I don't think about something extremely advanced, which can dig into entire Redstone machine structure, databack and everything else just to detect one player. Only basic detection. It shouldn't be THAT difficult to implement.

  • 0
    Guzio MG commented
    Comment actions Permalink

    @tintin10q

    Yes, they added, but it only works in "/execute" command. No chain commandblock support.

  • 0
    Alex Testria commented
    Comment actions Permalink

    I think this isn't needed.

    You can already do that.
    Also sometimes a previous command has more than 1 target like an execute command:

    "execute as @e[type=wolf] at @s if entity @p as @r at @s run say hi!