Skip to content

Feature request: allow multiple input types in property syntaxes #85

@Snow-Pyon

Description

@Snow-Pyon

Is your feature request related to a problem? Please describe.
Right now, property expressions/conditions only allow a single type to get the property from. This really limits the usefulness of property syntaxes.

Describe the solution you'd like
Allow more than one type to be inputted in property syntaxes.

Describe alternatives you've considered
I've thought that an expression like the following one:

%*classinfo% property <.+>

Which would be used in the patterns sections like this:

expression:
  patterns:
    player property stuff
    world property stuff

condition:
  patterns:
    livingentity property something
    block property something

That would create two patterns with the desired property format. Though, this approach has many disadvantages for this purpose and these are:

  • Creating uneeded patterns.
  • Having more logic than the needed one to handle types.
  • Disapproach of Skript's multiple type support.

So, while this expression might be good, it is just not good for this specific purpose, perhaps for other things like #75, it could be good.

Metadata

Metadata

Assignees

Labels

priority: mediumRequires some attention, but does not need to be deployed immediately (most bugs)type: enhancement

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions