/trigger Command Needs Critical Improvements

The /trigger command has severe limitations that hurt datapack development:

Problems:

1. No Target Selectors

   • Can't do: /trigger menu set 1 @a[tag=admin]

   • Forces: /execute as @a run trigger menu set 1

2. Manual Enable Spam

   • Must enable every tick per player

   • Creates massive tick overhead

   • No auto-enable option

3. Limited Operations

   • Only set and add

   • No toggle, remove, operation

4. No Permission System

   • Either everyone or manual per-player

   • Can't restrict to tags/teams

Current Workaround (BAD):

# Every single tick...
execute as @a run scoreboard players enable @s menu
execute as @a run scoreboard players enable @s settings
execute as @a run scoreboard players enable @s admin
# Repeat for every trigger...

Proposed Solutions:

/trigger menu set 1 @a[tag=admin]
/scoreboard players enable @a menu {autoEnable:true}
/trigger flag toggle
/trigger panel set 1 {requireTag:"admin"}

Impact:

• Menu systems require constant enable loops

• Forces bad performance patterns

• Makes datapacks harder to maintain

• Unnecessary complexity

Please modernize triggers to work like normal scoreboards with optional permissions!