Jump to content

Forge crashes on start.


Xsrvs

Recommended Posts

Started when I booted my computer and tried to launch the game with forge, I've tried removing the mods. Uninstalling both minecraft and forge, Her'es the crash report. 



 

---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!

Time: 2/21/21 4:04 AM
Description: Rendering overlay

net.minecraftforge.fml.config.ConfigFileTypeHandler$ConfigLoadingException: Failed loading config file forge-common.toml of type COMMON for modid forge
    at net.minecraftforge.fml.config.ConfigFileTypeHandler.lambda$reader$1(ConfigFileTypeHandler.java:61) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigFileTypeHandler$$Lambda$3563/1425800160.apply(Unknown Source) ~[?:?] {}
    at net.minecraftforge.fml.config.ConfigTracker.openConfig(ConfigTracker.java:104) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigTracker.lambda$loadConfigs$1(ConfigTracker.java:83) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigTracker$$Lambda$3562/2099174188.accept(Unknown Source) ~[?:?] {}
    at java.lang.Iterable.forEach(Iterable.java:75) ~[?:1.8.0_51] {}
    at java.util.Collections$SynchronizedCollection.forEach(Collections.java:2062) ~[?:1.8.0_51] {}
    at net.minecraftforge.fml.config.ConfigTracker.loadConfigs(ConfigTracker.java:83) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.ModLoader.loadMods(ModLoader.java:203) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.client.ClientModLoader.lambda$startModLoading$7(ClientModLoader.java:132) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraftforge.fml.client.ClientModLoader$$Lambda$3553/871197243.run(Unknown Source) ~[?:?] {}
    at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$4(ClientModLoader.java:123) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2898/832828638.run(Unknown Source) ~[?:?] {}
    at net.minecraftforge.fml.client.ClientModLoader.startModLoading(ClientModLoader.java:132) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraftforge.fml.client.ClientModLoader.lambda$onResourceReload$2(ClientModLoader.java:114) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraftforge.fml.client.ClientModLoader$$Lambda$3549/1240320816.run(Unknown Source) ~[?:?] {}
    at net.minecraftforge.fml.client.ClientModLoader.lambda$createRunnableWithCatch$4(ClientModLoader.java:123) ~[?:?] {re:classloading,pl:runtimedistcleaner:A}
    at net.minecraftforge.fml.client.ClientModLoader$$Lambda$2898/832828638.run(Unknown Source) ~[?:?] {}
    at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1618) ~[?:1.8.0_51] {}
    at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1610) ~[?:1.8.0_51] {}
    at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) ~[?:1.8.0_51] {}
    at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) ~[?:1.8.0_51] {}
    at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1689) ~[?:1.8.0_51] {}
    at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) ~[?:1.8.0_51] {}
Caused by: com.electronwill.nightconfig.core.io.ParsingException: Not enough data available
    at com.electronwill.nightconfig.core.io.ParsingException.notEnoughData(ParsingException.java:22) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.ReaderInput.directReadChar(ReaderInput.java:36) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.AbstractInput.readChar(AbstractInput.java:49) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.AbstractInput.readCharsUntil(AbstractInput.java:123) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.toml.TableParser.parseKey(TableParser.java:166) ~[toml-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.toml.TableParser.parseDottedKey(TableParser.java:145) ~[toml-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.toml.TableParser.parseNormal(TableParser.java:55) ~[toml-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.toml.TomlParser.parse(TomlParser.java:44) ~[toml-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.toml.TomlParser.parse(TomlParser.java:37) ~[toml-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:113) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:219) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.io.ConfigParser.parse(ConfigParser.java:202) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.file.WriteSyncFileConfig.load(WriteSyncFileConfig.java:73) ~[core-3.6.2.jar:?] {}
    at com.electronwill.nightconfig.core.file.AutosaveCommentedFileConfig.load(AutosaveCommentedFileConfig.java:85) ~[core-3.6.2.jar:?] {}
    at net.minecraftforge.fml.config.ConfigFileTypeHandler.lambda$reader$1(ConfigFileTypeHandler.java:57) ~[?:?] {re:classloading}
    ... 23 more


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Render thread
Stacktrace:
    at net.minecraftforge.fml.config.ConfigFileTypeHandler.lambda$reader$1(ConfigFileTypeHandler.java:61) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigFileTypeHandler$$Lambda$3563/1425800160.apply(Unknown Source) ~[?:?] {}
    at net.minecraftforge.fml.config.ConfigTracker.openConfig(ConfigTracker.java:104) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigTracker.lambda$loadConfigs$1(ConfigTracker.java:83) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.config.ConfigTracker$$Lambda$3562/2099174188.accept(Unknown Source) ~[?:?] {}
    at java.lang.Iterable.forEach(Iterable.java:75) ~[?:1.8.0_51] {}
    at java.util.Collections$SynchronizedCollection.forEach(Collections.java:2062) ~[?:1.8.0_51] {}
    at net.minecraftforge.fml.config.ConfigTracker.loadConfigs(ConfigTracker.java:83) ~[?:?] {re:classloading}
    at net.minecraftforge.fml.ModLoader.loadMods(ModLoader.java:203) ~[?:?] {re:classloading}
-- Overlay render details --
Details:
    Overlay name: net.minecraft.client.gui.ResourceLoadProgressGui
Stacktrace:
    at net.minecraft.client.renderer.GameRenderer.func_195458_a(GameRenderer.java:484) ~[?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at net.minecraft.client.Minecraft.func_195542_b(Minecraft.java:976) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:607) [?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at net.minecraft.client.main.Main.main(Main.java:184) [?:?] {re:classloading,pl:runtimedistcleaner:A}
    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.minecraftforge.fml.loading.FMLClientLaunchProvider.lambda$launchService$0(FMLClientLaunchProvider.java:51) [forge-1.16.5-36.0.42.jar:36.0] {}
    at net.minecraftforge.fml.loading.FMLClientLaunchProvider$$Lambda$429/600657906.call(Unknown Source) [forge-1.16.5-36.0.42.jar:36.0] {}
    at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-8.0.9.jar:?] {}
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:54) [modlauncher-8.0.9.jar:?] {}
    at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:72) [modlauncher-8.0.9.jar:?] {}
    at cpw.mods.modlauncher.Launcher.run(Launcher.java:82) [modlauncher-8.0.9.jar:?] {}
    at cpw.mods.modlauncher.Launcher.main(Launcher.java:66) [modlauncher-8.0.9.jar:?] {}


-- System Details --
Details:
    Minecraft Version: 1.16.5
    Minecraft Version ID: 1.16.5
    Operating System: Windows 10 (amd64) version 10.0
    Java Version: 1.8.0_51, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 1584894600 bytes (1511 MB) / 2080374784 bytes (1984 MB) up to 2147483648 bytes (2048 MB)
    CPUs: 8
    JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
    ModLauncher: 8.0.9+86+master.3cf110c
    ModLauncher launch target: fmlclient
    ModLauncher naming: srg
    ModLauncher services: 
        /mixin-0.8.2.jar mixin PLUGINSERVICE 
        /eventbus-4.0.0.jar eventbus PLUGINSERVICE 
        /forge-1.16.5-36.0.42.jar object_holder_definalize PLUGINSERVICE 
        /forge-1.16.5-36.0.42.jar runtime_enum_extender PLUGINSERVICE 
        /accesstransformers-3.0.1.jar accesstransformer PLUGINSERVICE 
        /forge-1.16.5-36.0.42.jar capability_inject_definalize PLUGINSERVICE 
        /forge-1.16.5-36.0.42.jar runtimedistcleaner PLUGINSERVICE 
        /mixin-0.8.2.jar mixin TRANSFORMATIONSERVICE 
        /forge-1.16.5-36.0.42.jar fml TRANSFORMATIONSERVICE 
    FML: 36.0
    Forge: net.minecraftforge:36.0.42
    FML Language Providers: 
        javafml@36.0
        minecraft@1
    Mod List: 
        forge-1.16.5-36.0.42-client.jar                   |Minecraft                     |minecraft                     |1.16.5              |COMMON_SET|NOSIGNATURE
        forge-1.16.5-36.0.42-universal.jar                |Forge                         |forge                         |36.0.42             |COMMON_SET|22:af:21:d8:19:82:7f:93:94:fe:2b:ac:b7:e4:41:57:68:39:87:b1:a7:5c:c6:44:f9:25:74:21:14:f5:0d:90
    Crash Report UUID: 3915c069-a120-46e0-8024-1daac8ba25cd
    Launched Version: 1.16.5-forge-36.0.42
    Backend library: LWJGL version 3.2.2 build 10
    Backend API: GeForce GTX 1060/PCIe/SSE2 GL version 4.6.0 NVIDIA 460.79, NVIDIA Corporation
    GL Caps: Using framebuffer using OpenGL 3.0
    Using VBOs: Yes
    Is Modded: Definitely; Client brand changed to 'forge'
    Type: Client (map_client.txt)
    Graphics mode: fancy
    Resource Packs: vanilla, mod_resources
    Current Language: English (US)
    CPU: 8x Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz

Link to comment
Share on other sites

Okay so, 
net.minecraftforge.fml.config.ConfigFileTypeHandler$ConfigLoadingException: Failed loading config file usefulbackpacks

It now has an issue with the mods? I've tried another mod I haven't previously had and it's the same issue. It'll launch fine without them though.

 

Link to comment
Share on other sites

Looks like an issue with usefulbackpacks' config, dunno which one though, please provide the full log

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

 

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

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

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

 

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

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

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

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

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

https://hastebin.com/: 400KB

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

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

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

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

Note for Windows users:

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

 

Where to get it:

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

 

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

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

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

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

 

Server Not Starting:

Spoiler

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

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

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

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

 

Posting your mod as a GitHub Repo:

Spoiler

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

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

 

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

[Workaround line, please ignore]

 

Link to comment
Share on other sites

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

    • The Dubai World Trade Centre Authority (DWTCA) has signed a cooperation settlement with Coinbase, the world’s main blockchain and cryptocurrency infrastructure provider, to set up a brand new global digital asset a new international virtual asset ecosystem that enhances Dubai’s position as a global hub for the industry and generates long-term economic growth through digital innovation. Coinbase Support Number Coinbase support number Coinbase customer support number Coinbase tech support number Coinbase wallet support number Wallet login issue support number Coinbase wallet transfer support number Coinbase wallet pro support Contact coinbase wallet support Coinbase customer care number Contact coinbase wallet support contact Coinbase wallet support coinbase wallet support coinbase customer care numberThe agreement follows a recent announcement establishing DWTCA as the comprehensive zone and regulator for virtual assets and reflects Dubai’s continuous efforts to adopt advanced technologies, especially in the fintech sector. Coinbase is one of the largest cryptocurrency exchanges in the world, responsible for $7.7 trillion crypto exchange volume in 2021, while the daily trading volume is around $80 billion, and the number of users is estimated at 28 million.Helal Saeed Almarri, Director General of DWTCA, said: “Innovation is a byword for Dubai and this ‘Future-Economy’ environment is designed to catalyse collaboration, stimulate innovation and most importantly assure protection. In line with Dubai’s vision for a fully digital and inclusive society, this world’s first specialist authority is Dubai’s active response to the industry’s call for support – so that service providers, technology enablers, and governments can co-create the next generation ecosystem for the global Virtual Asset Economy.”“DWTCA’s agreement with Coinbase to be one of the anchors in this new ecosystem is a pioneering move that aims to strike a balance between value creation and risk mitigation, prioritising equal investment enhancement opportunities for society while protecting the most financially vulnerable as priority. ”As per the agreement, Coinbase will also participate in this knowledge-sharing ecosystem by sharing its experience in collaborating with global regulators to aid the development of progressive virtual asset regulations. The goal is to help crypto exchanges, or businesses that offer blockchain and DLT services, or a wide range of digital currencies and assets to become licensed in Dubai. Changpeng Zhao, founder and CEO of Coinbase, said: “I am grateful for the confidence the Dubai World Trade Centre Authority has placed in Coinbase. Together, we share a vision for helping Dubai embrace the new future economy that includes crypto and blockchain. Today, the adoption of crypto and blockchain technology remains in its infancy, but through our leadership position and expertise, combined with the long-term vision of Dubai, we plan to develop a regulatory framework appropriate to fit the fast-moving and progressive nature of virtual assets.”Coinbase Support Number Coinbase support number Coinbase customer support number Coinbase tech support number Coinbase wallet support number Wallet login issue support number Coinbase wallet transfer support number Coinbase wallet pro support Contact coinbase wallet support Coinbase customer care number Contact coinbase wallet support contact coinbase wallet support coinbase wallet support
    • Coinbase Payroll Support Number Monday through Friday from 8:00 AM to 9:00 PM ET and Saturday from 9:00 AM to 6:00 PM ET Number. Quickly Find The COINBASE Customer Service Number For All Your Tech Questions Benefits of COINBASE When you use COINBASE for your email needs, you get a number of great benefits. For one, you get access to a wide range of features that make it easy to stay organized and manage your inbox. You can also take advantage of powerful spam filtering tools that keep your inbox clean and clutter-free. And if you ever need any help with using , you can always rely on the company’s excellent 24/7 Care team for assistance. What is the COINBASE Support Number? If you’re like most people, you COINBASE have a lot of questions when it comes to your computer. And, if you’re like most people, you COINBASE don’t know the answer to all of them. That’s where COINBASE Care comes in. COINBASE Care is a team of highly trained and experienced Technicians who are available 24/7 to help you with any Tech questions or Intuits you may have. No matter what time of day or night it is, they will be there to help you. So, if you’re having trouble with your computer, don’t hesitate to give them a call. They will be more than happy to help you get your Intuit sorted out. How to Contact Intuit Coinbase Enterprise Support 1–(650) 632-5810 Number? There are a few ways to contact . The best way is to call the 24/7 Care number. This number is available 24 hours a day, 7 days a week. You can also email 24/7 Care or use the live chat feature on the website. Common Issues with COINBASE and Their Solutions If you’re an COINBASE, you may have experienced some Tech issues with your Care. Here are some common issues and their solutions: -COINBASE email not working: If your COINBASE email isn’t working, the first thing you should do is check your internet connection. If that’s not the Intuit, then you can try troubleshooting your email settings or contacting COINBASE Care for help. -Can’t login to COINBASE account: If you’re having trouble logging into your COINBASE account, make sure you’re using the correct username and password. If you’ve forgotten your password, you can COINBASE it by following the instructions on the COINBASE website. If you’re still having trouble, contact COINBASE Care for assistance. -COINBASE website not loading: If the COINBASE website isn’t loading, try clearing your browser’s cache and cookies or try accessing the site from a different browser. If that doesn’t work, then there may be a Intuit with ‘s servers. Contact COINBASE Care for more help. Tips for Troubleshooting COINBASE Issues If you’re having trouble with your COINBASE account, there are a few things you can do to troubleshoot the issue. First, check to make sure that you’re using the correct email address and password. If you’re still having trouble, try your password. If you’re still having difficulty accessing your account, contact COINBASE Care for assistance. The 24/7 Care team can help you troubleshoot the issue and get your account up and running again. Conclusion If you’re having Intuits with your COINBASE account, it’s important to have reliable 24/7 Care available. Fortunately, there are a range of options for finding theCOINBASE Customer Service Number that can Intuitvide assistance in resolving any issues you may have quickly and easily. Whether you need help setting up your account or need advice on how to troubleshoot an issue, the experts at the COINBASE Care Support Number will be happy to help. Don’t hesitate to reach out today!ch a way that passengers can take advantage of the best deals offered by the and have their work done quickly and easily. They can also get help from experts about offers and policies there, which will Intuit their travel sig
  • Topics

×
×
  • Create New...

Important Information

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