Selector

Overview

Fetches one or more entities based on a Selector-Expression, which is either relative to the recipient of the message (if provided when calling the API) or the explicitly provided location (that always takes precedence). The Code-Blocks are only available within the browser is handed an implicit environment-variable called Code-Blocks are only available within the browser which is a list of type PlatformEntity, as well as a Code-Blocks are only available within the browser, which is the Location which served as an origin.

<selector

  selector: selector

  ↪ Selector to decide entities with

  at: coordinates(null)

  ↪ Explicit origin of the selector

  renderer: markup(null)

  ↪ Appearance-dictating markup; introduces:

  ↪ - selector_result: List<PlatformEntity>

  ↪ - selector_origin: PlatformEntity

/>

Example

Plain Appearance

When not providing a custom renderer, the default implementation will mimick the plain look and feel of the Code-Blocks are only available within the browser command.

Code-Blocks are only available within the browser

At Location

In order to select entities at a custom position, simply supply the desired coordinates.

Code-Blocks are only available within the browser

Distances And Teleportation

Since there are no restrictions when it comes to the complexity of the renderer, nuanced scenarios like the following, displaying a nicely-formatted distance as well as providing a teleportation-command that's not only displayed when hovering but also executed when clicking is no challenge whatsoever. Granted, calculating the euclidean distance may look a bit convoluted, but we're taking it to the extremes here.

Code-Blocks are only available within the browser