2

Follow

"Launcher" selector

1. What Feature Is "Launcher selector"?
This feature is a selector that executes all commands to "the person who launched the command block" if the command block is used to execute them.

2. Why this feature needed?
The command block currently only has selectors for nearby players, all players, random players, and all entities. There is nothing wrong with this on a solo map. However, the problem becomes apparent when users started to create a multi-player map.
For example, let's say you start a conversation with an NPC and a player approaches you in the middle of the conversation. Then the command is not for the player who started the conversation, but for the player who passed by. This can be a spoiler for the player who is passing by, or it can cause the player who started the conversation to miss the important part.
Even in a less complicated case like this, if users create a teleportation command with the @p selector, for example, and it's pressed at the very edge of the reach, someone nearby will be teleported, and user who pressed button won't be teleported. This is very serious, and this is why we need a "selector for the person who launched the command block".

3. What we require for that selector
This is an important part. We need to decide how far we want to go to be an "launcher".
I believe that the entire command block launched by the player using something that generates power (e.g buttons) would be within the scope of the selector. This is something we need to consider.

Registered User shared this idea

• September 26, 2020 00:53
• Report a Concern

Please sign in to leave a comment.

• 1

  Registered User commented

  Comment actions Permalink

  • September 26, 2020 23:29
  • Edited
  • Report a Concern
  • Comment actions Permalink

  You do have something very similar to this: The current entity selector or @s. It basically executes the command on the sender.

  To change the sender, you can use:
  /execute as (selector) run (command)

  And then inside your command, you use the selector @s. I am not sure if it is possible to pass the selector from one command block to another (for example in your case, the blocks responsible from saying the npc's lines would take the information from the first command block, meaning even if someonr passed by they would have been already assigned to you), but you can use a function (a text file of type .mcfunction inside .minecraft/daves/YourWorld/datapacks/YourDatapack/YourDatapack_data/functions that executes multiple commands at once, so you can do:

  
  /execute as @p run (function)
  And inside the function use the @s selector.

  It's a little more complicated than that but I am on phone and it would be hard to explain more details, I hope you understand that and good luck with your project.