Well, I added a few mods to Monster 1.10 and how whenever I launch the game it crashes. I'm pretty sure if you add any mods to the packs support wont help you so I decided to post in this forum section.
Added a few mods to monster, constant crashes
- Thread starter Yukine Chris
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Can you tell me which mods you installed? Also what was the last mod you installed before the crash?
I added...
Thaumic History 1.1
Witchery 0.15.1
Forbidden Magic pr 0.32
Mekanism 6.03.30 + generators and tools
and Resonant Induction 0.3.1 + archaic, electrical and mechanic
I cant tell you which was installed last since I put them in at the same time.
Thaumic History 1.1
Witchery 0.15.1
Forbidden Magic pr 0.32
Mekanism 6.03.30 + generators and tools
and Resonant Induction 0.3.1 + archaic, electrical and mechanic
I cant tell you which was installed last since I put them in at the same time.
Typically I would suggest you install one mod at a time, this way you are able to discover which mod creates the problem. I would suggest from this point that you disable them all. Then install 1 at a time. Once you find the mod that is causing the crashes, first check if it needs any mods to accompany it in order to work properly (most often a Core mod). If that is not the problem, I would just look into if the mod has any incompatibilities with any other mods.
Ok I made it all the way to installing Resonant Induction core before crashing so I would guess it would be that.
If I recall correctly Calclavia core is already a part of the monster modpack (I dont play monster, so I may not be correct). Did you double install the Core?
Well due to me not having any further knowledge to help you find a solution for this. I would recommend you post your issue on the Calvacia Core issues page: https://bitbucket.org/calclavia/resonant-induction/issue/119/resonant-induction-startup-crash .
Yea, no problem. Wish I could actually help you solve the problem. Hope you figure out a solution.
Resonant Induction is notoriously buggy and unstable at the moment, however your crash could have just as easily been caused by a simple ID Conflict. Monster is a HUGE mod pack, there's not a whole lot of room for spare ID's. Can't wait for some of the 'staple' mods to come out to 1.7 when we no longer have to deal with them...
I did that, with even more mods, but including those you used. Mekanism 6.03.30 + generators and tools caused the crash problem for me, but ONLY if I had any of Reika's mods installed. Not sure why though.
Its not Resonant Induction, i have it and i experience no crashes in the latest version of Monster, be sure you have UE core and Calclavia core on their latest versions as they are included in monster but at a downgraded version.
To be more precise use this versions:
Calclavia Core: Stable build Number 307
UE core: Build Number 73
For the rest, latest versions should be fine.
Also for mekanism, im using 6.0.4.31 without issues and as 6.0.4.32 doesnt have anything in changelog I didnt update because I don't find it necessary.
Also, there is no ID conflict, as Monster comes with predefined configs for these mods except the new resonant induction which comes with a Expanded Redstone one (change the motor or the Expanded Redstone (Found on reika folder in config) to fix.
I've also installed witchery, can't remember which version but was the latest one (for testing purposes) and it didn't gave me a single crash and ran smoothly, but I uninstalled it because I simply didn't liked it, so unless it updated and broke something, it should work.
Also, for people saying that resonant induction is buggy, try using a public build instead of a development one and you will find it's not that buggy at all, resonant induction is my second power infrastructure (Reactor Craft being the first one and Atomic Science the third) and I've experienced no trouble whatsoever, please stop saying resonant induction doesn't work properly because its bandwagoning and giving it a bad start which doesn't deserve, it has MINOR bugs but nothing that could cause crashes or loss of play-ability and calclavia is working a fuckton on it as you could see with his constant builds.
Also if you'd like, try using a dev build if you feel like helping RI grow..
Edit: I cannot make the crash happen, are you using latest versions of everything and installing calclavia core correctly?
Edit2: Found out i was testing with development builds without knowing while I have my main build in another instance, reinstalled as stand alone and found the problem, doing new tests now in the monster pack to solve the issue (Apparently with calclavia core 1.1.1.287 it should work without having to use development builds.. Checking this possibility although I recommend using dev build)
Edit3: In monster environment with the following versions:
Calclavia Core 1.1.1.287
UE Core 3.1.0.73
Resonant 0.3.1.331 (Latest Public Build)
It works without crashing.
Another working setup:
Calclavia Core Stable # 307 / Calclavia Dev #5 (probably all of them but haven't checked)
Resonant Development #37+
To be more precise use this versions:
Calclavia Core: Stable build Number 307
UE core: Build Number 73
For the rest, latest versions should be fine.
Also for mekanism, im using 6.0.4.31 without issues and as 6.0.4.32 doesnt have anything in changelog I didnt update because I don't find it necessary.
Also, there is no ID conflict, as Monster comes with predefined configs for these mods except the new resonant induction which comes with a Expanded Redstone one (change the motor or the Expanded Redstone (Found on reika folder in config) to fix.
I've also installed witchery, can't remember which version but was the latest one (for testing purposes) and it didn't gave me a single crash and ran smoothly, but I uninstalled it because I simply didn't liked it, so unless it updated and broke something, it should work.
Also, for people saying that resonant induction is buggy, try using a public build instead of a development one and you will find it's not that buggy at all, resonant induction is my second power infrastructure (Reactor Craft being the first one and Atomic Science the third) and I've experienced no trouble whatsoever, please stop saying resonant induction doesn't work properly because its bandwagoning and giving it a bad start which doesn't deserve, it has MINOR bugs but nothing that could cause crashes or loss of play-ability and calclavia is working a fuckton on it as you could see with his constant builds.
Also if you'd like, try using a dev build if you feel like helping RI grow..
Edit: I cannot make the crash happen, are you using latest versions of everything and installing calclavia core correctly?
Edit2: Found out i was testing with development builds without knowing while I have my main build in another instance, reinstalled as stand alone and found the problem, doing new tests now in the monster pack to solve the issue (Apparently with calclavia core 1.1.1.287 it should work without having to use development builds.. Checking this possibility although I recommend using dev build)
Edit3: In monster environment with the following versions:
Calclavia Core 1.1.1.287
UE Core 3.1.0.73
Resonant 0.3.1.331 (Latest Public Build)
It works without crashing.
Another working setup:
Calclavia Core Stable # 307 / Calclavia Dev #5 (probably all of them but haven't checked)
Resonant Development #37+
Last edited:
Ok thanks for your help doing what you guys said now. I posted on the Resonant Induction support page last night and all I got was 'install calcore' even though I know it's already there.
That's ICBM going crazy, let me give you the correct versions to make it work without dev builds:
Calclavia Core 1.1.1.287/ Dev #5
UE core 3.1.0.73
Induction 0.3.1.331+
ICBM 1.4.1.322 (Don't use EMP missiles from the horizontal launcher)
Atomic Science 1.1.0.55+
That should work perfectly, let me know if you encounter any other error.
Calclavia Core 1.1.1.287/ Dev #5
UE core 3.1.0.73
Induction 0.3.1.331+
ICBM 1.4.1.322 (Don't use EMP missiles from the horizontal launcher)
Atomic Science 1.1.0.55+
That should work perfectly, let me know if you encounter any other error.
Does that version if ICBM actually care if you want the potionIDs to be assigned elsewhere? The version I have(1.4.1.226) gives zero fucks that it's overwriting vanilla potion effects.
EDIT: You know, maybe it would have helped if I checked the other configs that cropped up when I installed that batch...
Calclavica.cfg lines 89-98 as follows...
Code:
####################
# """""""""""""potion id"""""""""""""
####################
""""""""""""""potion id"""""""""""""" {
I:"frostBite ID"=24
I:"radiation ID"=21
I:"toxin ID"=22
I:"virus ID"=23
}YEY GONNA FIX DIS NAO.
Last edited:
Doensn't give a flying fuck but take care and check BoP potions too, as they make some duplicates. If you are using witchery, then also check their potion ID's. And if you are going to change this take extreme care because other mods add own effects and you may overwrite them, as far as I know the most problematic one is ars magica, but its range goes up to 36 or so I think, so if you use potion ID's of 40+ you should be set.