Suggestion Closed - Already Exists

Placeholder Support for Target Options

#2203 opened by Unknown 5 years ago

Unknownreported this suggestion

Summary

Instead of just using Ignore=Player, having Ignore=<target.name> or Ignore=<global.var.target1name>

Usage

When combined with other variables, you can get a global.target1name variable to be equal to <target.name>, and then get global.target2name to be equal to <target.name> but ignoring the first one, so it essentially gets the SECOND player that would come up in this order.

VariablePlayer1: Skills: - setvariable{var=global.target1name;val=<target.name>;type=STRING} @NearestPlayer{r=10} - skill{s=VariablePlayer2} @Self VariablePlayer2: Skills: - setvariable{var=global.target2name;val=<target.name>;type=STRING} @NearestPlayer{r=10;ignore="<global.var.target1name>"} - skill{s=VariablePlayer3} @Self

Value

This would allow further implementation of lists within text for either addressing groups of people in dialogue, or developing scoreboards where more than 1 person is involved.

Priority

Low. It would be extremely valuable, if not overlooked, to have, but isn't necessary for the base function of the plugin or its content.

Implementation

Add STRING Placeholder support to the arguments for Target Options. ~Enhancement

Unknowncommented

This is already possible using TargetConditions and the name condition, which supports placeholders.

Sign in to join the discussion.