Jump to content

Dedicated 1.14.4 crash


Silentdarkness12

Recommended Posts

I've run into a rather peculiar crash on dedicated server and I can't figure out what exactly is making this happen.

 

Spoiler


Time: 9/15/19 11:01 AM
Description: Exception in server tick loop

net.minecraftforge.fml.LoadingFailedException: null
    at net.minecraftforge.fml.ModLoader.dispatchAndHandleError(ModLoader.java:198) ~[?:?] {}
    at net.minecraftforge.fml.ModLoader.gatherAndInitializeMods(ModLoader.java:180) ~[?:?] {}
    at net.minecraftforge.fml.server.ServerModLoader.begin(ServerModLoader.java:45) ~[?:?] {}
    at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:121) ~[?:?] {pl:accesstransformer:B}
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:598) [?:?] {pl:accesstransformer:B,pl:runtimedistcleaner:A}
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_221] {}


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

-- System Details --
Details:
    Minecraft Version: 1.14.4
    Minecraft Version ID: 1.14.4
    Operating System: Windows 10 (amd64) version 10.0
    Java Version: 1.8.0_221, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 3770625752 bytes (3595 MB) / 5693243392 bytes (5429 MB) up to 6569328640 bytes (6265 MB)
    CPUs: 8
    JVM Flags: 2 total; -Xms4024M -Xmx7048M
    ModLauncher: 3.2.0+60+b86c1d4
    ModLauncher launch target: fmlserver
    ModLauncher naming: srg
    ModLauncher services: 
        /eventbus-1.0.0-service.jar eventbus PLUGINSERVICE 
        /forge-1.14.4-28.1.1.jar object_holder_definalize PLUGINSERVICE 
        /forge-1.14.4-28.1.1.jar runtime_enum_extender PLUGINSERVICE 
        /accesstransformers-1.0.0-shadowed.jar accesstransformer PLUGINSERVICE 
        /forge-1.14.4-28.1.1.jar capability_inject_definalize PLUGINSERVICE 
        /forge-1.14.4-28.1.1.jar runtimedistcleaner PLUGINSERVICE 
        /forge-1.14.4-28.1.1.jar fml TRANSFORMATIONSERVICE 
    FML: 28.1
    Forge: net.minecraftforge:28.1.1
    FML Language Providers: 
        [email protected]
        minecraft@1
    Mod List: 
        anviltweaks-1.4.jar Anvil Tweaks {[email protected] CREATE_REGISTRIES}
        betteranimalsplus-1.14.4-7.1.2.jar Better Animals Plus {[email protected] CREATE_REGISTRIES}
        BiomesOPlenty-1.14.4-9.0.0.252-universal.jar Biomes O' Plenty {[email protected] CREATE_REGISTRIES}
        C.O.M.B.A.T.-1.14.4-0.20.5.jar C.O.M.B.A.T. {[email protected] ERROR}
        Charm-1.14.4-1.3.4.jar Charm {[email protected] CREATE_REGISTRIES}
        corail_pillar-4.5.3-1.14.4.jar Corail Pillar {[email protected] CREATE_REGISTRIES}
        corail_pillar_extension_biomesoplenty-4.2.0-1.14.4.jar Corail Pillar - Biomes O'Plenty Extension {[email protected] CREATE_REGISTRIES}
        corpse-1.14.4-1.0.2.jar Corpse {[email protected] CREATE_REGISTRIES}
        Craftable+Saddles+[1.14]-1.3.jar Craftable Saddles {[email protected] CREATE_REGISTRIES}
        curioofundying-FORGE-1.14.4-2.0-beta2.jar Curio of Undying {[email protected] CREATE_REGISTRIES}
        curios-FORGE-1.14.4-1.0.jar Curios API {[email protected] CREATE_REGISTRIES}
        Dirt2Path-1.0.0.jar Dirt2Path {[email protected] CREATE_REGISTRIES}
        DoggyTalents-1.14.4-1.15.1.7-universal.jar Doggy Talents {[email protected] CREATE_REGISTRIES}
        DungeonCrawl-1.14.4-1.3.0.jar Dungeon Crawl {[email protected] CREATE_REGISTRIES}
        EnigmaticLegacy-1.2.2.jar Enigmatic Legacy {[email protected] CREATE_REGISTRIES}
        extcaves-1.1.jar Extended Caves {[email protected] CREATE_REGISTRIES}
        FastFurnace-1.14.4-2.2.0.jar FastFurnace {[email protected] CREATE_REGISTRIES}
        FastWorkbench-1.14.4-2.1.1.jar FastWorkbench {[email protected] CREATE_REGISTRIES}
        followingvillagers-1.14.4-1.2.0.jar Following Villagers {[email protected] CREATE_REGISTRIES}
        FriendlyFire-1.14.4-3.0.1.jar FriendlyFire {[email protected] CREATE_REGISTRIES}
        furniture-7.0.0-pre8-1.14.4.jar MrCrayfish's Furniture Mod {[email protected] CREATE_REGISTRIES}
        GoodSkeletonsDontStrafe-v1.1.1-1.14.4.jar Good Skeletons Don't Strafe {[email protected] CREATE_REGISTRIES}
        HardcoreRevival_1.14.4-3.0.9.jar Hardcore Revival {[email protected] CREATE_REGISTRIES}
        jei-1.14.4-6.0.0.11.jar Just Enough Items {[email protected] CREATE_REGISTRIES}
        metalbarrels-1.3c.jar Metal Barrels {[email protected] CREATE_REGISTRIES}
        Mine+and+Decoration-1.0.5.5.jar Mine & Decoration {[email protected] CREATE_REGISTRIES}
        Mine+and+Slash-1.14.4-2.7.1.jar Mine and Slash {[email protected] CREATE_REGISTRIES}
        Mine+and+Slash+-+Expansion-1.3.1.27.jar Mine & Slash Expansion {[email protected] CREATE_REGISTRIES}
        petcollars-1.1.jar Pet Collars {[email protected] CREATE_REGISTRIES}
        Placebo-1.14.4-2.2.1.jar Placebo {[email protected] CREATE_REGISTRIES}
        portality-1.14.4-2.0.0-5f9c6a1.jar Portality {portality@NONE CREATE_REGISTRIES}
        reap-1.10.1.jar Reap Mod {[email protected] CREATE_REGISTRIES}
        recycler-1.0.0.jar Recycler {[email protected] CREATE_REGISTRIES}
        resynth-3.0.0.jar Resynth {[email protected] CREATE_REGISTRIES}
        rsgauges-1.14.4-1.1.8-b2.jar Redstone Gauges and Switches {[email protected] CREATE_REGISTRIES}
        ruins-1.14.4.1.jar Ruins {[email protected] CREATE_REGISTRIES}
        SilentLib-1.14.4-4.4.0+44.jar Silent Lib {[email protected]+44 CREATE_REGISTRIES}
        simplefarming-1.14.4-1.1.4c.jar Simple Farming {[email protected] CREATE_REGISTRIES}
        spiketraps-1.0.jar Spike Traps {[email protected] CREATE_REGISTRIES}
        StorageDrawers-1.14.4-6.0.4.jar Storage Drawers {[email protected] CREATE_REGISTRIES}
        timedilationmod-1.1.jar Time Dilation {[email protected] CREATE_REGISTRIES}
        titanium-1.14.4-2.2.0-d9775a7.jar Titanium {[email protected] CREATE_REGISTRIES}
        ToolBelt-1.14.4-1.11.1.jar Tool Belt {[email protected] CREATE_REGISTRIES}
        TorchBandolier-1.14.4-1.3.1+6.jar Torch Bandolier {[email protected]+6 CREATE_REGISTRIES}
        travel_bag-1.0.5-1.14.4.jar Travel Bag {[email protected] CREATE_REGISTRIES}
        wild_netherwart-1.14.4-v3.0.jar Wild Netherwart {[email protected] CREATE_REGISTRIES}
        XaerosWorldMap_1.4.10.1_Forge_1.14.4.jar Xaero's World Map {[email protected] CREATE_REGISTRIES}
        XL-Food-Mod-1.14.4-2.1.0.jar XL Food Mod {[email protected] CREATE_REGISTRIES}
        forge-1.14.4-28.1.1-universal.jar Forge {[email protected] CREATE_REGISTRIES}
        forge-1.14.4-28.1.1-server.jar Minecraft {[email protected] CREATE_REGISTRIES}
    Data Packs: 
    Is Modded: Definitely; Server brand changed to 'forge'
    Type: Dedicated Server (map_server.txt)

Logs attatched, crash report in spoiler. I'm at a dead end on what exactly to do here.

debug.log latest.log

Link to comment
Share on other sites

Remove FastFurnace

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

New log please?

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

Combat is broken and cannot run on a server.

MMORPG may be the mod causing the crash

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.



×
×
  • Create New...

Important Information

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