Currently playing on Direwolf20 pack, MC Version 1.12.2, pack version 1.6.0. I have set up a mob masher in a compact machine for collecting wither skeleton skulls. I find that when I leave my compact machine, the mob spawns continue (to the mob duplicators upper limit), yet the masher doesn't seem to be killing them. I'm 98% sure that this mod is the issue, but since other mod authors don't seem to think being able to transmit redstone out a dimension while keeping signal strength or giving a nice block which can give an actual count and not a redstone strength of entity number, I'm unable to properly test this. Is there a work-around or a fix for this problem?

Is it just unmentioned that the mob masher checks for a nearby player while operating? I should probably mention, the compact machine is in a loaded chunk and has a spot loader inside of it, so it's not a chunk loading issue. I can tell the spawns continue because after I leave the dimension one of my displays shows my mob essence count depleting (until I max out on mobs).

Hello,
I'll take a look in to this as it doesn't work off any player location nearby. The Masher is a Fake player and as such should be able to exist in other dimensions - I'll take a look at the code and see if I have any code that specifies the dimension it's in (it's over a year since I wrote all the code so I don't honestly remember off hand). I would imagine with a chunk loader etc it should in theory work - but it is modded MC ;)
Cheers,
Me.

This may be an issue with the specific pack and as such not a mod bug. I have seen people use the mob mashers in the Twilight Forest and other dimensions fine but not remotely so I'm unsure as to if this is a one off instance of the mod just not being what you need or a genuine issue for others. The fake player that the Mob Masher uses is set to a specific co-ordinate away from the player due to issues with item equipping noises and the original sound event cancelling it not working for me - more of a bandaid than a cure. Perhaps that could be the issue here and it's location is unloaded. The location is set to the X and Z position of the block and at -100 Y world height (so out of the world essentially) - Will investigate further and see about a proper solution.

I've not found an ideal solution to this - may re-open at a later date.