PaperMC / PaperMC/Paper

Entity ID based wireless redstone sometimes triggers when no signal sent - 1gt AND gate

Open
#13,321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

I've been operating wireless redstone referenced in #6277 and it does work, but I have it connected to a stasis chamber and about once per hour it'll randomly trigger the pearl even though I haven't sent any signal. I have split off the AND gate that is used, set it up to a 20gt timer, and have the input offset with a 1gt delay so it should never trigger. The output is connected to a piston and a block, so if the block ever moves we know the piston pushed it and the AND gate triggered incorrectly (confirmed with coreprotect)

Observed/Actual behavior

AND gate gets regular 1gt pulses 1gt apart and occasionally trips

Steps/models to reproduce

Schematic needs a clock attached, it has a 4gt and 5gt delay into a 1-tick AND gate and which drives a piston (there should be a single item in the bottom dropper)

and1gt.zip

Plugin and Datapack List
Image

not an admin so I can't use /datapack list but i can request it if necessary

Paper version
Image
Other

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by loading the attached and1gt.zip schematic with the described clock, 4gt and 5gt delays, 1-tick AND gate, and piston on the reported Paper version. Reproduce the occasional trigger and compare it with the expected behavior; the issue does not name a source file or test to run, so tracing the relevant redstone tick behavior will be necessary.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.