so, I'm in a SSP survival world and actually having the spawner setup and running for a long time period.

I've noticed quite a few times that no output was happening. One time, picking/replacing one of the upgrade blocks got it going again, other time, only doing same for grinder block itself would get it to go again.

Using TOP it's easy to see that there is no rf in the block itself. picking/replacing the EIO transceiver doesn't work either. The transceiver is on it's own channel, only servicing the woot setup and it's a full 8x8x8 EIO vibrant cap bank, so lots and lots of power.

If I can catch it when it's stopped, maybe I can help you determine what's causing it but at this point, it's random as hell when it does happen.

WOOT is setup in it's own chunk, no chunk borders.
woot-1.10.2-1.2.3

I want to say this is an EIO issue. going to close this. I set the transciever to push into the woot block and It went from 0 rf to filling it. again, w/o this, it'd work, but then suddenly stop working. sorry for the trouble.

ok, I'm reopening. unless there's a specific issue with EIO here that's only affecting ur mod block, I have no clue. I went searching for 1-2 hrs from base (which is chunkloaded) and when I got back, main block has 0 rf in it and is non responsive. I've now hooked up some eio conduit to power the block and transceiver to the conduit. It's the only rf required device in my base that is having this kind of issue atm.

It is possible that this is down to the new Forge power API that I don't use yet.
I normally user EnderIO in my test world, but only for short periods of time, so I wouldn't have seen any issue. I'll investigate and try it with different power gens to see if I can narrow down the issue.

FInally getting round to looking at this.
Can you let me know which version of EnderIO you are using, so I can use the same.
I'm guessing that the EnderIO device is in the same chunk as the factory - I'm guessing yes.

sorry to take so long to get back to you.

I was using EnderIO-1.10.2-3.0.1.141_beta

Thanks, I'll see if i can replicate it with the version as I was having issues doing that.

Good news and bad news.
The bad news is I cannot replicate it.
The good news is someone on a Discord channel that I use has the same issue with the dimensional transceiver needing broken/replaced to make it work again. I've also noticed comments on the same server regarding EnderIO conduits having problems as well.

So I'm not saying it is EnderIO, but there does seem to be an issue under discussion regarding EnderIO and chunkloading that MIGHT be related to this.

I've now updated to the new Forge power API - in the next mod release - however I don't believe this will make any difference.

So I'll very much be trying to understand and fix this issue, but it sounds like it wont be trivial.

sry for late reply (again) ...

tbh, the way I saw it, it really didn't matter too much that it happened. so what if I had to go back and verify it was working or not. it was already providing so much stf in the first place, lol I only mentioned it cause obviously something was going on. I can try supplying power using calculator plugs or something and see if EIO has nothing to do with it but I don't play that pack much if at all now.

I did have everything chunkloaded using chickenchunks. I also am very chunk aware (to a fault) and keep things in their own chunks at all times, especially multiblocks.

We're still having the same issue, with EIO and IE cables this time. Multiple people on the server have the problem. The only difference is breaking, replacing, rewiring... Nothing fixes it.