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

BlockDispenseEvent is called twice since 26.3 for most blocks

Cerrado
  • ¿Algo no está bien?
#14,415 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
Área
api, backend

Línea de trabajo

Start in DispenserBlock around line 121 and trace SulfurCubeBlockDispenseItemBehavior.execute into dispenseBlock and CraftEventFactory.handleBlockDispenseEvent. Check how the fallback through DefaultDispenseItemBehavior triggers the event, then reproduce with an event listener that logs each dispense. Done means one BlockDispenseEvent per dispense, with the sulfur cube behavior and fallback still working.

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

Descripción

status: accepted version: 26.3
Expected behavior

BlockDispenseEvent is only called once when a dispenser throws out a block

Observed/Actual behavior

When a block is dispensed from a dispenser, it used to go through the usual DefaultDispenseItemBehavior.
With the Sulfur Cubes that changed for most blocks (DispenserBlock line 121):

} else if (itemStack.is(ItemTags.SULFUR_CUBE_SWALLOWABLE)) {
    return SulfurCubeBlockDispenseItemBehavior.INSTANCE;
}

SulfurCubeBlockDispenseItemBehavior#execute (vanilla) falls back to super.execute if no Sulfur Cube took the item:

@Override
protected ItemStack execute(final BlockSource source, final ItemStack dispensed) {
    return dispenseBlock(source.level(), source.pos().relative(source.state().getValue(DispenserBlock.FACING)), dispensed, source, this) // Paper - Call BlockDispenseEvent
        ? dispensed
        : super.execute(source, dispensed);
}

Paper calls handleBlockDispenseEvent at the start of dispenseBlock, before it checks whether a Sulfur Cube is in front:

ItemStack result = org.bukkit.craftbukkit.event.CraftEventFactory.handleBlockDispenseEvent(source, pos, dispensed, currentBehavior);

If there is none, dispenseBlock returns false and vanilla falls back to super.execute, which fires the event again in DefaultDispenseItemBehavior.spawnItem.

The same applies to TNT: the TNT behavior also calls SulfurCubeBlockDispenseItemBehavior.dispenseBlock first and then fires its own BlockDispenseEvent. The TNT is only primed once, but the event is called twice for a single dispense.

sequenceDiagram
    autonumber
    participant D as DispenserBlock
    participant S as SulfurCubeBlockDispenseItemBehavior
    participant DD as DefaultDispenseItemBehavior (super)
    participant F as CraftEventFactory
    participant L as Plugin Listener

    D->>D: getDefaultDispenseMethod(itemStack)
    Note over D: itemStack.is(SULFUR_CUBE_SWALLOWABLE)<br/>→ SulfurCubeBlockDispenseItemBehavior.INSTANCE
    D->>S: dispense(source, stack)
    S->>S: execute(source, stack)
    S->>S: dispenseBlock(level, pos, stack, source, this)
    S->>F: handleBlockDispenseEvent(source, pos, stack, this)
    F->>L: BlockDispenseEvent (1st call)
    L-->>F: not cancelled
    F-->>S: null
    S->>S: getEntitiesOfClass(SulfurCube, AABB(pos))
    Note over S: no Sulfur Cube in front<br/>→ dispenseBlock returns false
    S->>DD: super.execute(source, stack)
    DD->>DD: spawnItem(level, stack, 6, direction, position, source)
    DD->>L: BlockDispenseEvent (2nd call)
    L-->>DD: not cancelled
    DD->>DD: level.addFreshEntity(itemEntity)
Steps/models to reproduce

Watch the BlockDispenseEvent with a event listener and see two logs for the same dispense.

Plugin and Datapack List
Paper version

This server is running Paper version 26.3-209-main@03af8b4 (2026-10-20T21:49:44Z) (Implementing API version 26.3.build.209-stable)

Other

No response

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.