Observer implementation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 106
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 3
Description
It seemed like a relatively simple redstone component and I wanted to implement one :D.
Observers are however a bit different to other redstone components as they react to any state change of the block behind them instead of responding to absolute redstone signals.
The observer should also only respond to the block it is looking at for this a few changes need to be made that allows the block to see where the updates come from.
A few notable things that update observers are:
- all sides of redstone including the top
- all sides of repeaters, comparators and other observers
- locking repeaters
- torches
- redstone lamps, trapdoors
- buttons, levers and pressure plates
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how existing redstone components receive block updates and how update sources are identified; the issue names no files or tests. Compare the observer’s required behavior with the listed update sources, then verify that it reacts only to changes from the block it faces and emits the expected observer update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100