Jump to content

[1.16.1] Library Mod / Dependencies


Maxi07

Recommended Posts

I have made a mod which contains a few class I need across other mods. I want to use the code of this mod like I can use the minecraft and forge code in all my mods.

Unfortunately I dont know anything about gradle and was unable to find something helpful...

 

I have built the jar of my lib mod with gradlew build and now I want to use it in my other mods, what do I have to do?

 

Thanks for helping!

Link to comment
Share on other sites

You have two choices, either you put it somewhere and then each of your mods points to where you put it, or you create a multi-build project

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

1 hour ago, Maxi07 said:

I think I want the first option: I want to have this mod as a dependency for every other mod

 

But what do I have to do, to get this working?

I think this what you are looking for these can be found in any ExampleMod classes forge show us how communcation works between other mods
 

private void enqueueIMC(final InterModEnqueueEvent event)
    {
        // some example code to dispatch IMC to another mod
        InterModComms.sendTo("examplemod", "helloworld", () -> { LOGGER.info("Hello world from the MDK"); return "Hello world";});
    }

    private void processIMC(final InterModProcessEvent event)
    {
        // some example code to receive and process InterModComms from other mods
        LOGGER.info("Got IMC {}", event.getIMCStream().
                map(m->m.getMessageSupplier().get()).
                collect(Collectors.toList()));
    }

But i'm not sure about this i never tried anything like this but if this is not working then you can take a look at the source of any library mod on curseforge

Link to comment
Share on other sites

@Crazzy4999 Thanks for helping, but I think this not what I want.

I am pretty sure a have to add something to my build.gradle, but because I dont know anything about gradle I dont know what.

 

What I want:

23 hours ago, Maxi07 said:

I want to use the code of this mod like I can use the minecraft and forge code in all my mods.

In all mods I am able to use the minecraft classes like "Item" and "Block" (e.g. "new Item(new Properties().group(ItemGroup.MATERIALS))" )

Link to comment
Share on other sites

I believe you'll probably want to set up publishing your library to mavenLocal (it's a maven repository structure on your disk), then pull it from there.

(Please attempt to look up what I've mentioned before continuing)

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

I'm not sure that works anymore, I need to look at that.

And even if it works the same way it used to, it working would depend on how your library is built, whether it's reobfed or not

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

1 minute ago, DaemonUmbra said:

And even if it works the same way it used to, it working would depend on how your library is built, whether it's reobfed or not

I don't fully understand this, but enough for me to say that I don't want this problem.

So you recommend using mavenLocal... I dont know what this is and how I can get it working, but I will try it. And could you please give a few examples or, even better, a guide?

Link to comment
Share on other sites

Well you'll still have the issue of do you want to reobf with build or do you want to reobf with publish?

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

Just now, BlockyPenguin said:

I'm not going to pretend to know anything about making a library mod, but don't you just add it as a dependency in the mods.toml file of the mods that depend on your library?

Thanks for helping, but this is only for forge, to say the mod is missing instead of just crashing

Link to comment
Share on other sites

Just now, Maxi07 said:

Thanks for helping, but this is only for forge, to say the mod is missing instead of just crashing

Ah right ok :) What about adding it to the build path of the other mod? In eclipse, if you right click your project folder, go to build path > configure build path > libraries and then press "Add external JARs"image.png.2258ad148ea8e45951acda6eb617a417.png
 

I mean, I can see forge in there? Again, I don't know much about lib mods, this is just my guesswork.

Today (22/10/20) I reached 100 posts!

I'm probably more excited than I should be for something so realistically minor...

Link to comment
Share on other sites

49 minutes ago, Maxi07 said:

What about that "libs" folder I have heard of?

Quoted from the example mod mdk: You may put jars on which you depend on in ./libs or you may define them like so..

Just putting the in ./libs does not work...

 

But now I found this:

repositories {

    flatdir { dir 'libs' }

}

 

----------------------------------------------------------

 

1 minute ago, BlockyPenguin said:

Ah right ok :) What about adding it to the build path of the other mod? In eclipse, if you right click your project folder, go to build path > configure build path > libraries and then press "Add

I will try this

Link to comment
Share on other sites

4 minutes ago, BlockyPenguin said:

Ah right ok :) What about adding it to the build path of the other mod? In eclipse, if you right click your project folder, go to build path > configure build path > libraries and then press "Add external JARs"image.png.2258ad148ea8e45951acda6eb617a417.png
 

I mean, I can see forge in there? Again, I don't know much about lib mods, this is just my guesswork.

No that's not how you do it. (I mean it is for regular Eclipse projects, but this is a Gradle project)

 

If you make a multi-build project you just have the mod project depend on the library project's output and have everything reobf on publish.

If you have every project separate you reobf with build, have the library publish to mavenLocal (or use a flatDir repo) and have your mod project get the library and fg.deobf() it

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

It deobfuscates things to your current mappings

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

2 minutes ago, DaemonUmbra said:

No that's not how you do it. (I mean it is for regular Eclipse projects, but this is a Gradle project)

 

If you make a multi-build project you just have the mod project depend on the library project's output and have everything reobf on publish.

If you have every project separate you reobf with build, have the library publish to mavenLocal (or use a flatDir repo) and have your mod project get the library and fg.deobf() it

ah ok :)

Today (22/10/20) I reached 100 posts!

I'm probably more excited than I should be for something so realistically minor...

Link to comment
Share on other sites

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

I am making progress...

 

I added

repositories {
   flatDir { dir 'libs' }
}

and 

implementation fg.deobf('maxi.simpledev:simpledev-1.16.1:1.0')

to my build.gradle and run

.\gradlew --refresh-dependencies

.\gradlew genEclipseRuns eclipse

again...

 

It only works halfway: Eclipse always says: "Source not found". Maybe it is this problem:

20 hours ago, DaemonUmbra said:

Well you'll still have the issue of do you want to reobf with build or do you want to reobf with publish?

My build.gradle has this default line:

jar.finalizedBy('reobfJar') 

But my jar is not obfuscated, I can use an online decompiler and can read my code (only one subclass where I override one function, the function is only numbers and letters)

But then, why I need fg.deobf if it does not do anything (it seems like)?

 

Edit: 

19 hours ago, DaemonUmbra said:

If you make a multi-build project you just have the mod project depend on the library project's output and have everything reobf on publish.

Maybe a multi-build project is easier?

Edited by Maxi07
Link to comment
Share on other sites

Does your library use any Minecraft code?

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

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.

Announcements




  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • ironically it is a create based modpack so i need help understanding whats contradicting it 
    • An unexpected issue occurred and the game has crashed. (Exit Code 1) Heres the crash report (there are mods btw) [16:25:39] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [16:25:39] [main/INFO]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLTweaker [16:25:39] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLTweaker [16:25:39] [main/INFO]: Forge Mod Loader version 14.23.5.2859 for Minecraft 1.12.2 loading [16:25:39] [main/INFO]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_51, running on Windows 10:amd64:10.0, installed at C:\Users\bruiser\curseforge\minecraft\Install\runtime\jre-legacy\windows-x64\jre-legacy [16:25:40] [main/INFO]: Searching C:\Users\bruiser\curseforge\minecraft\Instances\Fnaf 6\mods for mods [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from 3dSkinLayers-forge-mc1.12.2-1.2.0.jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from [1.12.2] SecurityCraft v1.9.9.jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from [___MixinCompat-1.1-1.12.2___].jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from _supermartijn642corelib-1.1.17-forge-mc1.12.jar [16:25:40] [main/INFO]: Loading tweaker guichaguri.betterfps.tweaker.BetterFpsTweaker from BetterFps-1.4.8.jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from controllable-0.11.2-1.12.2.jar [16:25:40] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in CreativeCore_v1.10.71_mc1.12.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [16:25:40] [main/WARN]: The coremod com.creativemd.creativecore.core.CreativePatchingLoader does not have a MCVersion annotation, it may cause issues with this version of Minecraft [16:25:40] [main/WARN]: The coremod CreativePatchingLoader (com.creativemd.creativecore.core.CreativePatchingLoader) is not signed! [16:25:40] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in CTM-MC1.12.2-1.0.2.31.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [16:25:40] [main/WARN]: The coremod team.chisel.ctm.client.asm.CTMCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [16:25:40] [main/WARN]: The coremod CTMCorePlugin (team.chisel.ctm.client.asm.CTMCorePlugin) is not signed! [16:25:40] [main/WARN]: Found FMLCorePluginContainsFMLMod marker in ears-forge-1.12-1.4.6.jar. This is not recommended, @Mods should be in a separate jar from the coremod. [16:25:40] [main/WARN]: The coremod com.unascribed.ears.common.agent.NewForgeCoremod does not have a MCVersion annotation, it may cause issues with this version of Minecraft [16:25:40] [main/WARN]: The coremod Ears (com.unascribed.ears.common.agent.NewForgeCoremod) is not signed! [16:25:40] [main/INFO]: Loading tweaker gg.essential.loader.stage0.EssentialSetupTweaker from essential_1-3-2-2_forge_1-12-2.jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from malisiscore-1.12.2-6.5.1.jar [16:25:40] [main/INFO]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from movingelevators-1.4.7-forge-mc1.12.jar [16:25:40] [main/INFO]: Loading tweaker optifine.OptiFineForgeTweaker from OptiFine_1.12.2_HD_U_G5.jar [16:25:40] [main/WARN]: The coremod shetiphian.asm.TweakPlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [16:25:40] [main/WARN]: The coremod ShetiPhian-ASM (shetiphian.asm.TweakPlugin) is not signed! [16:25:40] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [16:25:40] [main/INFO]: Loading tweak class name org.spongepowered.asm.launch.MixinTweaker [16:25:40] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.8.5 Source=file:/C:/Users/bruiser/curseforge/minecraft/Instances/Fnaf%206/mods/3dSkinLayers-forge-mc1.12.2-1.2.0.jar Service=LaunchWrapper Env=CLIENT [16:25:41] [main/DEBUG]: Instantiating coremod class SecurityCraftLoadingPlugin [16:25:41] [main/DEBUG]: The coremod net.geforcemods.securitycraft.SecurityCraftLoadingPlugin requested minecraft version 1.12.2 and minecraft is 1.12.2. It will be loaded. [16:25:41] [main/WARN]: The coremod SecurityCraftLoadingPlugin (net.geforcemods.securitycraft.SecurityCraftLoadingPlugin) is not signed! [16:25:41] [main/INFO]: Compatibility level set to JAVA_8 [16:25:41] [main/DEBUG]: Enqueued coremod SecurityCraftLoadingPlugin [16:25:41] [main/DEBUG]: Instantiating coremod class CoreModPlugin [16:25:41] [main/TRACE]: coremod named SuperMartijn642's Core Lib Plugin is loading [16:25:41] [main/DEBUG]: The coremod com.supermartijn642.core.coremod.CoreModPlugin requested minecraft version 1.12.2 and minecraft is 1.12.2. It will be loaded. [16:25:41] [main/WARN]: The coremod SuperMartijn642's Core Lib Plugin (com.supermartijn642.core.coremod.CoreModPlugin) is not signed! [16:25:41] [main/DEBUG]: Added access transformer class com/supermartijn642/core/coremod/CoreLibAccessTransformer to enqueued access transformers [16:25:41] [main/DEBUG]: Enqueued coremod SuperMartijn642's Core Lib Plugin [16:25:41] [main/DEBUG]: Instantiating coremod class ControllablePlugin [16:25:41] [main/TRACE]: coremod named Controllable is loading [16:25:41] [main/DEBUG]: The coremod com.mrcrayfish.controllable.asm.ControllablePlugin requested minecraft version 1.12.2 and minecraft is 1.12.2. It will be loaded. [16:25:41] [main/DEBUG]: Found signing certificates for coremod Controllable (com.mrcrayfish.controllable.asm.ControllablePlugin) [16:25:41] [main/DEBUG]: Found certificate 4d54165f7f65cf475bf13341569655b980a5b430 [16:25:41] [main/DEBUG]: Added access transformer class com.mrcrayfish.controllable.asm.ControllableAccessTransformer to enqueued access transformers [16:25:41] [main/DEBUG]: Enqueued coremod Controllable [16:25:41] [main/DEBUG]: Instantiating coremod class MalisisCorePlugin [16:25:41] [main/WARN]: The coremod net.malisis.core.asm.MalisisCorePlugin does not have a MCVersion annotation, it may cause issues with this version of Minecraft [16:25:41] [main/WARN]: The coremod MalisisCorePlugin (net.malisis.core.asm.MalisisCorePlugin) is not signed! [16:25:41] [main/DEBUG]: Enqueued coremod MalisisCorePlugin [16:25:41] [main/DEBUG]: Instantiating coremod class CoreMod [16:25:41] [main/TRACE]: coremod named Moving Elevators Plugin is loading [16:25:41] [main/DEBUG]: The coremod com.supermartijn642.movingelevators.core.CoreMod requested minecraft version 1.12.2 and minecraft is 1.12.2. It will be loaded. [16:25:41] [main/WARN]: The coremod Moving Elevators Plugin (com.supermartijn642.movingelevators.core.CoreMod) is not signed! [16:25:41] [main/DEBUG]: Enqueued coremod Moving Elevators Plugin [16:25:41] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:41] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:41] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:41] [main/INFO]: Loading tweak class name guichaguri.betterfps.tweaker.BetterFpsTweaker [16:25:41] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:41] [main/INFO]: Loading tweak class name gg.essential.loader.stage0.EssentialSetupTweaker [16:25:42] [main/INFO]: Starting Essential Loader (stage2) version 1.6.0 (b0b46ed40e44f9aaf7086a0d8c46a674) [stable] [16:25:45] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:45] [main/WARN]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping [16:25:45] [main/INFO]: Loading tweak class name optifine.OptiFineForgeTweaker [16:25:45] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker [16:25:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [16:25:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker [16:25:45] [main/INFO]: Calling tweak class optifine.OptiFineForgeTweaker [16:25:45] [main/INFO]: [optifine.OptiFineForgeTweaker:dbg:56]: OptiFineForgeTweaker: acceptOptions [16:25:45] [main/INFO]: [optifine.OptiFineForgeTweaker:dbg:56]: OptiFineForgeTweaker: injectIntoClassLoader [16:25:45] [main/INFO]: [optifine.OptiFineClassTransformer:dbg:242]: OptiFine ClassTransformer [16:25:45] [main/INFO]: [optifine.OptiFineClassTransformer:dbg:242]: OptiFine ZIP file: C:\Users\bruiser\curseforge\minecraft\Instances\Fnaf 6\mods\OptiFine_1.12.2_HD_U_G5.jar [16:25:45] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:45] [main/DEBUG]: Injecting coremod FMLCorePlugin \{net.minecraftforge.fml.relauncher.FMLCorePlugin\} class transformers [16:25:45] [main/TRACE]: Registering transformer net.minecraftforge.fml.common.asm.transformers.SideTransformer [16:25:45] [main/TRACE]: Registering transformer net.minecraftforge.fml.common.asm.transformers.EventSubscriptionTransformer [16:25:45] [main/TRACE]: Registering transformer net.minecraftforge.fml.common.asm.transformers.EventSubscriberTransformer [16:25:45] [main/TRACE]: Registering transformer net.minecraftforge.fml.common.asm.transformers.SoundEngineFixTransformer [16:25:45] [main/DEBUG]: Injection complete [16:25:45] [main/DEBUG]: Running coremod plugin for FMLCorePlugin \{net.minecraftforge.fml.relauncher.FMLCorePlugin\} [16:25:45] [main/DEBUG]: Running coremod plugin FMLCorePlugin [16:25:49] [main/INFO]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557 [16:25:49] [main/INFO]: Found valid fingerprint for Minecraft. Certificate fingerprint cd99959656f753dc28d863b46769f7f8fbaefcfc [16:25:49] [main/DEBUG]: Coremod plugin class FMLCorePlugin run successfully [16:25:49] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:49] [main/DEBUG]: Injecting coremod FMLForgePlugin \{net.minecraftforge.classloading.FMLForgePlugin\} class transformers [16:25:49] [main/DEBUG]: Injection complete [16:25:49] [main/DEBUG]: Running coremod plugin for FMLForgePlugin \{net.minecraftforge.classloading.FMLForgePlugin\} [16:25:49] [main/DEBUG]: Running coremod plugin FMLForgePlugin [16:25:49] [main/DEBUG]: Coremod plugin class FMLForgePlugin run successfully [16:25:49] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:49] [main/DEBUG]: Injecting coremod CreativePatchingLoader \{com.creativemd.creativecore.core.CreativePatchingLoader\} class transformers [16:25:49] [main/DEBUG]: Injection complete [16:25:49] [main/DEBUG]: Running coremod plugin for CreativePatchingLoader \{com.creativemd.creativecore.core.CreativePatchingLoader\} [16:25:49] [main/DEBUG]: Running coremod plugin CreativePatchingLoader [16:25:50] [main/DEBUG]: Coremod plugin class CreativePatchingLoader run successfully [16:25:50] [main/INFO]: Calling tweak class org.spongepowered.asm.launch.MixinTweaker [16:25:50] [main/ERROR]: Mixin config 3dskinlayers.mixins.json does not specify "minVersion" property [16:25:50] [main/ERROR]: Mixin config mixins.mixincompat.json does not specify "minVersion" property [16:25:50] [main/INFO]: Initialised Mixin FML Remapper Adapter with net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper@3e0855b0 [16:25:50] [main/DEBUG]: Injecting coremod SecurityCraftLoadingPlugin \{net.geforcemods.securitycraft.SecurityCraftLoadingPlugin\} class transformers [16:25:50] [main/DEBUG]: Injection complete [16:25:50] [main/DEBUG]: Running coremod plugin for SecurityCraftLoadingPlugin \{net.geforcemods.securitycraft.SecurityCraftLoadingPlugin\} [16:25:50] [main/DEBUG]: Running coremod plugin SecurityCraftLoadingPlugin [16:25:50] [main/DEBUG]: Coremod plugin class SecurityCraftLoadingPlugin run successfully [16:25:50] [main/DEBUG]: Injecting coremod SuperMartijn642's Core Lib Plugin \{com.supermartijn642.core.coremod.CoreModPlugin\} class transformers [16:25:50] [main/DEBUG]: Injection complete [16:25:50] [main/DEBUG]: Running coremod plugin for SuperMartijn642's Core Lib Plugin \{com.supermartijn642.core.coremod.CoreModPlugin\} [16:25:50] [main/DEBUG]: Running coremod plugin SuperMartijn642's Core Lib Plugin [16:25:50] [main/DEBUG]: Coremod plugin class CoreModPlugin run successfully [16:25:50] [main/DEBUG]: Injecting coremod Controllable \{com.mrcrayfish.controllable.asm.ControllablePlugin\} class transformers [16:25:50] [main/DEBUG]: Injection complete [16:25:50] [main/DEBUG]: Running coremod plugin for Controllable \{com.mrcrayfish.controllable.asm.ControllablePlugin\} [16:25:50] [main/DEBUG]: Running coremod plugin Controllable [16:25:50] [main/DEBUG]: Coremod plugin class ControllablePlugin run successfully [16:25:50] [main/DEBUG]: Injecting coremod MalisisCorePlugin \{net.malisis.core.asm.MalisisCorePlugin\} class transformers [16:25:50] [main/DEBUG]: Injection complete [16:25:50] [main/DEBUG]: Running coremod plugin for MalisisCorePlugin \{net.malisis.core.asm.MalisisCorePlugin\} [16:25:50] [main/DEBUG]: Running coremod plugin MalisisCorePlugin [16:25:50] [main/DEBUG]: Coremod plugin class MalisisCorePlugin run successfully [16:25:50] [main/DEBUG]: Injecting coremod Moving Elevators Plugin \{com.supermartijn642.movingelevators.core.CoreMod\} class transformers [16:25:50] [main/DEBUG]: Injection complete [16:25:50] [main/DEBUG]: Running coremod plugin for Moving Elevators Plugin \{com.supermartijn642.movingelevators.core.CoreMod\} [16:25:50] [main/DEBUG]: Running coremod plugin Moving Elevators Plugin [16:25:50] [main/DEBUG]: Coremod plugin class CoreMod run successfully [16:25:50] [main/INFO]: Calling tweak class gg.essential.loader.stage0.EssentialSetupTweaker [16:25:50] [main/INFO]: Calling tweak class guichaguri.betterfps.tweaker.BetterFpsTweaker [16:25:50] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLDeobfTweaker [16:25:50] [main/DEBUG]: Validating minecraft [16:25:52] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:52] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:52] [main/INFO]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper [16:25:52] [main/INFO]: Loading tweak class name net.minecraftforge.fml.common.launcher.TerminalTweaker [16:25:52] [main/INFO]: Loading tweak class name org.spongepowered.asm.mixin.EnvironmentStateTweaker [16:25:52] [main/INFO]: Loading tweak class name gg.essential.asm.compat.betterfps.tweaker.BetterFpsWrappingTweaker [16:25:52] [main/INFO]: Calling tweak class net.minecraftforge.fml.common.launcher.TerminalTweaker [16:25:52] [main/INFO]: Calling tweak class org.spongepowered.asm.mixin.EnvironmentStateTweaker [16:25:52] [main/INFO]: Calling tweak class gg.essential.asm.compat.betterfps.tweaker.BetterFpsWrappingTweaker [16:25:52] [main/INFO]: [optifine.OptiFineForgeTweaker:dbg:56]: OptiFineForgeTweaker: getLaunchArguments [16:25:52] [main/WARN]: Reference map 'mixins.mixincompat.refmap.json' for mixins.mixincompat.json could not be read. If this is a development environment you can ignore this message [16:25:53] [main/INFO]: Starting Essential v1.3.2.3 (#6a2d13e09b) [stable] [16:25:54] [main/INFO]: Patching net.minecraft.client.renderer.EntityRenderer... (buq) [16:25:54] [main/INFO]: A re-entrant transformer 'guichaguri.betterfps.transformers.PatcherTransformer' was detected and will no longer process meta class data [16:25:55] [main/INFO]: Attempting: Injection of Run Particle Override into Entity.createRunningParticles [16:25:55] [main/INFO]: Searching for: Entity.createRunningParticles (func_174808_Z) [16:25:55] [main/INFO]: Found Method: Entity.createRunningParticles [16:25:55] [main/INFO]: Injecting: Run Particle Override [16:25:56] [main/INFO]: [team.chisel.ctm.client.asm.CTMTransformer:preTransform:230]: Transforming Class [net.minecraftforge.client.ForgeHooksClient], Method [getDamageModel] [16:25:56] [main/INFO]: [team.chisel.ctm.client.asm.CTMTransformer:finishTransform:242]: Transforming net.minecraftforge.client.ForgeHooksClient Finished. [16:25:56] [main/INFO]: [team.chisel.ctm.client.asm.CTMTransformer:preTransform:230]: Transforming Class [net.minecraft.client.renderer.texture.TextureMap], Method [registerSprite] [16:25:56] [main/INFO]: [team.chisel.ctm.client.asm.CTMTransformer:finishTransform:242]: Transforming net.minecraft.client.renderer.texture.TextureMap Finished. [16:25:57] [main/WARN]: Re-entrance detected during prepare phase, this will cause serious problems. org.spongepowered.asm.mixin.transformer.throwables.ReEntrantTransformerError: Re-entrance error.     at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:283) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:234) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:202) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.Proxy.transform(Proxy.java:72) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) [launchwrapper-1.12.jar:?]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424) [?:1.8.0_51]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357) [?:1.8.0_51]     at java.lang.Class.forName0(Native Method) ~[?:1.8.0_51]     at java.lang.Class.forName(Class.java:348) [?:1.8.0_51]     at com.unascribed.ears.common.agent.mini.asm.ClassWriter.getCommonSuperClass(ClassWriter.java:1017) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.SymbolTable.addMergedType(SymbolTable.java:1202) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.Frame.merge(Frame.java:1299) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.Frame.merge(Frame.java:1197) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.MethodWriter.computeAllFrames(MethodWriter.java:1610) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.MethodWriter.visitMaxs(MethodWriter.java:1546) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.tree.MethodNode.accept(MethodNode.java:769) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.tree.MethodNode.accept(MethodNode.java:649) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.asm.tree.ClassNode.accept(ClassNode.java:452) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.mini.MiniTransformer.transform(MiniTransformer.java:203) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.EarsAgent.transform(EarsAgent.java:43) [ears-forge-1.12-1.4.6.jar:?]     at com.unascribed.ears.common.agent.TransformerAdapter.transform(TransformerAdapter.java:12) [ears-forge-1.12-1.4.6.jar:?]     at net.minecraftforge.fml.common.asm.ASMTransformerWrapper$TransformerWrapper.transform(ASMTransformerWrapper.java:256) [ASMTransformerWrapper$TransformerWrapper.class:?]     at org.spongepowered.asm.service.mojang.LegacyTransformerHandle.transformClassBytes(LegacyTransformerHandle.java:80) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.service.mojang.MixinServiceLaunchWrapper.applyTransformers(MixinServiceLaunchWrapper.java:548) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.service.mojang.MixinServiceLaunchWrapper.getClassBytes(MixinServiceLaunchWrapper.java:514) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.service.mojang.MixinServiceLaunchWrapper.getClassNode(MixinServiceLaunchWrapper.java:592) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.ClassInfo.forName(ClassInfo.java:2005) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinInfo.getTargetClass(MixinInfo.java:1017) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinInfo.readTargetClasses(MixinInfo.java:1007) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinInfo.parseTargets(MixinInfo.java:895) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinConfig.prepareMixins(MixinConfig.java:867) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinConfig.prepare(MixinConfig.java:775) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinProcessor.prepareConfigs(MixinProcessor.java:539) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinProcessor.select(MixinProcessor.java:462) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinProcessor.checkSelect(MixinProcessor.java:438) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:290) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:234) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:202) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.Proxy.transform(Proxy.java:72) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) [launchwrapper-1.12.jar:?]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424) [?:1.8.0_51]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357) [?:1.8.0_51]     at java.lang.Class.forName0(Native Method) ~[?:1.8.0_51]     at java.lang.Class.forName(Class.java:348) [?:1.8.0_51]     at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?] [16:25:57] [main/WARN]: Error loading class: net/minecraft/client/renderer/entity/layers/LayerElytra (net.minecraftforge.fml.common.asm.ASMTransformerWrapper$TransformerException: Exception in class transformer com.unascribed.ears.asm.PlatformTransformerAdapter@7bd7c4cf from coremod Ears) [16:25:57] [main/WARN]: @Mixin target net.minecraft.client.renderer.entity.layers.LayerElytra was not found mixins.essential.json:client.renderer.entity.Mixin_DisableElytraRendering [16:25:59] [main/INFO]: Launching wrapped minecraft {net.minecraft.client.main.Main} [16:25:59] [main/INFO]: Patching net.minecraft.client.Minecraft... (bib) [16:25:59] [main/WARN]: Re-entrance detected, this will cause serious problems. org.spongepowered.asm.mixin.transformer.throwables.ReEntrantTransformerError: Re-entrance error.     at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:352) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:234) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:202) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.Proxy.transform(Proxy.java:72) [3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) [launchwrapper-1.12.jar:?]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424) [?:1.8.0_51]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357) [?:1.8.0_51]     at net.minecraft.client.main.Main.main(SourceFile:38) [Main.class:?]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51]     at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51]     at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?] [16:25:59] [main/ERROR]: Unable to launch java.lang.reflect.InvocationTargetException: null     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_51]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_51]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51]     at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51]     at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) [launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.Launch.main(Launch.java:28) [launchwrapper-1.12.jar:?] Caused by: java.lang.NoClassDefFoundError: net/minecraft/client/Minecraft     at net.minecraft.client.main.Main.main(SourceFile:38) ~[Main.class:?]     ... 6 more Caused by: java.lang.ClassNotFoundException: net.minecraft.client.Minecraft     at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:191) ~[launchwrapper-1.12.jar:?]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_51]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_51]     at net.minecraft.client.main.Main.main(SourceFile:38) ~[Main.class:?]     ... 6 more Caused by: org.spongepowered.asm.mixin.transformer.throwables.ReEntrantTransformerError: Re-entrance error.     at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:352) ~[3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:234) ~[3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:202) ~[3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at org.spongepowered.asm.mixin.transformer.Proxy.transform(Proxy.java:72) ~[3dSkinLayers-forge-mc1.12.2-1.2.0.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.runTransformers(LaunchClassLoader.java:279) ~[launchwrapper-1.12.jar:?]     at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:176) ~[launchwrapper-1.12.jar:?]     at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_51]     at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_51]     at net.minecraft.client.main.Main.main(SourceFile:38) ~[Main.class:?]     ... 6 more [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]: net.minecraftforge.fml.relauncher.FMLSecurityManager$ExitTrappedException [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraftforge.fml.relauncher.FMLSecurityManager.checkPermission(FMLSecurityManager.java:49) [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at java.lang.SecurityManager.checkExit(SecurityManager.java:761) [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at java.lang.Runtime.exit(Runtime.java:107) [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at java.lang.System.exit(System.java:971) [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraft.launchwrapper.Launch.launch(Launch.java:138) [16:25:59] [main/INFO]: [java.lang.ThreadGroup:uncaughtException:1052]:     at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
    • I downloaded Better MC BMC4, it didnt starts and say: "Error: java.lang.IllegalStateException: Config property is not linked yet" Exit-Code: -1   https://paste.ee/p/g7qO2
    • I am wanting to export my mod to a .zip file in IntelliJ version 2024.1 but cannot.   I am not sure what to do, the only options available to me are "Files or selection to HTML" and "Project to eclipse." A possible theory I have is that IntelliJ believes that my mod is a HTML file, though I am not sure whether I could change that or not. There is nothing I have found online about the missing zip option for exporting a file, so I am confused. I export a backup of my mod every time I add/edit something important, though I don't think I can do this currently. (I have tried to export as HTML though I did not think it would work).
  • Topics

×
×
  • Create New...

Important Information

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