Loot pet breaks with spawners

[lethalitycomplex]

I've found in 1.20 that if you try to mine a spawner with a Loot pet on your hotbar (i.e equipped), it won't allow the spawner to break as you mine the spawner, the pet tries to apply its effects, and game spits out an exception, not allowing the spawner to break, even in Creative mode.

I can provide an exception log if needed, but is there any way to add spawners as an exception to the doubling effect of the loot pet?

[capnkirok]

Monster Spawners don't drop by default if you mine them, even with Silk Touch. That is Minecraft behavior.

[capnkirok]

If you are talking about the Inventory Pets spawn blocks, those are not mineable (on purpose). But break in creative just fine, so must be something else. I'm not seeing this error, so sounds like a conflict. Shoot me the exception log if you have it, but the behavior sounds correct.

[lethalitycomplex]

That one is a my bad on explaining the issue due to lack of information on my part

The spawners underneath are apparently the spawners from Apotheosis, which are breakable and can be picked up with Silk Touch (which probably makes this a compat issue).

I don't have the exception log on me (this happened a while ago on a server that isn't running anymore), but reproducing it is basically as simple as having a loot pet on the hotbar, and trying to mine any Apotheosis spawner. It doesn't have any issues with other fortune modifiers (such as enchants and the like), as I did try that at the time, as well as in other configurations where Inventory Pets wasn't present at all.

[capnkirok]

Ahhh, ok. I'll take a look at Apotheosis and see what's going on.

[capnkirok]

I'm not able to replicate. The spawner appears to break and go into inventory. It doesn't duplicate, but I'm ok with that.

Do you happen to have Vein Miner installed? There is a known compatibility issue there in conjunction with the Loot Pet.

[lethalitycomplex]

The pack in question had FtB Ultimine installed for vein mining, not sure if it'd be a known issue due to shared code or something else