Describe the bug
We are currently running a quite big me network. Now we ran into the problem that our ME Drives keep going offline without a reason to do so.
Our stored Power: 240-250MRF
Max Power: 250MRF

Energy Usage: 110kRF
Energy Generation: 110kRF
The stored power never runs below 240MRF.

We're powering it as follows:
Mekanism Induction battery output is directly attached to the energy acceptor which is directly attached to our dense energy cells, which are attached with a dense smart cable. We don't see what we're doing wrong.

To Reproduce
Attach a mekanism induction battery to a energy acceptor to a dense energy cell. With this setup we can use the me system for a while before the me drives go offline again.

Expected behavior
The ME Drives should stay online if there is stored power in the network.

Additional context

Environment
We're playing the modpack MC.Eternal on version 1.3.5 with draconic evolution and galacticraft added. It's quite a big pack and we're playing on a server with the latest forge version for 1.12.2 (14.23.5.2847).

• Minecraft Version: 1.12.2
• AE2 Version: appliedenergistics2-rv6-stable-7
• Forge Version: forge-1.12.2-14.23.5.2847-universal.jar

June 2020 Sky Force 4 ME System goes still randomly offline...

Can you observe the me capacity bottoming out with the network tool? Or is it happening purely random? I am curious if the me system may reset due to an network update rather an actual powerloss. But i remember an single power transfer issue i read somewhere (implying i can not find it yet) which could maybe explain it but one would have to test if the system is actually running low or not

I inspected the system with the network tool and our stored power never ran below 240MRF while the drives just went offline from time to time. The ME itself needs ~110kRF to run constant. So the power never actually runs out, the drives just keep going offline in random intervals.

Can you assure the network is (chunk-)loaded the whole time and no parts are attached to toggle busses? Do you have quantum bridges installed and assured the dimensions stay loaded?

I'm having this problem with creative energy cells, so it seems unlikely it's power related. The chunkloading is done through FTB Utilities. All chunks with any active block is loaded, but chunks containing only cables are not.

This is running on a server with a large AE2 network.

I'm using appliedenergistics2-rv6-stable-6, 1.12.2, forge 14.23.5.2838

So we're also using the ftb chunk loading and some parts are also chunk loaded with Flux network chunk loading feature. We went ahead and chunk loaded all chunks that have cables in em.

@Lilylicious cables are parts of the network, so there is very likely your issue

@tkerkering and how about QNBs?

It seems strange that the entire network would go offline because part of it 300 blocks away unloads, though I don't know how it's coded so it may make complete sense.

Generic does not work is out of the scope for a bug tracker. Usually it even is an user error, but there are simply too many possible ones and this medium is not really suited for these things.

We really need some way to reproduce these things, otherwise it is pretty impossible to even consider it as a bug.

That was a bit too early to close @tkerkering was very cooperative, i will not reopen it but continue if @tkerkering want to

I just encountered this myself, thats odd and my system is very small! @yueh i can repeat the issue with the antimatter chemistry modpack and the issue almost always happens after the first login or when the dimension was just loaded. The first time i open the terminal and i transfer any item, it reboots

https://imgur.com/a/3CEVkWh So we build an quantum bridge and that looked to solve the problem. But after we went away for some distance the me drives went offline again.
I can tell that the me runs better after building the quantum bridge, but when I look into it with a wireless terminal for some time the drives go offline again for quite some time.

If there is anything I could do that could be of help I'd be glad to do. If you guys want I could also record a video where I show how we build the controllers and everything.

Also if the numbers don't match my original description anymore it's related to us trying to figure out what's wrong.

So as we continued on playing, the me drives went offline again. We mostly encounter this problem when we're not near the system itself. But sometimes you can stand in front of the controllers and look at the drives before they go offline.

So @mindforger pretty happy that one of you guys could more or less encounter the same "bug"? that we did. I'm thinking about setting up a clean 1.12.2 modded mc version with just mekanism and applied energistics added to see if I'm able to reproduce it again.
I'm a developer myself so I know how important it is for us users to give you guys a good way to reproduce the bug.

After building the quantum bridge the me drives keep going offline but most of the time some of them stay online. This way we can still dump stuff into the system, but are not able to craft everything cause some of the stuff we need is on other drives that are currently not online.

We also encountered that this is more likely to occur if there are several players connected to our server. If it's only 1 person playing the bug doesn't occur as much, like the me grows instable the more players join the server.

We tried removing all loops in the network, which was only 1 that we found. We build the quantum bridges. We have the area chunkloaded in several ways. We have the dimension stay loaded with galacti craft. We removed the energy drain so our me only used 2kRF cause somebody on our modpack server told us it might have something to do with the me draining 200kRF. We probably spend 10-15hrs now trying to figure out what might be wrong and trying to fix the problem.

So it's probably better to just try to reproduce it on a clean install.

Unfortunately i can most probably not test this until monday properly again in my instance. I can not remember if i have mekanims, but i have also thermal expansion and thermal dynamics installed

These are probably 3 different reasons/issues.

The first one being the usual an unloaded network is basically a non existing network for minecraft and just join here because "does not work" seems to be equal enough to be considered identical.

Then we have a completely different modpack. Could be something completely different like some AE2 addon doing funky stuff. Which is not that uncommon. E.g. triggering network rebuilds once their stuff comes online. I think there were one or two doing something like that, but I do not want to blame some potentially unrelated addon.

And the original post is nearly void of any information besides does not work and some useless stuff like removing loops, which is pretty much BS level in terms of any effect.
The only slightly useful information is that it happens more commonly with more people. Which sounds a bit like the server is dynamically scaling the loaded chunks across all players or similar and starts to unload them once it hits a threshold. Trying to gather further details then more or less leads to the same appearance. Crash reports without any crash log and nothing more than crashes with some error.

@yueh I think you don't understand. I can stand in front of my me network and the drives go offline. It's not the whole network it's just the drives. Network can't get u loaded if I stand right in front of it and in the same chunk.
If I attach more dense energy cells the drives go offline even faster. You're quite grumpy that I don't post any crash logs/stacktrace but if it's not posting any how could I?
So I guess we're going to test it on a clean install and give you a step by step tutorial how to get this big going. If that is still "generic not working" I don't know what you need more. I think it's also quite problematic that we have more or less to defend ourselves instead of having a developer looking into the thing after several people tell you about it, which in my company is Atleast a no go.
If a bug occurs in another modpack as well that's even more reason to look into the bug cause that means that it's not purely our pack at fault.

Sure, if you can provide a way to reproduce it, it would be highly appreciated.

Your description just is somewhat common. Yet until now it always came down to an user error. Like not chunkloading the network. Even this issue already has the usual case of not chunk loading it, therefore not working in some cases. Which is simply how minecraft works and out of the scope for this project to solve. That is something mojang would have to fix.

Also keep in mind, this is not a business. Just some hobby project and I cannot justify spending days trying to reproduce something with nearly no information. On the other hand this project is open source. So nobody prevents you from submitting a fix as pull request. In case you feel I am not prioritizing it as urgently as you expect. (Based on my previous experience with similar reports)

So apparently we rebuild our whole me network. This time we used p2p to connect all our drives (that we completely moved in another place). After doing this it's magically working without the drives magically going offline. So I think there might be a limitation or some kind of overflow if you connect too many drives with normal connections to your me controller.
We also read the wiki entries to me drives and me controller, so we know that you're only able to connect 8 drives on each side of the controller with a cable. We did that and checked it 10 times before rebuilding the whole thing to use p2p (we rebuild everything and enlarged the controller).
So @mindforger try replacing your connection to the drives with p2p tunnel connections. That fixed the problem for us. How exactly that fixed the problem is still a mystery but aslong as it works. ¯_(ツ)_/¯

So after playing on the server again for a while we saw the me drives going offline once more. Because we now have 3 me's bundled into one we don't see it happening directly. But for our main me the drives keep going offline in random intervals. We did everything that is possible and it can't be an user error because we perfectly made sure to follow what the wiki tells.

But rebuilding the me to use p2p tunnels increased the stability.