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

Forge 1.12.2 - 14.23.4.2768 Startup Crash

Fandomaniac

By Fandomaniac
in Support & Bug Reports

 Share

Recommended Posts

LexManos Reality Controller

LexManos

Posted
Posted


WARNING: coremods are present:
  CreativePatchingLoader (CreativeCore_v1.9.32_mc1.12.2.jar)
  MalisisCorePlugin (malisiscore-1.12.2-6.4.0.jar)
  CTMCorePlugin (CTM-MC1.12.2-0.3.2.18.jar)
  CamPatchingLoader (1.12.2.minecamera-1.1.2.jar)
  SSLoadingPlugin (SereneSeasons-1.12.2-1.2.6-universal.jar)
  ItemPatchingLoader (ItemPhysic_Full_1.4.16_mc1.12.2.jar)
  PassableLeavesCore (PassableLeavesCore-1.12.2-1.0.0.jar)
  FirstAid CoreMod (firstaid-core-1.5.9.jar)
  DynamicSurroundingsCore (DynamicSurroundings-1.12.2-3.4.9.16.jar)
  BetterFoliageLoader (BetterFoliage-MC1.12-2.1.10.jar)
Contact their authors BEFORE contacting forge

  • Thanks 1

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
Fandomaniac Tree Puncher

Fandomaniac

Posted
  • Author
Posted (edited)

Sorry for the ping. I'm just not sure what I need to tell these mod authors. My modpack runs great on Forge 1.12.2 - 14.23.4.2762 and below. What should I tell these mod authors when I contact them?

 

Sorry again for the ping. I didn't know that it was a no no here.

Edited by Fandomaniac
Link to comment
Share on other sites
Cadiboo Reality Controller

Cadiboo

Posted
Posted
56 minutes ago, Fandomaniac said:

Sorry for the ping. I'm just not sure what I need to tell these mod authors. My modpack runs great on Forge 1.12.2 - 14.23.4.2762 and below. What should I tell these mod authors when I contact them?

 

Sorry again for the ping. I didn't know that it was a no no here.

If I had to guess, Forge added a feature (or one of the mods added/removed a feature) and this breaks the other mods. Tell them to make sure that their mods work with the latest Forge versions

About Me

Spoiler

My Discord - Cadiboo#8887

My Website - Cadiboo.github.io

My Mods - Cadiboo.github.io/projects

My Tutorials - Cadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Link to comment
Share on other sites
Fandomaniac Tree Puncher

Fandomaniac

Posted
  • Author
Posted
1 hour ago, Cadiboo said:

ALSO The Forge Version that they “Don’t  work on” is a DEVELOPMENT BUILD. Use the Stable build (2705) if you want compatibility & stability.

 

 

According to the Forge Homepage/Files section, Forge 1.12.2 - 14.23.4.2768 is also the Recommended Stable build.

Link to comment
Share on other sites
Avatair Tree Puncher

Avatair

Posted
Posted

From the look of both log snippets there is a coremod incompatibility. Both errors would occur if argument list of a method has changed (e.g. after a forge update) and one of the core mods assumes that the old argument list still persists and tries accessing an unexisting argument.

 

First snippet https://pastebin.com/qLAE9Qhc is impacting living entities. And the second snippet https://paste.ee/p/mr7DK is impacting chunk rendering. If you suspect, that one of the listed mods at the end of the log is connected to at least one of the both impacts then you could try to remove it and see what happens.

Link to comment
Share on other sites
Fandomaniac Tree Puncher

Fandomaniac

Posted
  • Author
Posted

I removed all mods and added them back, one-at-a-time. I found the 2 mods in my pack that crash with Forge 1.12.2 - 14.23.4.2768. They are: 

  • Obfuscate
  • NotEnoughItems

Both mods run fine on Forge 1.12.2 - 14.23.4.2762 and below. Do you know why these mods crash on Forge 1.12.2 - 14.23.4.2768 and not Forge 1.12.2 - 14.23.4.2762 and below? I'm asking so I can pass the info to their developers, so they can be patched.

Link to comment
Share on other sites
LexManos Reality Controller

LexManos

Posted
Posted

Boys and girls, Don't be like Zim, he has received a 24 hour ban for being an ass.

He had to come in here getting offended on behalf of Fandomaniac, for a simple exchange that we resolved in one post. 

As for his accusations that I am a crap programmer who breaks mods on purpose, No. These are COREMODS that are breaking.

And as everyone knows COREMODS are mods that are explicitly designed to screw with the internals of Minecraft/other mods in unknown ways.

By default being prone to breaking, and as such unsupported on these forums.

This is why the crash log says go to them BEFORE coming to Forge. Which is what my original post pointed out, and this whole thing could of been avoided if more people read their log files.

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
Fandomaniac Tree Puncher

Fandomaniac

Posted
  • Author
Posted

LexManos, mine wasn't resolved. In my case, core mods were not responsible. Obfuscate and NotEnoughItems are both not core mods.Both mods run fine on Forge 1.12.2 - 14.23.4.2762 and below. Do you know why these mods crash on Forge 1.12.2 - 14.23.4.2768 and not Forge 1.12.2 - 14.23.4.2762 and below? I'm guessing something changed starting with Forge 1.12.2 - 14.23.4.2763 that is now making both those mods incompatible. Please advise on what info I should pass on to those mod developers, so this can be fixed. Any info you can provide would be greatly appreciated.

Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Obfuscate is a coremod, besides Forge plainly flagging it as such, it utilizes a library that in this case has no purpose other than coremodding.

While NEI is not a coremod itself, it requires JEI as well as CodeChickenLib (which has coremod functionality) to function.

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

I don't know the nitty gritty of how these mods work.

The easiest explanation is that Forge tries its hardest to be the ONLY coremod that anyone needs, people making their own coremods makes this a "too many cooks in the kitchen" situation.

People making their own coremods assume things when they make their coremods, and when Forge changes something that they were making assumptions about, things go wrong.

 

Yes the Forge change "causes" the issue.

NO this is not Forge's fault, it is explicitly stated that coremods do not receive official support and this is one of the many reason why.

People making coremods have to accept that when there is a change in Forge they are responsible for keeping their crap compatible.

 

If you continue to argue that this is Forge's fault then you do not understand the regrettable arrangement between Forge and modders who insist on making coremods.

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
Fandomaniac Tree Puncher

Fandomaniac

Posted
  • Author
Posted

I wasn't arguing or blaming anyone. I'm just trying to help fix bugs by reporting them to developers. I have sent issue reports to the developers of both Obfuscate and NotEnoughItems. I was trying to get as much info as I can to help them troubleshoot. Thanks for the info you have provided. If anyone else has any additional info to help get these bugs squashed, please post it here and I will refer the developers to this post.

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


×
×
  • Create New...

Important Information

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

  I accept