Intro:

hi, i created a modpack with 50/60 mods i just putted 34/35 because it keeps crashing and i didnt know why so i deleted all the mods and added some to know what was the problem. the AbyssalCraft mod was the problem and i dont know how to fix this... anyone can help me please im desperate.

Crash report:

latest.log

[pastebin/gist/etc link here if the bug results in a crash, leave line empty otherwise]

Affected versions ("latest" is NOT a version):

• Minecraft:1.7.10
• Forge:???
• AbyssalCraft:1.9.1.3

Latest log file for when the issue was present:

[pastebin/gist/etc link here]

java.lang.RuntimeException: Biome ID 100 is already occupied by the biome Eden (net.divinerpg.dimensions.twilight.eden.BiomeGenEden)!
You have a biome ID conflict. Check either the AbyssalCraft or DivineRPG config file and modify the IDs there.
AbyssalCraft uses the ID range 100 - 113, so keep that in mind when configuring.

thank you so much @Shinoow

can you help me to modify the id of divinerpg? if yes where i have to set the id config? minecraft mod menu?

??

If you open your modpack folder, there should be a folder named config next to the mods folder. This folder should contain a bunch of .cfg files (and possibly other stuff), and there should be one called something along the lines of "divinerpg.cfg". I have no idea what the contents of that file look like, but I would assume there should be something there mentioning biome IDs. Open it and modify any biome ID config option so that no biome from that mod occupies the ID range 100 - 113, then the game should load.

ok i did thanks

but still not working :\

@Shinoow im having a problem while starting a world. i waited 2 hours and thats what it says:

@Shinoow im having a problem while starting a world. i waited 2 hours and thats what it says:

2023-11-26-6.log.gz

ill see if i find it 1s

Uploading 2023-11-26-6.log…
should be this

I can't really make out anything from that picture. If you send your logs I could look through that and see if I see anything.

I need the latest log. One that's nearly 3 weeks old won't contain the log data from yesterday

Hm... I can't really pin down anything. Erebus seems to track something, which in turn references optifine (probably just something that's overridden by OF). Failcraft is loading a billion dimensions, which might be part of the problem (could be something there that hangs up down the line). Honestly, this isn't related to AbyssalCraft anymore, unless there's a dimension id conflict, but that should've crashes during startup.
I can't help you with this. Might wanna join a modpack dev Discord server or another community and ask for help there.

but what you mean "that's overridden by optifine"?

ok

do you mean the problem is caused by that? i also tried without and still not workin

or by the erebus mod?

than what i have to send? the log i sended was for the crash of minecraft with abyssalcraft and said shutting down internal server

That log is from an instance running 1.19.2. I can't help you if you send the wrong log file. The file I want you to send is latest.log, AFTER trying to create a world in the 1.7.10 setup (assuming it fails the same way again).

ok ill see again

ok im trying to enter a new world in 10-20minutes ill send the log if it doesnt start

latest.log
here

look

Well, there you have it, you don't have enough memory allocated.