Jump to content

Recommended Posts

Posted

Hello.


My 1.19 server crashes at launch and multiple mods are concerned, that's why I am here. They all have the same issue : problem during the common_setup phase...
Is it a mutual problem ? What can I do to fix it ?
After 6 minecraft :andesite I REMOVED SOME LONG PART OF THE LOG BECAUSE IT CRASHED THE WEBSITE.
Log

  Reveal hidden contents

 

Posted
  On 8/14/2022 at 11:55 AM, diesieben07 said:

It looks like it from the crash report.

Expand  

sadly I removed it and it didn't change. The problem that I have is that Quark, Oh the Biomes You'll Go were fine before. I didn't update them. But now they are in the crash report. I can't tell which one causes it among nature's aura, occultism, etc...

Posted
java.lang.NoSuchMethodError: 'net.minecraft.world.item.RecordItem net.mehvahdjukaar.moonlight.api.platform.PlatformHelper.newMusicDisc(int, java.util.function.Supplier, net.minecraft.world.item.Item$Properties)'
        at TRANSFORMER/supplementaries@1.19-2.0.13/net.mehvahdjukaar.supplementaries.reg.ModRegistry.lambda$static$168(ModRegistry.java:1001)
        at TRANSFORMER/forge@41.1.0/net.minecraftforge.registries.DeferredRegister.lambda$addEntries$1(DeferredRegister.java:388)

Looks like an issue with either supplementaries or the moonlight mod.

You seem to have the latest versions of these mods for 1.19 - double check? Then contact the mod author.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted

Your other errors including the problem you had with evilcraft may just be a consequence of this? They are all missing registry entries at a later stage in the mod loading.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted
  On 8/14/2022 at 12:52 PM, warjort said:
java.lang.NoSuchMethodError: 'net.minecraft.world.item.RecordItem net.mehvahdjukaar.moonlight.api.platform.PlatformHelper.newMusicDisc(int, java.util.function.Supplier, net.minecraft.world.item.Item$Properties)'
        at TRANSFORMER/supplementaries@1.19-2.0.13/net.mehvahdjukaar.supplementaries.reg.ModRegistry.lambda$static$168(ModRegistry.java:1001)
        at TRANSFORMER/forge@41.1.0/net.minecraftforge.registries.DeferredRegister.lambda$addEntries$1(DeferredRegister.java:388)

Looks like an issue with either supplementaries or the moonlight mod.

You seem to have the latest versions of these mods for 1.19 - double check? Then contact the mod author.

Expand  

actually, moonlight was recently updated, and the issue might come from that update. Could also check for an older version of supplementaries. Because yes, both of them are up to date.

Posted

The way music disks got registered changed in either 1.19.1 or 1.19.2 (can't remember) so it might be the compatibility is marked wrongly for one of these mods.

Like I said, the mod author would know more about this.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted
  On 8/14/2022 at 12:54 PM, warjort said:

Your other errors including the problem you had with evilcraft may just be a consequence of this? They are all missing registry entries at a later stage in the mod loading.

Expand  

yeah, has to be this. Mods that had no issue started having issues for no apparent reasons.
I am currently downgrading the mods to the latest version before the one I had.

Posted
  On 8/14/2022 at 12:58 PM, warjort said:

The way music disks got registered changed in either 1.19.1 or 1.19.2 (can't remember) so it might be the compatibility is marked wrongly for one of these mods.

Like I said, the mod author would know more about this.

Expand  

music disks ? I don't see a such mod...
Also downgrading supplementaries and moonlight did not solve it.
Here is the updated log : https://mega.nz/file/NY5TiJya#GZXmz4n1A5Yo8c39z_GJUiJVKzDRlf9UWqeFdybsp2c

Posted

Creating music disks is the missing method in the moonlight mod

  Quote

net.minecraft.world.item.RecordItem net.mehvahdjukaar.moonlight.api.platform.PlatformHelper.newMusicDisc

Expand  

:

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted

Your error now is something about evilcraft:werewolf not being a valid profession

  Quote

[14Aug2022 15:01:49.316] [main/ERROR] [net.minecraft.server.Main/FATAL]: Failed to start the minecraft server
net.minecraftforge.fml.LoadingFailedException: Loading errors encountered: [
        Oh The Biomes You'll Go (byg) encountered an error during the common_setup event phase
§7java.lang.IllegalStateException: Config errors were found:

java.lang.IllegalArgumentException: Jankson file reading for "E:\Users\david\Downloads\1.19 Server\config\byg\trades.json5" failed due to the following error(s):
java.lang.IllegalArgumentException: Jankson file reading for "E:\Users\david\Downloads\1.19 Server\config\byg\trades.json5" failed due to the following error(s):
"evilcraft:werewolf" is not a valid id in registry: Registry[ResourceKey[minecraft:root / minecraft:villager_profession] (Experimental)].
Current Registry Values:

0. "minecraft:none"
1. "minecraft:armorer"
2. "minecraft:butcher"
3. "minecraft:cartographer"
4. "minecraft:cleric"
5. "minecraft:farmer"
6. "minecraft:fisherman"
7. "minecraft:fletcher"
8. "minecraft:leatherworker"
9. "minecraft:librarian"
10. "minecraft:mason"
11. "minecraft:nitwit"
12. "minecraft:shepherd"
13. "minecraft:toolsmith"
14. "minecraft:weaponsmith"
15. "pneumaticcraft:mechanic"
16. "byg:forager"
17. "armorplus:soul_exchanger"
18. "car:gas_station_attendant"

 missed input: { "evilcraft:werewolf": { "1": [], "2": [], "3": [], "4": [], "5": [] } }
 

Expand  

 

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted

This is in your config file, not the mod:

E:\Users\david\Downloads\1.19 Server\config\byg\trades.json5

 

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted
  Quote

that's weird.... I used the update before the latest. should I go one step/version back again ?

Expand  

Since reverting to a previous version seems to have fixed the issue, you should report it to the mod author so they can fix it.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

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



×
×
  • Create New...

Important Information

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