Discuss Minecraft's scripting and modding capabilities, including APIs, tools, customization, automation, and creator workflows. Share ideas and feedback on how players and creators can extend and customize Minecraft.

27

@u (Entity Detector)

6 Comments

Post a new comment:

Please sign in to leave a comment.

Sorted by oldest
  • 1
    Registered User commented
    Comment actions Permalink

    i like it BUT it should be

    @s

  • 0
    Registered User commented
    Comment actions Permalink

    That is already in the game. It is @p (nearest player) or @s (self)

  • 0
    Registered User commented
    Comment actions Permalink

    This is literally @e(emtity selector) and you can select entities with @s or @r too

  • 1
    Registered User commented
    Comment actions Permalink

    It's not possible to tell "who" activated a command block. The command block runs its command when it receives redstone power, which can come from anywhere!

  • 1
    Registered User commented
    Comment actions Permalink

    tryashtar, yeah i know that it's almost impossible v':, but i believe in that 1% that it can be added, and it will simplificate the mapmaking.

  • 2
    Registered User commented
    Comment actions Permalink

    It seems easy to determine "who" activated redstone just by looking at it, but for the game to do that, it would need to keep track of a player UUID for every piece of redstone dust, and potentially every single redstone component, entity, and block that could be modified as part of a chain reaction. Storing all that is currently not possible, and would cause tremendous overhead all for a tiny result.

     

    Since it's not going to happen, you could always use a sign! Signs can run commands when clicked on, and the @s selector will target the player who clicked the sign!