Modded Server Crashing, Need Help

  • As the title states, I am trying to set up a modded server and it continues to crash. The mods in question are for the Dark Souls Simulator mod pack on CurseForge. I have installed all of the mods with the right versions and upon starting the server I continue to get a crash. I dug around in the logs to try and find the issue and the last mod loaded before the crash was Ice and Fire: Dragons. I deleted the mod and the server managed to start, but crashed after about 15 seconds. I repeated this process with BYG (Oh The Biomes You'll Go) and Spartan Weaponry. The crashes continued and seemed to be different in nature with some crash logs being entirely red and some successfully loading other parts of the mod list. I reinstalled all of the mods and ran the server again to get this crash log: https://mclo.gs/42NZLvC


    If it would be helpful to attach logs of the other crash reports I can probably get those as well. Any help would be appreciated as I've tried all that I can think of and I really want to play this mod pack with my friend.

  • That's not the crash log. That is the server log. Share your crash log by going here: https://aternos.org/files/cras…01-30_20.17.18-server.txt


    Also, are you sure you deleted the Ice and Fire: Dragons mod? In the log, there are hundreds of warnings about the Ice and Fire mod.

    Maybe I was unclear, the crash log I posted was with all of the mods in the mod pack installed, I only described some of the steps I took trying to solve it, which is why I mentioned deleting ice and fire.


    I have a theory that the version of forge is incompatible, as the mod pack runs on 36.1.4. Is it possible to run this version of forge on Aternos? I only see 36.2 and up for MC 1.16.5.


    Here is the crash log, I apologize for the mixup. https://aternos.org/files/cras…01-30_20.53.35-server.txt

  • Maybe I was unclear, the crash log I posted was with all of the mods in the mod pack installed, I only described some of the steps I took trying to solve it, which is why I mentioned deleting ice and fire.


    I have a theory that the version of forge is incompatible, as the mod pack runs on 36.1.4. Is it possible to run this version of forge on Aternos? I only see 36.2 and up for MC 1.16.5.


    Here is the crash log, I apologize for the mixup. https://aternos.org/files/cras…01-30_20.53.35-server.txt

    Can you share your crash-report properly:

    1) Open your crash-report on Aternos by clicking on the link : https://aternos.org/files/cras…01-27_12.14.16-server.txt

    2)Copy and paste the content of the file to https://mclo.gs/

    3)Send the link here

  • -- Entity being ticked --
    55Details:
    56Entity Type: minecraft:skeleton (net.minecraft.entity.monster.SkeletonEntity)
    57Entity ID: 30
    58Entity Name: Skeleton
    59Entity's Exact location: 152.55, 74.00, -67.25

    You need to remove the Ticking entity as the server is crashing due to it. You can run /kill @e in the console to remove it or, if you can't do it, download the world and kill the entity in singleplayer then upload the world again

  • -- Entity being ticked --
    55Details:
    56Entity Type: minecraft:skeleton (net.minecraft.entity.monster.SkeletonEntity)
    57Entity ID: 30
    58Entity Name: Skeleton
    59Entity's Exact location: 152.55, 74.00, -67.25

    You need to remove the Ticking entity as the server is crashing due to it. You can run /kill @e in the console to remove it or, if you can't do it, download the world and kill the entity in singleplayer then upload the world again

    Ok so as the server is running I type /kill 152.55 74.00 -67.25?

    And if its a single killable entity, why does wiping and generating a new world not solve the issue? Just curious to know, really.

  • Ok so as the server is running I type /kill 152.55 74.00 -67.25?

    And if its a single killable entity, why does wiping and generating a new world not solve the issue? Just curious to know, really.

    Download the world if you cannot access the console while it's running, then type /kill @e[type=skeleton] or simply /kill @e.


    /kill @e[type=skeleton] --> only kills all skeletons

    /kill @e --> kills every single entity that exists in the world

    Edited 2 times, last by ZXVoidx ().

  • Download the world if you cannot access the console while it's running, then type /kill @e[type=skeleton].


    Regenerating the world(s) can solve the issue if that isn't a problem to you.

    I tried wiping the world and generating a new one as this server is completely new, and it did not work. Regardless I am going to try killing the entity and running the world again to maybe prevent a new ticking entity from spawning.

  • I tried wiping the world and generating a new one as this server is completely new, and it did not work. Regardless I am going to try killing the entity and running the world again to maybe prevent a new ticking entity from spawning.

    Sorry, I didn’t know wiping the world wouldn’t fix that.

  • Sorry, I didn’t know wiping the world wouldn’t fix that.

    No worries. I recreated the world in single player and killed all skeletons anyway. It did not seem to fix it. Looking at the new crash report, it appears to be creating more ticking entities. I think the issue lies in the mismatch of forge versions. On the modpack page, a comment says that 36.1.4 is the exact necessary version of forge, so my guess is that with Aternos running 36.2.23, ice and fire is not loading properly.

  • No worries. I recreated the world in single player and killed all skeletons anyway. It did not seem to fix it. Looking at the new crash report, it appears to be creating more ticking entities. I think the issue lies in the mismatch of forge versions. On the modpack page, a comment says that 36.1.4 is the exact necessary version of forge, so my guess is that with Aternos running 36.2.23, ice and fire is not loading properly.

    Can you share the latest crash-report

  • Quote from NipplSalad

    No worries. I recreated the world in single player and killed all skeletons anyway. It did not seem to fix it. Looking at the new crash report, it appears to be creating more ticking entities. I think the issue lies in the mismatch of forge versions. On the modpack page, a comment says that 36.1.4 is the exact necessary version of forge, so my guess is that with Aternos running 36.2.23, ice and fire is not loading properly.


    Does the issue persist if you remove the Ice and Fire mod?

  • -- Entity being ticked --
    55Details:
    56Entity Type: minecraft:skeleton (net.minecraft.entity.monster.SkeletonEntity)
    57Entity ID: 4
    58Entity Name: Skeleton
    59Entity's Exact location: 30.50, 43.00, 96.50
    60Entity's Block location: World: (30,43,96), Chunk: (at 14,2,0 in 1,6; contains blocks 16,0,96 to 31,255,111), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
    61Entity's Momentum: 0.00, -0.08, 0.00
    62Entity's Passengers: []
    63Entity's Vehicle: ~~ERROR~~ NullPointerException: null


    Use /kill @e this time. If it doesn’t work, make sure you are killing it in the overworld since the skeleton is in the overworld.


    Also, the ticking entity is crashing the server because it is a corrupted mob/entity that is in the game data files somewhere.

  • -- Entity being ticked --
    55Details:
    56Entity Type: minecraft:skeleton (net.minecraft.entity.monster.SkeletonEntity)
    57Entity ID: 4
    58Entity Name: Skeleton
    59Entity's Exact location: 30.50, 43.00, 96.50
    60Entity's Block location: World: (30,43,96), Chunk: (at 14,2,0 in 1,6; contains blocks 16,0,96 to 31,255,111), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
    61Entity's Momentum: 0.00, -0.08, 0.00
    62Entity's Passengers: []
    63Entity's Vehicle: ~~ERROR~~ NullPointerException: null


    Use /kill @e this time. If it doesn’t work, make sure you are killing it in the overworld since the skeleton is in the overworld.


    Also, the ticking entity is crashing the server because it is a corrupted mob/entity that is in the game data files somewhere.

    As regenerating the world didn't work even the kill command won't work

    Does the issue persist if you remove the Ice and Fire mod?

    I don't think the issue is with ice and fire as nowhere in the crash-report I see an issue with it

  • -- Entity being ticked --
    55Details:
    56Entity Type: minecraft:skeleton (net.minecraft.entity.monster.SkeletonEntity)
    57Entity ID: 4
    58Entity Name: Skeleton
    59Entity's Exact location: 30.50, 43.00, 96.50
    60Entity's Block location: World: (30,43,96), Chunk: (at 14,2,0 in 1,6; contains blocks 16,0,96 to 31,255,111), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
    61Entity's Momentum: 0.00, -0.08, 0.00
    62Entity's Passengers: []
    63Entity's Vehicle: ~~ERROR~~ NullPointerException: null


    Use /kill @e this time. If it doesn’t work, make sure you are killing it in the overworld since the skeleton is in the overworld.


    Also, the ticking entity is crashing the server because it is a corrupted mob/entity that is in the game data files somewhere.

    Killing all entities seems to have worked, I started the server after reuploading the world and it stayed up for the entire 5 minutes or so. However, both my friend and I were unable to connect.

    I have not removed the performant mod yet. My guess is that the forge mismatch is causing the connection issue but I don't know for sure. I am told that an existing connection was closed by the remote host.