Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

1.12.2, fatally missing registry entries


Recommended Posts

Forge 14.23.0.2522

the game throws the error in the title to any players whom try and join the server. fresh server and fresh world

will comment forge latest logs below (forum doesn't like me posting them both at the same time)

edit: had to link to my google drive for the logs. forum wont let me post them

fml-client-latest.log
https://drive.google.com/open?id=15bZo5yymKCCxdKb1MiAwRgh5pV9hqpYl
fml-server-latest.log
https://drive.google.com/open?id=1UOoCC0-KKfgN-qj1DxtSvj44eyUfg9XW

Edited by PoiDoe
Link to post
Share on other sites
[13:11:29] [User Authenticator #1/INFO]: UUID of player PoiDoe is b8e21e8a-3224-4c26-aede-c670a05ba57d
[13:11:29] [Netty Epoll Server IO #2/INFO] [FML]: Client protocol version 2
[13:11:29] [Netty Epoll Server IO #2/INFO] [FML]: Client attempting to join with 83 mods : blockdrops@1.3.0,netherportalfix@5.3.13,binniecore@unspecified,mca@1.12.2-5.3.1,jei@4.8.0.111,dynamiclights_theplayer@1.1.3,dynamiclights_floodlights@1.0.3,radixcore@1.12.x-2.2.1,bibliocraft@2.4.3,dynamiclights@1.4.6,multimine@1.5.7,bdlib@1.14.3.10,kleeslabs@5.3.2,mcp@9.42,jeibees@0.9.0.5,ctm@MC1.12-0.2.3.9,cookingforblockheads@6.3.6,aroma1997core@1.3.0.2,chameleon@1.12-4.1.3,bookshelf@2.2.485,inventorytweaks@1.63+release.109.220f184,harvestcraft@1.12.2a,underphangables@1.0.0,extrabees@2.5.0.86,dynamiclights_otherplayers@1.0.9,waila@1.8.22,packingtape@0.7.4,enderstorage@2.4.0.122,jeresources@0.8.5.27,immersivepetroleum@1.1.3,forge@14.23.0.2531,immersivetech@1.3.4,infernalmobs@1.7.3,ironchest@1.12.2-7.0.34.820,extratrees@2.5.0.86,minecraft@1.12.2,tconstruct@1.12-2.7.4.34,dldungeonsjdg@1.10.0,dynamiclights_entityclasses@1.0.1,immersiveengineering@0.12-74,jehc@1.3.1,botany@2.5.0.86,biomesoplenty@7.0.1.2302,baubles@1.5.1,applecore@2.2.2,aromabackup@2.1.1.3,botania@r1.10-349,ding@1.0.1,dynamiclights_dropitems@1.1.0,enchiridion@3.3.3,gendustry@1.6.5.6,llor@1.1.4-mc1.12,dynamiclights_mobequipment@1.1.0,fairylights@2.1.1,genetics@2.5.0.86,dynamiclights_flamearrows@1.0.1,extrautils2@1.0,roguelike@1.8.0,bloodmoon@1.5.2,quark@r1.3-114,ic2@2.8.16-ex112,mantle@1.12-1.3.1.21,randomthings@4.0.8,autoreglib@1.3-15,storagedrawers@1.12-5.2.5,toughasnails@3.0.0.68,harvest@1.12-1.2.6-18,FML@8.0.99.99,aromabackuprecovery@2.1.1.3,chisel@MC1.12-0.0.14.18,autoplant@1.12-1.0.0,hardcoredarkness@1.9,flatcoloredblocks@mc1.12-6.6,dynamiclights_onfire@1.0.7,spiceoflife@1.3.11,dynamiclights_creepers@1.0.6,codechickenlib@3.1.3.313,fastleafdecay@v14,chiselsandbits@14.9,wailaharvestability@1.1.12,forestry@5.7.0.209,binniedesign@1.0,betteradvancements@0.0.4.16
[13:11:30] [Server thread/INFO]: PoiDoe lost connection: Disconnected
[13:11:30] [Server thread/INFO]: PoiDoe left the game

From the server terminal
client:
nGu1jCU.png

Edited by PoiDoe
added client image
Link to post
Share on other sites

Your log ends at: [12:35:13] [main/INFO] [BetterFps/]: Patching net.minecraft.server.dedicated.DedicatedServer... (nz)

Either way the problem is that your modpack on the server doesnt match the modpack on the client.

Make sure you have all the same versions/mods/cofigs installed on both sides.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Patreon: http://www.patreon.com/lexmanos
Paypal: http://paypal.me/LexManos

BitCoin: 1Q8rWvUNMM2T1ZfDaFeeYQyVXtYoeT6tTn

Link to post
Share on other sites
4 hours ago, LexManos said:

Your log ends at: [12:35:13] [main/INFO] [BetterFps/]: Patching net.minecraft.server.dedicated.DedicatedServer... (nz)

Either way the problem is that your modpack on the server doesnt match the modpack on the client.

Make sure you have all the same versions/mods/cofigs installed on both sides.

i'm sure they are running the same configs and mods as i took the mods folder and config folder from the client and gave it to the server

edit: sorry for the late reply only just got off work

edit 2: just recopied everything over again thinking maybe a file broke somewhere and it seems to be working now. 

Edited by PoiDoe
Link to post
Share on other sites
  • 2 months later...
  • 3 months later...

I have the same problem, but not on a server. Trying to get on a LAN, same version I downloaded both versions at the same time, same version of Minecraft. When I go to join the LAN game, the server side gets a notice that I disconnected, (never that I connected) and client side gets either "Connection Lost" or "Fatally missing registry entries". I've tried doing a LAN with other modpacks and it works fine. Re-downloaded everything, still getting the issues. When I clear it through Twitch are there other configs I have to manually delete? Everything I could find related to the pack was gone.

Link to post
Share on other sites
  • 11 months later...

Please do not necro old threads, if you have an issue please make your own thread.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to post
Share on other sites
Guest
This topic is now closed to further replies.


  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • Understood, and I'll go check that out. Thank you so much!
    • This. The reason for this is that DeferredRegister relies on static initializers. If you put your RegistryObjects in some random class it is not guaranteed that that class is actually initialized by the time your DeferredRegister is. Hence: Put the DeferredRegister and its entries in the same class. @ObjectHolder is explained here: https://mcforge.readthedocs.io/en/latest/concepts/registries/#using-objectholder
    • Okay, thanks for the help! A few questions. BLOCKS and ITEMS are in the same class as each other- it's called 'registry'. (forgot to capitalize, oops- I'll fix that momentarily.) What exactly shouldn't be in separate classes? Are you saying that my actual RegistryObjects (the individual blocks, items, etc.) should all be in the same class? Or that the DeferredRegisters should all be in the same class? Or that all the RegistryObject<Block>s should be in the same class as the DeferredRegister<Block>, and the RegistryObject<Item>s should be in the same class as the DeferredRegister<Item>, but those two classes don't necessarily have to be the same? What is @ObjectHolder, what does it do, and where can I go to learn more? (That is, assuming it's a Forge thing. If it's a Java thing I don't know, say so and I'll go research it elsewhere- I understand and respect that this forum isn't a place to look for Java help.)
    • First of all the BLOCKS and ITEMS fields (i.e. your DeferredRegister instances) should not be in a separate class. Put them in the same class or you will have issues. No, you cannot, because then you defeat the entire purpose of DeferredRegister. You must create your registry objects (blocks, items, etc.) in the registry event. DeferredRegister manages this for you. If you don't want this, you can also manually subscribe to RegistryEvent and create and register your things there. You can then use @ObjectHolder to obtain the instances for your registry entries. You can also mix and match these if you so choose - you can have @ObjectHolder annotated fields and things registered by DeferredRegister will still end up there and equally you can register things manually in RegistryEvent and create your own RegistryObject (just call the of method) which you can then use to access them. But what you cannot do is create registry objects (i.e. blocks and items) outside registry events.
    • From my understanding, all of my blocks, items, and whatnot should be registered like this: public static final RegistryObject<Block> CRASH_PAD = registry.BLOCKS.register("crash_pad", () -> new CrashPadBlock(AbstractBlock.Properties.of(Material.CLAY, MaterialColor.GRASS).friction(0.8F).sound(SoundType.SLIME_BLOCK).noOcclusion())); public static final RegistryObject<Item> ALCHEMICAL_FLASK = registry.ITEMS.register("alchemical_flask", () -> new Item(new Item.Properties().tab(ItemGroup.TAB_MATERIALS))); If I then wished to refer to the crash_pad Block, or the alchemical_flask Item, do I have to refer to them as 'registry.CRASH_PAD.get()' and 'registry.ALCHEMICAL_FLASK.get()'? This seems a bit roundabout. Can I define the blocks as Blocks and the items as Items before creating and registering RegistryObject<T>s from them, or do I have to always get the blocks and items from their RegistryObjects?
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.