Skip to content
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

Tripwire hook not registering properly on BlockRedstoneEvents #9714

Open
Thorinwasher opened this issue Sep 12, 2023 · 0 comments · May be fixed by #9724
Open

Tripwire hook not registering properly on BlockRedstoneEvents #9714

Thorinwasher opened this issue Sep 12, 2023 · 0 comments · May be fixed by #9724
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. type: bug Something doesn't work as it was intended to.

Comments

@Thorinwasher
Copy link

Thorinwasher commented Sep 12, 2023

Expected behavior

Whenever an entity goes onto a wire connecting two tripwire hooks, there should fire two induvidual BlockRedstoneEvents for the two related tripwire hooks.

For example, when an entity goes onto a tripwire with one end having a tripwire hook facing east, and the other end a tripwire hook facing west, then there should trigger a BlockRedstoneEvent once for both of the tripwire hooks.

Observed/Actual behavior

Only east facing and north facing tripwire hooks show up in BlockRedstoneEvent. The Event also triggers at least 2 times to the maximum tested value of 3 times (depending on the length of the wire) for the same tripwire hook.

Steps/models to reproduce

Make a plugin with the following listener

@EventHandler
void onBlockRedstoneEvent(BlockRedstoneEvent event){
    plugin.getLogger().log(Level.INFO, event.getBlock().toString())
}

Then make a tripwire contraption (Place tripwire hooks, and strings connecting the two hooks, the connection has to be a straight line)

After that, go into the tripwire and see the logged messages

Plugin and Datapack List

Only a testplugin with the above mentioned listener

Paper version

This server is running Paper version git-Paper-176 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 517f8fb)
You are running the latest version

Other

No response

@Thorinwasher Thorinwasher added status: needs triage type: bug Something doesn't work as it was intended to. labels Sep 12, 2023
@papermc-projects papermc-projects bot moved this to 🕑 Needs Triage in Issues: Bugs Sep 12, 2023
@Warriorrrr Warriorrrr added status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. and removed status: needs triage labels Sep 13, 2023
@papermc-projects papermc-projects bot moved this from 🕑 Needs Triage to ✅ Accepted in Issues: Bugs Sep 13, 2023
@Lulu13022002 Lulu13022002 linked a pull request Sep 14, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. type: bug Something doesn't work as it was intended to.
Projects
Status: ✅ Accepted
Development

Successfully merging a pull request may close this issue.

2 participants