Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

EntityDropItemEvent is not fired for item frame drops

Abierto
#14,424 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java

Línea de trabajo

Start by tracing HangingEntity#spawnAtLocation and compare it with the Entity#spawnAtLocation event-firing path described in the issue. Reproduce the four item-frame cases using the attached plugin source and output. Done means establishing whether hanging-entity drops should fire EntityDropItemEvent and, if so, verifying it fires for the frame and its contents.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

status: needs triage version: 26.3
Expected behavior

Should EntityDropItemEvent fire for the frame item and its contents, with the frame as the source? Or are hanging entities intentionally excluded?

Observed/Actual behavior

Destroying an item frame with an explosion fires HangingBreakEvent and ItemSpawnEvent, but no EntityDropItemEvent.

Reproduced for normal and glow item frames, both empty and containing a diamond. Empty frames produce one item drop; filled frames produce two. EntityDropItemEvent fires zero times in all four cases.

Steps/models to reproduce
  1. Extract the attached reproduction archive.
  2. Put frame-drop-probe.jar in plugins/ on a fresh Paper test server with a new world.
  3. Start the server and read the console or plugins/FrameDropProbe/result.txt.

The plugin creates and destroys all four frame variants automatically with World#createExplosion(location, 3.0f, false, false). It uses only the Bukkit API, with no NMS or manually dispatched events. The archive includes the source and test output.

frame-drop-reproduction.zip

Plugin and Datapack List

Only FrameDropProbe 1.0. Datapacks: vanilla (built-in), paper (built-in).

Paper version
This server is running Paper version 26.3-222-main@e3ba7b1 (2026-10-24T13:18:21Z) (Implementing API version 26.3.build.222-stable)
You are running the latest version

Java: Eclipse Adoptium Temurin 25.0.4.1+1-LTS, macOS aarch64.

Other

HangingEntity#spawnAtLocation calls addFreshEntity directly, bypassing the Entity#spawnAtLocation overload that fires EntityDropItemEvent.

Is this intentional, or should hanging-entity drops use the event-firing path?

Lenguaje dominante
Java
Estrellas
12.8k
Forks
3.6k
Merge medio
4 d 22 h
PR fusionados (30 d)
46

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PaperMC/Paper

Todos los issues de PaperMC/Paper

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.