[Enhancement] Adding more Argument Types

(long time, no talk) Please describe your suggestion I was starting to use the api, when I realized it was missing some argument types, I tried to put these from most useful to least useful:

• rotation: An angle, represented as 2 numbers (which may have a decimal point, but will be moved to the center of a block if none is specified). May use relative locations with ~.
• column_pos: Represents a column position.
• int/float_range: An integer/floating-point range of values with a min and a max.
• block_predicate: A block, or a block tag.
• block_state: A block state, optionally including NBT and state information.
• nbt: An NBT value, parsed using JSON-NBT rules.
• swizzle: A collection of up to 3 axes.
• item_slot: A name for an inventory slot.
• entity_anchor: The entity anchor related to the facing argument in the teleport command, is feet or eyes.
• entity_summon: Represents an entity summon.
• dimension: Represents a dimension.
• color (minecraft): Represents a color used in chat formatting. Ex: red, green, reset
• component: Represents a raw JSON text. (Not just Chat/Book)
• time: Accepts a single-precision floating point number suffixed with a unit. Units:
  • d: an in-game day, 24000 ticks;
  • s: a second, 20 ticks;
  • t: a single tick; the default unit.
• score_holder: Something that can join a team. Allows selectors and *. (has a property that is singgle/multiple)
• nbt_path: A path within an NBT value, allowing for array and member accesses.
• nbt_tag: Represents an NBT tag in SNBT format.
• message: A regular message, potentially including selectors.
• scoreboard_slot: A scoreboard display position slot. list, sidebar, belowName, and sidebar.team.${color} for all chat colors (reset is not included)
• objective: A scoreboard objective.
• objective_criteria: A single score criterion.
• resource_location: An Identifier.
• vec3: A location, represented as 3 numbers (which may have a decimal point, but will be moved to the center of a block if none is specified). May use relative locations with ~.
• vec2: A location, represented as 2 numbers (which may have a decimal point, but will be moved to the center of a block if none is specified). May use relative locations with ~.
• long: Represents a 64-bit long. It’s in brigadier, but not used by MC, so not 100% if it will work.

https://wiki.vg/Command_Data https://minecraft.gamepedia.com/Argument_types

Please supply examples of the desired inputs and outputs I mean these Arguments are explained above, I guess I’ll do this one, as the wiki’s description isn’t great: /tell john Hey look at all the players: @a Shows to John “Hey look at all the players [Minenash, Steve, john]”

---

I know you can’t add all 25 in at once. (I think at least), but The ones high up are definitely useful.

[JorelAli]

Okay, this seems pretty reliable, I’ll use this going forward:

public Team getTeam(CommandSender sender, String team) {
	
	Scoreboard board = sender instanceof Player
			         ? ((Player)sender).getScoreboard()
			         : Bukkit.getScoreboardManager().getMainScoreboard();
	return board.getTeam(team);	
}

[Minenash]

AxisArgument sounds good. Though do you know if Location supports NaN values? If so, that might me the better y-value.

Any ideas?

As in ideas on what to do in 1.13 where it doesn’t exist?

Edit: AxesArgument might be better, as there can be more than 1