Flux networks Power supply broken by update [1.12.2]
CanisArtorus opened this issue ยท 8 comments
At current: the basic power cell needs to drain power from an adjacent storage block (using EIO vibrant capacitor bank) = Woot 1.4.6 in Stoneblock 1.0.22r1
Before update: the basic power cell was being charged directly a Flux Point. = Woot 1.4.5 in Stoneblock 1.0.21
I have successfully reproduced this change in a minimal environment (Flux Networks 3.0.16, EIO 5.0.36, and specified Woot versions. Forge 14.23.5.5772 in MC 1.12.2).
We were somewhat surprised by the woot altars no longer functioning, and even tried chunk aligning the structure.
Hello
Version 1.4.8 still has this issue
Any news about a fix? or a temporary workaround?
I raised a bug on the Flux Networks Github page, but so far I've had no response.
(SonarSonic/Flux-Networks#269)
I don't believe the problem is in Woot and have provided the Flux Networks author with information on what my mod is doing. Hopefully they come back either with their mod not processing one of the standard block update mechanisms or something that Woot is not providing to them, but they are relying on them.
The block update explanation is consistent.
That was the first server reboot after building our altar. No similar trouble was experienced in prior packs we played. Test world with woot 1.4.5 does not exhibit save/load difficulties.
Test world break/replace the flux point did connect to the power cell.
Also, the flux point remained visually connected to the power cell when the altar was broken. And would continue to power it once repaired.
I've retested with the following setup:
EnderIO - 5.0.36
Flux Networks - 3.0.16-11
Woot - 1.4.5
Forge - 14.23.5.2772
This shows the exact same issue as with Woot 1.4.6 for me.
Do you know the mod versions that you were using where Woot 1.4.5 was working?
(If Flux Networks is not reacting to neighbor change events then breaking the altar will not change the connection to the cell. Breaking the cell would however do that. I've opened an issue with the Flux Networks author to see if they can give me any information on how they handle neighbor changes).
I'll have to load this into my dev environment to see what is going on. I didn't think I had played around with anything that would impact this between 1.4.5 and 1.4.6, but you never know!
Stoneblock 1.0.20 = Flux Networks 3.0.16-11 Woot 1.4.5 Ender IO 5.0.36 Forge 14.23.5.2768 Stoneblock 1.0.21 = Flux Network 3.0.16-11 Woot 1.4.5 EnderIO 5.0.36 Stoneblock 1.0.25 = Flux Networks 3.0.16-11 Woot 1.4.6 EnderIO 5.0.36 Forge 14.23.5.2768Finally managed to get everything updated and setup.
Enderio capacitor -> flux plug
Basic flux storage
Flux point -> premium power cell
That causes a drain of 5.5KFE/T on the flux point while I generate Withers.
After save and reload of the world the flux point no longer powers the premium cell and is no longer visually connected.
So I think I know why .....
When the blocks are created after load, the Woot factory is not formed so nothing can connect. However the factory then detects all the valid blocks, forms and can accept power connection. However the flux point is not being updated to say - hello there is a new block here to connect to.
If I retest with Enderio conduit instead of Flux Points then it connects and all is well, although EnderIO may well check for valid block connection in a different way.
Can you check that if you break and replace the Flux Point at the power cell that it works again?
Do you know if you have previously had this working and a server stop/start has not broken it?
I don't know if that has always been the case or if the save/load issue is a new thing.
Many apologies. I no longer remember where that assertion came from. And re-testing has yet to find a version that doesn't have the same issue.
So this really was an inherent behaviour limitation intersection all along.