Targeting 🎯
Execute commands on the actual player who triggered them.
Overview
Targeting introduces a new selector, @t, designed to solve one of Minecraft's long-standing limitations: reliably identifying the player who activated a redstone-triggered command.
In vanilla behavior, command blocks triggered by buttons, pressure plates, or other redstone inputs lack direct context about who caused the activation. This mod bridges that gap by dynamically binding the triggering player to command execution.
Key Feature:
@t Selector Targets the player responsible for triggering the command block, whether via: Button press Lever toggle Pressure plate Any redstone interaction linked to a command block
Why This Matters?
Without Targeting, mapmakers and server developers often rely on:
- Proximity-based selectors (@p)
- Complex scoreboards
- Detection loops
These approaches are unreliable, inefficient, or unnecessarily complex.
@t provides precision, simplicity, and performance in a single selector.
Example Usage Scenario: Teleport the player who pressed a button
Command Block Command:
/tp @t 100 100 100
What Happens:
Player presses a button connected to the command block The command executes Only that specific player is teleported to (100, 100, 100) Comparison Selector Behavior @p Nearest player (can be incorrect) @a All players @s Command executor (not useful in redstone context) @t ✅ Player who triggered the command
