Nomifactory

Nomifactory

143k Downloads

[f05d2f5] Cannot start|[f05d2f5] 无法启动

shengcaixing opened this issue · 4 comments

commented

1:我正在游玩[nomifactory-dev-f05d2f5-server]版本 无论是专用服务器 还是客户端版本都无法启动
我发现了一些错误日志。尚未找到[crash] 下面链接提供了 [log] 和[sever.bat]

1:I am playing the [nomifactory-dev-f05d2f5-server] version. and neither the dedicated server nor the client version can be started.
I found some error logs. Not found [crash] The following link provides [log] and [server.bat].

1:[https://github.com/shengcaixing/temp]

2:下面问题由于未验证[f05d2f5]版本中是否还存在此问题,我需要一并知道
在20230128版本当中,使用该版本启动专用服务器时出现了错误([crash])
信息摘要:

net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Modular Machinery (modularmachinery)
···········
at hellfirepvp.modularmachinery.common.util.FuelItemHelper.initialize(FuelItemHelper.java:40)
at hellfirepvp.modularmachinery.common.CommonProxy.init(CommonProxy.java:96)
at hellfirepvp.modularmachinery.ModularMachinery.init(ModularMachinery.java:85)
···········
more+++

上述问题早于2019年有提交报告,但原作者不提供修复。是否有修复方案
它在客户端正常工作

2:The following question is not verified whether this problem still exists in [f05d2f5] version, I need to know it
in version 20230128, there was an error ([crash]) when starting a dedicated server with this version.
Summary of information:

net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Modular Machinery (modularmachinery)
···········
at hellfirepvp.modularmachinery.common.util.FuelItemHelper.initialize(FuelItemHelper.java:40)
at hellfirepvp.modularmachinery.common.CommonProxy.init(CommonProxy.java:96)
at hellfirepvp.modularmachinery.ModularMachinery.init(ModularMachinery.java:85)
···········
more+++

The above issue was reported as early as 2019, but the original author does not provide a fix. Whether there is a fix
It works fine on the client side

commented

The layout looks terrible
这排版好烂
我啥也没做(

commented

Please attach the crash log files.

The layout looks strange because GitHub uses Markdown formatting, and your post contains formatting codes.

commented

The crash you are experiencing in the linked log is caused by Serialization is Bad trying and failing to download a file - specifically this one - and since it is unable to do so, causing a crash. The reason why it is unable to download the file varies, but this can be resolved via:

  1. disabling useRemoteConfig and copying the values of the config into your local config.
  2. figuring out the cause of your inability to connect and resolving it. This appears to be caused by PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, but i do not know how to resolve this.
  3. disabling the mod. You should avoid doing this if you are going to be playing on servers, as it exists to prevent the ability for another player to send malicious packets and take over your computer.

I see no mention of Modular Machinery causing a crash or error at any point in the linked logs. Also: if you put three backticks ``` both above and below text, that text will not be formatted in such an ugly manner.