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

1.16.1 | Mods being loaded as datapacks is preventing me from creating a world

EnderWarlock

By EnderWarlock
in Support & Bug Reports

 Share

Recommended Posts

EnderWarlock Tree Puncher

EnderWarlock

Posted
Posted

No matter how I install forge, or how many new instances I make, I cannot create a world. The following screen always appears;
 

Quote

 

Errors in currently selected datapacks prevented world from loading. You can either try to load only with vanilla datapack ("safe mode") or go back to title screen and fix it manually.

 

Safe Mode                Back to title screen

 

 

The safe mode button never works. I have my mods in a separate mods folder, but when I open up the datapacks screen from the world creation screen, all the mods are listed there.

 

I do not believe it generates a log when this happens, but please correct me if I am mistaken.

EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted
48 minutes ago, diesieben07 said:

That file is not even remotely close to being called "debug.log".

I am not certain if you meant to be rude, but it is incredibly frustrating when after I explained that I am uncertain what I am looking for, and then post the wrong thing, that you do not even attempt to be helpful and explain why I am incorrect. It is frustrating and does not help me report the bug properly.

EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted

All I was told was to post a debug log, and you never stated where that log was located. I did not know there there was a log folder, and was not informed of that. When I found the file I thought was correct, I posted it and was told that was "not remotely" correct, which can come off as rude, especially when not advised or informed as to how that was incorrect in that reply. I can see how what you said would have been enough for someone that is experienced in reporting bugs, but I have never needed to report a bug for Minecraft forge or mods before.

 

I explained in some of my replies that I do not know what I am looking for. Instead of helping me or explaining in a way that was not terse, you told me I was wrong and did not help explain beyond that fact.

 

At the bottom of my original post, I even stated that I didn't think it posted a log (I was thinking of crash logs, and it did not crash), which Implies that I did not even know what I was looking for, which I didn't. Telling me to post the debug with that fact and no explanation is, while precise, not helpful.

 

TL;DR Please explain more when you tell someone they are doing something wrong, as while you are correct to point out the error, you are not being helpful in not explaining further.

EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted (edited)

I cannot get it to start any world, so I have not had the opportunity to attempt to start an existing world. It happens everytime I try to start a new world tho.

 

 

6 minutes ago, diesieben07 said:

 

File names are completely unrelated to reporting bugs. If you don't know how file names work you need a course in computer basics.

 

Now it seems like you are intentionally being rude. Everybody makes mistakes, but that does not warrant questioning my intelligence like that.

Edited by EnderWarlock
EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted

I listed the mods and their versions below.

AppleSkin-mc1.16.1-forge-1.0.14

BetterMineshaftsForge-1.16.1-1.3

BiomesOPlenty-1.16.1-11.0.0.391-universal

Controlling-7.0.0.3

fortunate-2.8.1-MC-1.16.1

Lollipop-1.16.1-2.1.3

Mekanism-1.16.1-10.0.6.429

MekanismAdditions-1.16.1-10.0.6.429

MekanismGenerators-1.16.1-10.0.6.429

MekanismTools-1.16.1-10.0.6.429

Powah-1.16.1-2.1.3

preview_OptiFine_1.16.1_HD_U_G2_pre15

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Try removing fortunate

  • Like 1

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]

 

EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted

That worked. I feel like an absolute ninny with how simple that was to resolve. lol

 

I never encountered that kind of error before, and had removed some mods for different errors, so I did not think that it was still caused by a mod.

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

It was caused by a mod whose built-in datapack was broken

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]

 

EnderWarlock Tree Puncher

EnderWarlock

Posted
  • Author
Posted (edited)

Ah, I see. I did not know that mods had built in datapacks. I had been on 1.12.2 previously.

 

Also, I would like to apologize to diesieben07 for any frustration I have have caused them. In retrospect I was being impatient, as I had already spent a few hours trying to troubleshoot the problem on my own. You did nothing wrong and it was wrong of me to get frustrated with you.

Edited by EnderWarlock
Clarification
  • 1 month later...
  • 7 months later...

Join the conversation

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

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept