Skip to content

Clear entities within conflict #7652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
TheLimeGlass opened this issue Feb 26, 2025 · 2 comments
Closed
1 task done

Clear entities within conflict #7652

TheLimeGlass opened this issue Feb 26, 2025 · 2 comments
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).

Comments

@TheLimeGlass
Copy link
Contributor

Skript/Server Version

[00:46:14 INFO]: [Skript] Server Version: 1.21.4-144-edacfdf (MC: 1.21.4)
[00:46:14 INFO]: [Skript] Skript Version: 2.10.1 (selfbuilt-unknown)
[00:46:14 INFO]: [Skript] Installed Skript Addons:
[00:46:14 INFO]: [Skript]  - Sky v1.1.0
[00:46:14 INFO]: [Skript]  - skript-reflect v2.6 (https://github.com/SkriptLang/skript-reflect)
[00:46:14 INFO]: [Skript]  - SkQuery v4.3.1
[00:46:14 INFO]: [Skript]  - Fawesk v2.2
[00:46:14 INFO]: [Skript] Installed dependencies:
[00:46:14 INFO]: [Skript]  - WorldGuard v7.0.13-beta-2+5c4848b

Bug Description

When running clear entities within {_pos1} to {_pos2} the syntax will actually be parsed as ExprValueWithin and collect the entities within the location variables instead of ExprEntities within two locations.

The result will return nothing because the two local variables are locations.

Expected Behavior

To return the entities within the two locations.

Steps to Reproduce

command /test:
	trigger:
		set {_pos1} and {_pos2} to player's location
		clear entities within {_pos1} and {_pos2}

Parses successfully

Errors or Screenshots

No response

Other

#5457 should solve the issue

Agreement

  • I have read the guidelines above and affirm I am following them with this report.
@erenkarakal
Copy link
Member

can reproduce, using all entities works as a workaround

@erenkarakal erenkarakal added bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements). labels Mar 4, 2025
@Fusezion
Copy link
Contributor

is this not a duplicate of #7280 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue that needs to be fixed. Alternatively, a PR fixing an issue. priority: lowest "Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
Projects
None yet
Development

No branches or pull requests

4 participants