Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

HandshakeMessageHandler Error on Join

Breymja

By Breymja
in Support & Bug Reports

 Share

Recommended Posts

Breymja Tree Puncher

Breymja

Posted
Posted (edited)

I got one of those problems, that seem to be happening more often in the last time (the latest topics are all about this error) after upgrading to 1690, then 2703 from 2655 and can't join my server anymore. Server and Client mods are identical, as are the config files - i quadruple checked this. When something was wrong there earlier i got "fatally missing registry entries".

 

I'm a bit off what's wrong.

Latest.log is here: https://gist.github.com/D3nnis3n/81678b202af6dc5e7d5169792e32773f

 

Error Message is the same as in the other thread: https://gyazo.com/fb779f21c12c45619038cf413e712184

 

Would appreciate any help what's the cause of it, no mod is named.

Edited by Breymja
Link to comment
Share on other sites
LexManos Reality Controller

LexManos

Posted
Posted

    Loaded coremods (and transformers): 


BetterFontsCore ([C]-TrueTypeFontReplacement-1.9.1.jar)
  cubex2.ttfr.BFClassTransformer
MalisisSwitchesPlugin (malisisswitches-1.12.2-5.1.0.jar)
  
SSLoadingPlugin (SereneSeasons-1.12.2-1.2.2-universal.jar)
  sereneseasons.asm.transformer.EntityRendererTransformer
  sereneseasons.asm.transformer.WorldTransformer
LoadingPlugin (Reskillable-1.12.2-1.5.1.jar)
  codersafterdark.reskillable.base.asm.ClassTransformer
SignPictureCorePlugin ([C]-SignPicture-2.8.1.jar)
  com.kamesuta.mc.signpic.asm.SignPictureTransformer
DynamicSurroundingsCore ([T]-DynamicSurroundings-3.4.9.13.jar)
  org.blockartistry.DynSurround.asm.Transformer
MMFMLCorePlugin ([CS]-MultiMine-1.12.2.jar)
  atomicstryker.multimine.common.fmlmagic.MMTransformer
CorePlugin (SmoothFont-1.12.2-1.15.jar)
  bre.smoothfont.asm.Transformer
AppleCore ([T]-AppleCore-3.1.1.jar)
  squeek.applecore.asm.TransformerModuleHandler
Plugin ([CS]-NotEnoughIDs-1.5.4.2.jar)
  ru.fewizz.neid.asm.Transformer
CorePlugin ([CS]-ForgeEndertech-4.3.5.0.jar)
  
HammerCoreCore (HammerCore-1.12.2-1.9.9.4.jar)
  com.pengu.hammercore.asm.HammerCoreTransformer
ShetiPhian-ASM (shetiphiancore-1.12.0-3.5.6.jar)
  shetiphian.asm.ClassTransformer
ISCore (ImprovableSkills_1.12.2-3.4.1r.jar)
  com.endie.is.asm.ImprovableSkillsTransformer
BetterFoliageLoader ([C]-BetterFoliage-2.1.10.jar)
  mods.betterfoliage.loader.BetterFoliageTransformer
ForgelinPlugin (Forgelin-1.6.0.jar)
  
IELoadingPlugin (ImmersiveEngineering-core-0.12-82.jar)
  blusunrize.immersiveengineering.common.asm.IEClassTransformer
weaponlib (mw-1.11.7.1_mc1.12.2.jar)
  com.vicmatskiv.weaponlib.core.WeaponlibClassTransformer
LoadingPlugin ([CS]-AdChimneys-3.3.0.0.jar)
  com.endertech.minecraft.mods.adchimneys.world.WorldData$BlockRandomTick
EnderCorePlugin ([CS]-EnderCore-0.5.22.jar)
  com.enderio.core.common.transform.EnderCoreTransformer
TransformerLoader (OpenComputers-MC1.12.2-1.7.2.67.jar)
  li.cil.oc.common.asm.ClassTransformer
EcomodLoadingPlugin (EcologyMod-1.12.2-1.5.1.0.jar)
  ecomod.asm.EcomodClassTransformer
MalisisCorePlugin ([T]-MalisisCore-6.4.0.jar)
  
Do not report to Forge! Remove FoamFixAPI (or replace with FoamFixAPI-Lawful) and try again. ([CS]-FoamFix-0.9.9.1-Anarchy.jar)
  pl.asie.foamfix.coremod.FoamFixTransformer

Remove all that shit and try again. ESPECIALLY 'NotEnoughIDs' as it is KNOWN to screw up handshakes as well as corrupt worlds.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites
Breymja Tree Puncher

Breymja

Posted
  • Author
Posted (edited)

I removed all CoreMods despite NotEnoughIDs and the issue persists:

https://gist.github.com/D3nnis3n/e3480396cd3e294e704be79ae31c6114

 

I'm very sure NotEnoughIDs is not the reason. We use it for a year on our live-server and never had problems before.

Even if it would be the reason, we can't remove it as, despite for this test we removed loads of mods, this happens after it's removed and therefore no further testing is possible:

Quote

 

Time: 5/26/18 7:54 PM
Description: Initializing game

java.lang.RuntimeException: Invalid id 4096 - maximum id range exceeded.
    at net.minecraftforge.registries.ForgeRegistry.add(ForgeRegistry.java:293)
    at net.minecraftforge.registries.ForgeRegistry.add(ForgeRegistry.java:279)
    at net.minecraftforge.registries.ForgeRegistry.register(ForgeRegistry.java:112)
    at mod.flatcoloredblocks.FlatColoredBlocks.registerBlocks(FlatColoredBlocks.java:179)
    at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_600_FlatColoredBlocks_registerBlocks_Register.invoke(.dynamic)
    at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90)
    at net.minecraftforge.fml.common.eventhandler.EventBus$1.invoke(EventBus.java:144)
    at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:182)
    at net.minecraftforge.registries.GameData.fireRegistryEvents(GameData.java:738)
    at net.minecraftforge.fml.common.Loader.preinitializeMods(Loader.java:628)
    at net.minecraftforge.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:245)
    at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:466)
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:377)
    at net.minecraft.client.main.Main.main(SourceFile:123)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
    at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

 

Any other ideas?

 

//EDIT:

I forgot AdChimneys and ForgeEndertech. Removed those two, also. Same faulty result.

Edited by Breymja
Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted
8 minutes ago, Breymja said:

I removed all CoreMods despite NotEnoughIDs and the issue persists:

Quote

[19:48:38] [main/INFO] [FML]: Loading tweaker optifine.OptiFineForgeTweaker from [C]-OptiFine-D3.jar

[19:48:38] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in [CS]-AdChimneys-3.3.0.0.jar. This is not recommended, @Mods should be in a separate jar from the coremod.

[19:48:38] [main/WARN] [FML]: The coremod com.endertech.minecraft.mods.adchimneys.LoadingPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[19:48:38] [main/WARN] [FML]: The coremod LoadingPlugin (com.endertech.minecraft.mods.adchimneys.LoadingPlugin) is not signed!

[19:48:38] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in [CS]-ForgeEndertech-4.3.5.0.jar. This is not recommended, @Mods should be in a separate jar from the coremod.

[19:48:38] [main/WARN] [FML]: The coremod com.endertech.minecraft.forge.coremod.CorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[19:48:38] [main/WARN] [FML]: The coremod CorePlugin (com.endertech.minecraft.forge.coremod.CorePlugin) is not signed!

[19:48:38] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in [CS]-MrTJPCore-2.1.1.27.jar. This is not recommended, @Mods should be in a separate jar from the coremod.

[19:48:38] [main/ERROR] [FML]: Coremod mrtjp.core.handler.CorePlugin: Unable to class load the plugin java.lang.ClassNotFoundException: mrtjp.core.handler.CorePlugin

[19:48:38] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in [CS]-NotEnoughIDs-1.5.4.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod.

[19:48:38] [main/WARN] [FML]: The coremod ru.fewizz.neid.asm.Plugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft

[19:48:38] [main/WARN] [FML]: The coremod Plugin (ru.fewizz.neid.asm.Plugin) is not signed!

If you did remove your coremods you posted the wrong log

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 comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted
1 hour ago, LexManos said:

'NotEnoughIDs' as it is KNOWN to screw up handshakes

Lex knows infinitely more than me in this matter and as far as I can tell with my novice experience the handshake is where this issue begins.

I'm sorry but it appears your "crucial" mod is the source of your problems.

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 comment
Share on other sites
Breymja Tree Puncher

Breymja

Posted
  • Author
Posted (edited)

I don't believe that, as rollbacking to Forge 2655 fixes the problem. I can't remove that mod, so it's no option. I also don't believe it causes this.

So if the Mod is the problem, something must have changed in a forge version after that. But anyway, i can't test if it is NEID, as we got too many IDs used.

Edited by Breymja
Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

I can tell you that the FMLHandshakeMessage class the error originates from has not been changed at all between those two versions (according to a git diff check between the two commits)

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 comment
Share on other sites
Breymja Tree Puncher

Breymja

Posted
  • Author
Posted (edited)

Well, i'll put a link to this topic on their issue tracker. Maybe they look into it - but i still don't think that's the issue.

https://github.com/fewizz/NotEnoughIDs/issues/74

 

As long as we can use 2655, we're fine. As a big amount of mods out there have coremods, they'll probably be there for a reason.

 

@DaemonUmbra

Yeah, but something must have changed, as the bug appears when updating forge 2655 to 2690 / 2703 and rollbacking to 2655 fixes it. Easy as that.

Edited by Breymja
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept