Skip to content

BlockLineIterator causes an IllegalStateException when looping blocks in a line #7496

@nanodn

Description

@nanodn

Skript/Server Version

[12:46:35 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[12:46:35 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[12:46:35 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[12:46:35 INFO]: [Skript] Server Version: 1.21.4-118-73f7736 (MC: 1.21.4)
[12:46:35 INFO]: [Skript] Skript Version: 2.10.0 (skriptlang-github)
[12:46:35 INFO]: [Skript] Installed Skript Addons:
[12:46:35 INFO]: [Skript]  - skript-reflect v2.6 (https://github.com/SkriptLang/skript-reflect)
[12:46:35 INFO]: [Skript] Installed dependencies: None

Bug Description

Similar to #6437, looping through blocks in a line causes an IllegalStateException to be thrown by the BlockLineIterator.

Expected Behavior

There should be no exceptions.

Steps to Reproduce

Run the command below as a player:

command issue:
    executable by: players
    trigger:
        set {_p1} to location(0, 100, 0, player's world)
        set {_p2} to location(10, 100, 10, player's world)
        set {_origin} to location(5, 100, 5, player's world)
        loop blocks within {_p1} and {_p2}:
            set {_loc} to location of loop-value-1
            loop blocks from {_origin} to {_loc}:
                broadcast loop-value-2

Errors or Screenshots

https://pastes.dev/MGZl6d8ZyF

Other

I'm not sure if this is the same as #6437 as it was supposed to be fixed by #7062.

Agreement

  • I have read the guidelines above and affirm I am following them with this report.

Metadata

Metadata

Assignees

Labels

bugAn issue that needs to be fixed. Alternatively, a PR fixing an issue.completedThe issue has been fully resolved and the change will be in the next Skript update.priority: mediumIssues that are detrimental to user experience (prohibitive bugs or lack of useful implementation).

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions