I've been trying to make a (fairly large) custom mudpack using the curse/twitch app and I've gone through slowly correcting all the issues in the crash reports. Recently as the pack has started to load, everything works fine until it hits step 6. Here it will stop responding and if I leave it to load, it will go on infinitly (I left it for about 5 hours and it made no difference). Upon closing it and checking the folders I cannot find any new crash log. I have no idea how to fix this (preferably without removing any mods and rather just changing some configs).
Note: I can provide a modlist if requested however be prepared for a large amount of mods.
I've been trying to make a (fairly large) custom mudpack using the curse/twitch app and I've gone through slowly correcting all the issues in the crash reports. Recently as the pack has started to load, everything works fine until it hits step 6. Here it will stop responding and if I leave it to load, it will go on infinitly (I left it for about 5 hours and it made no difference). Upon closing it and checking the folders I cannot find any new crash log. I have no idea how to fix this (preferably without removing any mods and rather just changing some configs).
Note: I can provide a modlist if requested however be prepared for a large amount of mods.
A mod list would be helpful, along with the "latest.log" from the logs folder.
It's an Abyssalcraft issue, seems to be complaining about biome IDs. Specifically the one(s) with ID 103. You may try resolving the biome ID conflict and see if it'll start. Although, if there's a conflict, I'm not used to the game crashing.. usually it'd just cause some weird map generation, but maybe it's a failsafe Abyssalcraft has built in?
If you aren't sure what biome IDs are available, try using the mod Anti ID Conflict. It'll force crash your game if there's any conflicts, and output a log in the config/Anti ID Conflict folder with duplicate IDs, as well as available IDs so you can safely reassign them.
The thing is, those logs have all been resolved in that I edited biome IDs. When the pack stops responding (and I manually close it) it will provide no log anywhere. So I have no idea what the problem is.
I see what you mean. Those logs are from 8/12. Perhaps try deleting latest.log and then MC should create a fresh one, hopefully with more information about where the problem is coming from. Other than that, I'm out of ideas, sorry!
Not working, but thanks for trying, I do appreciate it. But perhaps you can help me with a separate issue on a different custom pack. (Full thing here: Grass Issues ) but essentially I have problems with having grass spread (those being that it IS spreading) and I have no idea how to stop it from spreading (modded or not).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've been trying to make a (fairly large) custom mudpack using the curse/twitch app and I've gone through slowly correcting all the issues in the crash reports. Recently as the pack has started to load, everything works fine until it hits step 6. Here it will stop responding and if I leave it to load, it will go on infinitly (I left it for about 5 hours and it made no difference). Upon closing it and checking the folders I cannot find any new crash log. I have no idea how to fix this (preferably without removing any mods and rather just changing some configs).
Note: I can provide a modlist if requested however be prepared for a large amount of mods.
A mod list would be helpful, along with the "latest.log" from the logs folder.
Mod List - https://pastebin.com/DMe5r9XF
Latest Log - https://pastebin.com/23FaSc1w
Second Latest Log - https://pastebin.com/WFfypraL
Third Latest Log - https://pastebin.com/jb4aa12h
(After Review I've realized I have a fairly normal amount of mods)
Add Rope Bridge and Battle Towers to the mod list
It's an Abyssalcraft issue, seems to be complaining about biome IDs. Specifically the one(s) with ID 103. You may try resolving the biome ID conflict and see if it'll start. Although, if there's a conflict, I'm not used to the game crashing.. usually it'd just cause some weird map generation, but maybe it's a failsafe Abyssalcraft has built in?
If you aren't sure what biome IDs are available, try using the mod Anti ID Conflict. It'll force crash your game if there's any conflicts, and output a log in the config/Anti ID Conflict folder with duplicate IDs, as well as available IDs so you can safely reassign them.
The thing is, those logs have all been resolved in that I edited biome IDs. When the pack stops responding (and I manually close it) it will provide no log anywhere. So I have no idea what the problem is.
I see what you mean. Those logs are from 8/12. Perhaps try deleting latest.log and then MC should create a fresh one, hopefully with more information about where the problem is coming from. Other than that, I'm out of ideas, sorry!
Not working, but thanks for trying, I do appreciate it. But perhaps you can help me with a separate issue on a different custom pack. (Full thing here: Grass Issues ) but essentially I have problems with having grass spread (those being that it IS spreading) and I have no idea how to stop it from spreading (modded or not).