Skip to content

Detection range buggy #219

@Snowiro

Description

@Snowiro

We now moved to 1.21.1 Neoforge, and I was testing block entity trigger. Unless I'm misunderstanding how detection range works, when adjusting the detection range value above 16, it simply moves the radius location and does not increase its radius to the new positive value.

Example:

Replacing the detection range from 16 to 100 puts the detection trigger 100 blocks away from the entity block instead of increasing its radius to 100. There's also a weird skip on blocks every 16 blocks.

Also, by default the detection is only detecting one side, or two of the block entity going behind it doesn't trigger it. while being in range, it can also not work by placing the block enity one block away from where it was working.

Here's a recording incase trying to explain it doesn't make sense.

https://youtu.be/23ET9Ci_rQs

Metadata

Metadata

Assignees

No one assigned

    Labels

    1.20-1.21Pertaining specifically to (any supported version of) Minecraft 1.20 or 1.21WIPThe issue is being worked on and/or some progress being made towards a fixbugSomething isn't workingquestionFurther information is requestedthe impossible libraryThe issue is with The Impossible Library and is not fully caused by Music Triggers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions