Jump to content

Crashing forge server - 1.20.1; 47.2.0


Recommended Posts

Hello,
I really don't like resorting to help on the forum, because you are certainly burdened by a lot of people having similiar issues, but after many attempts to fix the error,
I have no choice. We have a private Minecraft server, version 1.20.1, which has around 230 mods. Crashes have been happening more and more recently. The crash I put in
the PasteBin below is the last one that happened.

I would be really grateful to anyone who would be willing to help me and preferably if he could explain to me some of the main points by which he recognized the problem.
I would like to be more self-sufficient in this regard in the future.

Thank you so much in advance and have a nice day!

Crash log: https://pastebin.com/vqEHqqrt

Link to comment
Share on other sites

3 minutes ago, TileEntity said:

Backup the world and make a test without storagenetwork

Hi, i appreciate the answer.

I would love to do that, but we have active players with all their belongings in SSN. Also this mod is really handy and they would be mad if we removed it.

Are you really certain that SSN is causing this? It would require lots of work to test it and SSN was not really an issue before we removed Fast Suite. Can
it be related somehow? I will provide you with log before removing FS.

PasteBin: https://pastebin.com/Y5EpLpNe (crash before removing Fast Suite, which I suspected to be a problem from some crash before)

Link to comment
Share on other sites

5 hours ago, TileEntity said:

Is there a change if you set max-tick-time to -1 in the server.properties?

So yeah, there is a change. Its even worse :(.

So far I have discovered that server is eating really weird amount of RAM. 32 GB is allocated and when we had one online player, 22 GB was used.

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

    • Made a block, copies exactly the soul campfire. But when I start Minecraft, it starts, and right before it goes into full screen, it errors out. That's when I get 2 of these: Caused by: java.lang.IllegalArgumentException: Cannot get property BooleanProperty{name=lit, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in Block{minecraft:air} And 2 of these: Caused by: java.lang.NullPointerException: Registry Object not present: revive:block_campfire   Thanks!
    • Here is a tutorial; this is what I used. 1.20 Minecraft Forge Modding Tutorial - Packets
    • Corrected item registration code: (for the ModItems class) public static final RegistryObject<Item> LEMON_JUICE_BOTTLE = ITEMS.register("lemon_juice_bottle", () -> new HoneyBottleItem(new Item.Properties().stacksTo(1) .food((new FoodProperties.Builder()).nutrition(3).saturationMod(0.25F) .effect(() -> new MobEffectInstance(MobEffects.DAMAGE_RESISTANCE, 1500), 0.5f).build())));
    • Apologies for the late reply. You'll need to register the item in ModItems; if you're following those tutorials, that's the only place you should ever register items. Otherwise, the mod will fail to register them properly and you'll get all sorts of interesting errors. Looking back at the code snipped I posted, I think that actually has some errors. I'm adding a lemon juice bottle to my mod just to ensure that it works correctly, and I will reply when I have solved the problems.
    • I might have an idea why your original method was causing so much trouble. See this while loop? You're only incrementing the number of blocks you've corrupted if you find one that you can corrupt. What happens if you can't find any? The while loop will run forever (a long time). This could happen if, for instance, the feature generates inside a vein of blocks that aren't marked as STONE_ABERRANTABLE. There are two alternate strategies I'd recommend to fix this.  First, you could simply increment numBlockCorrupted regardless of whether you've actually corrupted the block. This is the simplest and quickest way, and it should ensure that the loop runs no more than numBlocksToCorrupt times.  Alternatively, you could add a "kill switch" that keeps track of how many times the loop runs, and then ends it after a certain limit of your choosing. That could look something like this:  // Keeps track of how many blocks have been checked so far. int numBlocksChecked = 0; // Check up to twice as many blocks as you actually want to corrupt. // This is a good compromise between speed and actually getting the number of blocks // that you want to corrupt. int numBlocksToCheck = numBlocksToCorrupt * 2; // Modified the while loop condition to end after a certain number of blocks are checked. while (numBlocksCorrupted < numBlocksToCorrupt && numBlocksChecked < numBlocksToCheck) {                 // Generate a random position within the area, using the offset origin                 BlockPos randomPos = offsetOrigin.offset(                         ctx.random().nextInt(2 * areaSizeX + 1) - areaSizeX, // between -areaSize and areaSize                         ctx.random().nextInt(2 * areaSizeY + 1) - areaSizeY,                         ctx.random().nextInt(2 * areaSizeZ + 1) - areaSizeZ                 );                 // If the block at the random position is in the IS_ORE_ABERRANTABLE tag, replace it                 if (world.getBlockState(randomPos).is(ModBlockTags.STONE_ABERRANTABLE)) {                     world.setBlock(randomPos, surroundingBlockState, 2);                     numBlocksCorrupted++;                 } // Increment the number of blocks that you've checked. numBlocksChecked++;             } Let me know if you're still running into lag problems or are confused by my explanation.
  • Topics

×
×
  • Create New...

Important Information

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