DerToaster98

Yes, i *could* do that, but i will only have access to exactly the item using that approach. And for what i want to do i need access to the...

Iirc there is just an entity spawn event, no? Haven't seen one specific for dispensers. And iirc the entity spawn event lacks a "reason" or context what spawned the entity...

ok, that gets me the reason, but for what i want to do i need to have access to the dispenser too. And having to scan every of the 8/14...

> i didn't look at the implementation of this so i am not sure if this is possible but perhaps you could expand on the BlockDispenseEvent by adding a getEntity...

> I think this duplicates a lot of what is proposed in #7377. Looks like it. Will still keep this open though, cause the PR you mentioned hasn't been touched...

> > EDIT 2: Haven't looked in detail but for what i want i need access to the dispenser BE that fired the projectile or spawned the tnt, not having...

> > EDIT 2: Haven't looked in detail but for what i want i need access to the dispenser BE that fired the projectile or spawned the tnt, not having...

It is cleaner to remove 1.18 support. For a comparable system, i have the SignWrapper class in my sign PR, it essentially abstracts away the relevant calls to an event...

So, just to get this straight: I *do* have permission to remove 1.18.x stuff from the repo via a PR that fixes this issue?

Alright, do you mind if i use my "adapter" that i already have within the PR then?