Nomifactory

Nomifactory

Modpacks
143k Downloads

Problem when joining server

ImAWerewolfDuck opened this issue ยท 4 comments

commented

I wanted to play Omnifactory 1.2.2 with a friend on a custom server, but we always get 2 errors:

  1. Fatally missing registry entries (every first time trying to join a server after launching omnifactory)
    2."produces unregistered item" (view screenshot below)
    The game also warns me that the level.dat is being used (view other screenshot)
    Things I tried (always did a fresh install on Server and Client):
    -exchange client config with server config
    -exchange server config with client config
    -same as above with the mods
    -deleting the client side config (-> worked on first join. when placing anything the server would kick me out and when rejoining the same problems would occure again)
    issue1
    issue2
commented

Let's talk about this in the Discord support chat since I saw you joined the server. It will be easier to talk in real time than on a GitHub ticket for this sort of thing.

commented

Perhaps just posting "lets talk about this in discord" on the page that represents the only searchable landing point for a problem that multiple people might have isn't the most helpful way to utilize github issues.

commented

This problem tends to happen when an installation is corrupted or additional mods have been added to the pack which give mismatched configs as compared to the server.

I do not suspect the issue is related to the pack itself, but rather an ancillary tech-support issue. That said, if I discover anything useful, I will be sure to mention as such. I am still working with them on troubleshooting the issue.

commented

As it happens, I just heard back from them.

Previously they were using Twitch launcher, which ships with the very out of date Oracle Java JRE8u51 (released July 14, 2015) that the vanilla Minecraft launcher uses.

Installing the latest OpenJDK JRE with Hotspot and installing the pack in MultiMC instead resolved their problems. Many people were having strange errors with Twitch during that timeframe (look at e.g. the slew of Feed The Beast subreddit posts), and I suspect the underlying problem was a bad installation that broke the pack.