-
Notifications
You must be signed in to change notification settings - Fork 288
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
[1.20.1] Observers always on after being pushed by a piston during its pulse #4861
Comments
I'm not sure whats going on. In second video you sent the observer oes turn off |
also do you known which module in particular does this? is it the piston move tile entities one? |
Sorry if the first video wasn’t clear. The first two videos are with all automation settings disabled as then you’d expect vanilla behaviour I thought. In the first video I place the observer in front of the piston and break the block in front of the observer so the piston is powered and pushes the observer during its pulse. I do the same thing in the third video with Quark removed from the mod list. By doing this with Quark installed with all automation disabled, the observer always stays on. The second video is to show that it doesn’t always stay on when it isn’t pushed during its pulse. Again with all automation settings disabled. |
Didn’t mean to press closed with comment |
This looks like a Zeta issue in its piston reimplementation then |
I'm quite sure this predates zeta since it seems related to #4556 |
The Zeta piston implementation is the old Quark piston implementation so it makes sense |
With Quark Automation disabled:
Java-runtime-gamma.2024.07.17.-.21.23.31.01.mp4
Java-runtime-gamma.2024.07.17.-.21.32.37.03.mp4
Without Quark:
Java-runtime-gamma.2024.07.17.-.21.27.20.02.mp4
latest.log
https://pastebin.com/sYrUYnk8
The text was updated successfully, but these errors were encountered: