Looks like you have a lot going on there. Given the somewhat generic IndexOutOfBounds error, you're gonna have to do some leg work to see what mod is unhappy. Building a big pack is not impossible for one person to do, but it is a *lot* of work. Given the mod developers cannot anticipate which mods you want to put together, they can only assume that you are installing their mod alone in most cases. While generally that isn't an issue, it can lead to some mods trying to change the same code in the base game and thus being incompatible. Your best bet would be to start a fresh install, add only a few mods and the try booting the game. Once you determine those mods will boot, then add a few more a repeat. You'll keep doing this until you have a crash, that may give you a better insight into which mod may not be working as expected.
A few other things to watch out for, make sure you have downloaded the version of the mod for your version of MC and forge. Sometimes it can be a little tricky to tell, as there is no universal versioning scheme adopted by all mod developers. With such a large pack, you may also run into memory issues, you'll want to make sure you have enough memory dedicated to your Minecraft instance.
I know it takes long 1.7.10 pack I made for myself and my friends took me around 4-5 months :). I usually add the old known mods, mods that are downloaded a lot and new mods that seem ok, to test which which mods should stay and which mods should get removed/changed/updated or fixed. The reason I posted this error is because I've never seen a crash that gave me so little info and the IndexOutOfBounds error looked very odd (I was in a hurry so didn't read/test much). So I posted it here so people that have seen the likes of this can help fix and later get help from here. But thank you all anyway
I've been making packs since near the beginning of 1.3 and never seen anything like this (I've seen IndexOutOfBounds but never one like this) :). I like making packs because you learn the mods you find lots of bugs (I mean as in we put them in the open :P) (especially with 300+ mods or in 1.7.10 450+ mods XD) and you also learn many mods that are underrated and I don't get bored making the packs it's more like a puzzle for me especially to make it stable enough that I don't get a world corrupting bug which I've gotten at least a few hundred times. Also I removed many mods at 130 right now still crashing with the SAME error. I should solve this within this week or so if I find the time.
I'm crashing on my pack that I've made and I've never seen an error like this. Crash happens almost at the end.
Crash report: http://pastebin.com/TYshVG1i
Log: https://www.dropbox.com/s/n48a7ys1mmzv4ku/fml-client-latest.log?dl=0 (It's 4.5Mb)
Lower the render distance.
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
What are you doing with a 300 mod pack anyways? Even 100 uses a lot of resources.
My Vanilla server compatible modpack
My modpack that goes beyond Vanilla
Looks like you have a lot going on there. Given the somewhat generic IndexOutOfBounds error, you're gonna have to do some leg work to see what mod is unhappy. Building a big pack is not impossible for one person to do, but it is a *lot* of work. Given the mod developers cannot anticipate which mods you want to put together, they can only assume that you are installing their mod alone in most cases. While generally that isn't an issue, it can lead to some mods trying to change the same code in the base game and thus being incompatible. Your best bet would be to start a fresh install, add only a few mods and the try booting the game. Once you determine those mods will boot, then add a few more a repeat. You'll keep doing this until you have a crash, that may give you a better insight into which mod may not be working as expected.
A few other things to watch out for, make sure you have downloaded the version of the mod for your version of MC and forge. Sometimes it can be a little tricky to tell, as there is no universal versioning scheme adopted by all mod developers. With such a large pack, you may also run into memory issues, you'll want to make sure you have enough memory dedicated to your Minecraft instance.
Hope these pointers help and best of luck!
I know it takes long 1.7.10 pack I made for myself and my friends took me around 4-5 months :). I usually add the old known mods, mods that are downloaded a lot and new mods that seem ok, to test which which mods should stay and which mods should get removed/changed/updated or fixed. The reason I posted this error is because I've never seen a crash that gave me so little info and the IndexOutOfBounds error looked very odd (I was in a hurry so didn't read/test much). So I posted it here so people that have seen the likes of this can help fix and later get help from here. But thank you all anyway
Oh yead that error code, still don't know what it means after years of pack making.
My Vanilla server compatible modpack
My modpack that goes beyond Vanilla
I've been making packs since near the beginning of 1.3 and never seen anything like this (I've seen IndexOutOfBounds but never one like this) :). I like making packs because you learn the mods you find lots of bugs (I mean as in we put them in the open :P) (especially with 300+ mods or in 1.7.10 450+ mods XD) and you also learn many mods that are underrated and I don't get bored making the packs it's more like a puzzle for me especially to make it stable enough that I don't get a world corrupting bug which I've gotten at least a few hundred times. Also I removed many mods at 130 right now still crashing with the SAME error. I should solve this within this week or so if I find the time.