Help With Custom Modpack

[Munkey_Boy]

I guess it would say 'error' etc, sorry for so many questions it's my first time.

[plowmanplow]

Look for entries with "SEVERE" or "exception".

 

Something with SEVERE isn't necessarily fatal, just something to be aware of.

Edited June 2, 2014 by plowmanplow

[Munkey_Boy]

Its still not working and no erros are occurring crash log (https://www.dropbox.com/s/e3987uf3n33d3f0/crash-2014-06-03_19.46.56-client.txt)

forge log (https://www.dropbox.com/s/pmbp0x6jpsmwt6z/ForgeModLoader-client-0.log) many thanks

[plowmanplow]

• You have a block ID in ResonantInduction.cfg for molten_copper set to 16000. The highest value for blocks capable of worldgen is 4095 (as previously mentioned). However, somehow you ended up with a number of conflicts between blocks in the same ResonantInduction.cfg file. No idea how that would happen. You are better off at this point just removing the ResonantInduction.cfg file and letting the mod make a new one.
• You need to update to the beta (as of this post) of Magical Crops to be compatible with the version of Thaumcraft you have installed. You will have a few block ID conflicts to fix after you do this.

Don't feel to bad about missing that last one. The MCF post for Magical Crops doesn't mention anything about being compatible with certain versions of Thaumcraft. A tricky crash.

[Munkey_Boy]

Sorry I didnt realise the molten copper (16000) counted as a block, as for the last point I had no clue, you sir are a genius!

[plowmanplow]

Pretty much anything inside a tag like this is considered a block:

blocks {
   .
   .
   .
}

[Munkey_Boy]

Sorry theyre all called beta's? Is it the 15a one?http://magicalcrops.weebly.com

[plowmanplow]

Yes, the file named "magical_crops_1.6.4_3.2.0_BETA_15a.zip" worked for me.

[Munkey_Boy]

You don't happen to have the config file for resonant induction as ive ran it clean but wasnt playing ball...

[plowmanplow]

Not any more. I test so many modpacks that my BareBonesPack gets cleaned out as soon as I move on to another pack to test. Just go through the same procedures you have been doing so far. If you get stuck make sure your hosted pack is up to date and I'll take another look.

[Munkey_Boy]

Ok cheers :D

[Munkey_Boy]

I done everything you said but the same error with resonant induction is still happening???

[plowmanplow]

I'm not really sure what you are doing. If I load your pack, remove the ResonantInduction.cfg and run the pack it makes one that works just fine.

[Munkey_Boy]

Remove the config file, upload to file host site, then redownload the pack? I'm lost as well

[plowmanplow]

No, no. Remove the config in your %APPDATA%.technicmodpacksblahblahblahconfig folder, start the pack, THEN  re-package the modpack archive and upload it. Always, always get ALL the bugs worked out before uploading a new one.

[Munkey_Boy]

Thats what I did, installed resonant induction by itself to get the config (plus necessary mods), then fixed all id conflicts, uploaded, re downloaded and then BAM!

[Munkey_Boy]

I done what you mentioned in the previous step of deleting the config from appdata....../my modpack etc, it loaded fine in singleplayer, I uploaded to dropbox, ran through my launcher and it's working perfectly! 

Many thanks for all of your help

:D