"Fatally Missing Registry Entries"

#1

Hello! I’m trying to play Modded Minecraft (1.12.2) with my friends, but whenever I join, it always comes up with “Fatally Missing Registry Entries”. None of my friends have these issues.

I’ve been sent the logs when I join, and this is it.
05.01 22:12:57 [Server] User Authenticator #31/INFO [minecraft/NetHandlerLoginServer]: UUID of player Thestancis is be196f7b-757e-4934-a5e3-9efa1dd62f78
05.01 22:12:57 [Server] Netty Epoll Server IO #13/INFO [FML]: Client protocol version 2
05.01 22:12:57 [Server] Netty Epoll Server IO #13/INFO [FML]: Client attempting to join with 41 mods : minecraft@1.12.2,flansmod@5.5.2,tconstruct@1.12.2-2.13.0.171,astralsorcery@1.10.20,flansmodapocalypse@1.0,immersiveengineering@0.12-92,questionablyimmersive@@VERSION@,biomesoplenty@7.0.1.2441,baubles@1.5.2,roost@2.0.10,jei@4.15.0.291,movingworld@1.12-6.342,projecte@1.12.2-PE1.4.1,techguns_core@1.12.2-1.0,com.elytradev.movingworld.common.asm.coremod@,ic2@2.8.170-ex112,mantle@1.12-1.3.3.55,forgeendertech@1.12.2-4.4.26.0,mcp@9.42,ctm@MC1.12.2-1.0.1.30,journeymap@1.12.2-5.5.6,oreexcavation@1.4.140,compactmachines3@3.0.18,adhooks@1.12.2-3.2.2.0,railcraft@12.0.0,FML@8.0.99.99,davincisvessels@@DVESSELSVER@,omlib@3.1.3-246,geneticsreborn@1.20,betterbuilderswands@0.13.2,embers@1.13-hotfix2,chisel@MC1.12.2-1.0.1.44,computercraft@1.80pr1,chickens@6.1.0,inventorypets@2.0.3,immersivepetroleum@1.1.9,forge@14.23.5.2847,openmodularturrets@3.1.4-356,immersivetech@1.3.10,forestry@5.8.2.387,techguns@2.0.2.0
05.01 22:12:57 [Server] Netty Epoll Server IO #13/INFO [journeymap]: CLIENT
05.01 22:12:57 [Disconnect] User [minecraft/NetHandlerPlayServer]: Thestancis has disconnected, reason: Disconnected
05.01 22:12:57 [Server] Server thread/INFO [minecraft/DedicatedServer]: Thestancis left the game
05.01 22:13:39 [Server] Server thread/INFO [minecraft/DedicatedServer]: There are 2/10 players online:
05.01 22:13:39 [Server] Server thread/INFO [minecraft/DedicatedServer]: Everest, Leo_Mecha

#2

Have you made sure that all your mod config files are the same as the server? A minor conflict like that can result in what you are seeing.

#3

I’m sorry, I’m really bad at anything computer related. What are Config Files? If you could be a bit simpler that would help me out a lot! :slight_smile:

#4

Config files are what allow someone with the exact same mods as your server act in a different way. Say you dont like xyz feature from a mod. What you may do is go into the config files of your server or your client (server being what you connect to. Client being what you connect with) and disable the feature of xyz.

Config files for your server are located in the following location. being where your server is located.

<Root>/configuration

The configuration for your client are located in the following

%appdata%/roaming/.minecraft/configuration

Assuming your on windows 7 or above, you can simply put %appdata% in the search bar and hit enter to get to where %appdata% is

#5

Would downloading all my friend’s Server’s config files for the Mods and replacing them with my Config Files work?

#6

Depends on the mod. As the server and client code is different, some mods have different config files for the server and client.

What should work is if you download all the client config files from a friend who can connect and replace your own client config with the downloaded ones. As then there is no difference between config files from a working client and your client

#7

IMHO, the best test would be to do this:

Ask all the players to move (not remove) their config directories away out of the path.
You do the same.

let the server come up with the default config files that the mods generate on their first-run.
let the client come up with the default config files that the mods generate on their first-run.

Then check
a) does the server start up and run as expected.
b) does a client when attempting to connect to the server run as expected.

If you have the error then, it isn’t the config files. If it doesn’t error then there’s a possibility it is the config files.

Again, (using the rule: change one thing at a time)
Leave the server config’s as they were (put them back as-is – remember you moved them away, now put them back)
But move away the client config files (not delete, just move them out of the path )
and then restart the server
and check for

a) does the server start up as expected.
b) do clients connect as expected

Rinse repeat for the config directories that show working client operation, leaving the server-side along.

Divide and conquer
Change one variable at a time
etc…