Version 1.1.1 - Server Crash about ezpas

[JoshMayberry]

:) It is ok. You're doing amazing with this mod. We appreciate it and the work you put into it a lot.

[cakewhip]

Please attach a crash log.

[JoshMayberry]

I'm so sorry, I had forgotten to attach that.
Here it is.
crash-2020-08-11_18.33.37-server.txt

[JoshMayberry]

Here are some screen shots of the setup.
I think the issue is not that it is a server, but the existing setup I had with the previous version.

I punched out the things surrounding it and put up some white concrete for better pictures.

Items flow from the input chests to the smelter array:

Then to storage 1 and storage 2. Storage 1 has lots of filter pipes connected in a large matrix, which might be an issue (I did this so I could have more filter slots to put things in the chest, because 1 line of items wasn't enough):

One place that might be an issue is here, where the output from the smelters is sent back to the main bus: (perhaps this is causing a recursive loop)

This entire structure is a part of a nomadic structure, using the nomad books mod. The structure is taken mining and stuff, then re-deployed at the base camp where items are sucked out of the export 1 and export 2 bus and sent to the main base's sorting system. So, maybe the exposed extractors or filters could also cause a problem?

[JoshMayberry]

I just tried removing the spot where the output from the smelter array goes back into the main bus, and it still crashed with the same recursive loop.
crash-2020-08-11_19.52.14-server.txt

[cakewhip]

It is most likely an issue with the large number of filtered pipes. EZPaS treats items like water, as in the filtered pipe will apply its filter to all pipes coming afterward, like an actual pipe in real life. Because of that, EZPaS sees your rectangle of filtered pipes as a bunch of filters combining with each other, from the entry pipe to the last filtered pipe. This is a confusing aspect of EZPaS, and I will am planning on making a change to revert it back to its original form soon.

[cakewhip]

This may have been fixed as of v1.1.2. Test your world with that version (available for both 1.16.1 and 1.16.2) and comment back here so I can update the issue.

[JoshMayberry]

If I use version 1.1.2, I get the following error in the command window when the server starts up (no crash log was generated):

[main/FATAL]: Failed to start the minecraft server
java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'ezpas'!
        at net.fabricmc.loader.entrypoint.minecraft.hooks.EntrypointUtils.invoke0(EntrypointUtils.java:53) ~[fabric-server-launch.jar:?]
        at net.fabricmc.loader.entrypoint.minecraft.hooks.EntrypointUtils.invoke(EntrypointUtils.java:36) ~[fabric-server-launch.jar:?]
        at net.fabricmc.loader.entrypoint.minecraft.hooks.EntrypointServer.start(EntrypointServer.java:32) ~[fabric-server-launch.jar:?]
        at net.minecraft.server.Main.main(Main.java:125) [intermediary-server.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_201]
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_201]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_201]
        at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_201]
        at net.fabricmc.loader.game.MinecraftGameProvider.launch(MinecraftGameProvider.java:192) [fabric-server-launch.jar:?]
        at net.fabricmc.loader.launch.knot.Knot.init(Knot.java:140) [fabric-server-launch.jar:?]
        at net.fabricmc.loader.launch.knot.KnotServer.main(KnotServer.java:26) [fabric-server-launch.jar:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_201]
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_201]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_201]
        at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_201]
        at net.fabricmc.loader.launch.server.FabricServerLauncher.launch(FabricServerLauncher.java:61) [fabric-server-launch.jar:?]
        at net.fabricmc.loader.launch.server.FabricServerLauncher.setup(FabricServerLauncher.java:105) [fabric-server-launch.jar:?]
        at net.fabricmc.loader.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:49) [fabric-server-launch.jar:?]
Caused by: java.lang.NoSuchMethodError: com.kqp.ezpas.network.SetPersistStateC2S.register()V
        at com.kqp.ezpas.init.Ezpas.onInitialize(Ezpas.java:81) ~[ezpas-1.1.2-1.16.1.jar:?]
        at net.fabricmc.loader.entrypoint.minecraft.hooks.EntrypointUtils.invoke0(EntrypointUtils.java:50) ~[fabric-server-launch.jar:?]
        ... 17 more

It loads fine on the client though.

[cakewhip]

Well that's a little embarrassing. I just finished up another release, also fixing the error in that crash report.

[JoshMayberry]

Just tried loading version 1.2.0, and no server crash now. 🥇