PaperMC / PaperMC/Paper

Entity is null in BlockReceiveGameEvent for chest interactions

Open
#14,234 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected behavior

When opening and closing chests, I'd expect BlockReceiveGame event to have the player as an entity causing this event.

Observed/Actual behavior

Entity is null.

Steps/models to reproduce
  • Register BlockReceiveGameEvent listener and make it log event.getEntity() every time.
  • Open chest, double chest, trapped chest, ender chest or a barrel
  • Entity is null
Plugin and Datapack List
> plugins
[09:00:12 INFO]: ℹ Server Plugins (1):
[09:00:12 INFO]: Bukkit Plugins:
[09:00:12 INFO]:  - SculkSensors
> datapack list
[09:00:15 INFO]: There are 3 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]
[09:00:15 INFO]: There are no more data packs available
Paper version
> version
[08:58:51 INFO]: Checking version, please wait...
[08:58:51 INFO]: This server is running Paper version 26.2-121-main@a2a42c5 (2026-08-29T11:32:25Z) (Implementing API version 26.2.build.121-stable)
You are running the latest version
Previous version: 26.1.2-18-6bac3c9 (MC: 26.1.2)
Other

Ever since paper-26.1.2-18 Delay open/close callbacks for chests version, the event lost the player for chest interactions. Still works for shulker boxes btw

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 tracing the BlockReceiveGameEvent handling for chest interactions and compare it with the behavior introduced around Paper 26.1.2-18, when delayed chest callbacks were added. Reproduce with a listener logging event.getEntity() for each listed container; done means chest interactions report the player entity while the existing shulker-box behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.