PaperMC / PaperMC/Paper

Bug in the block update order or intentional behavior?

Open
#8,441 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: accepted type: bug version: 1.20.4
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

I wanted to build a system that detects if a sulker box has been opened and then sends out a redstone signal.
When the shulker box is opened, the item inside the dispenser to the right of the shulker box moves into the hopper and thus delivers the desired signal.
On vanilla Minecraft (1.19.2) it works perfectly fine:

Vanilla_Behavior

Observed/Actual behavior

On my paper server, no Redstone signal occurs when using the same design:

Paper_Behavior

I have tested the system on the paper server with the settings
redstone-implementation: EIGENCRAFT and
redstone-implementation: VANILLA
Both without success.
My question is, is this a bug, an intentional behavior or did i miss a setting somewhere?

Steps/models to reproduce

Here is a schmatic to recreate this behavior:
Shulker_update_detec.zip

The hopper below the dropper is filled with items so it can't pull any more items from the dispenser above.
grafik

The dropper above the hopper contains a random item that cannot be picked up by the hopper below
grafik

The hopper dispenser combination also contains a random item to swap back and forth.
grafik

The content of the shulker box does not matter

The result of opening the shulker box can also be simulated by removing and placing the redstone dust on top of the redstone block (this works also only in vanilla):
Vanilla_Behavior_2

Plugin and Datapack List

/plugins: none
/datapack list: vanilla & file/bukkit

Paper version

/version output:
This server is running Paper version git-Paper-199 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: 77a50b9)
You are running the latest version
Previous version: git-Paper-198 (MC: 1.19.2)

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 with the supplied Shulker_update_detec.zip schematic and reproduce the redstone behavior on Paper 1.19.2 with both EIGENCRAFT and VANILLA redstone implementations. No source files, tests, or entry points are named; done means determining whether the update-order difference is intentional or a bug and verifying the behavior after the relevant change.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.