[1.7.10] Ingenuity - Are you Ingenious? ---- Where's all the usual mods?!?! o.O

[nolaw70]

@jikuja

I have done the following:

1. Created a new user account on my machine.

2. Downloaded and installed the FTB launcher (the .exe) from http://www.feed-the-beast.com/

3. Downloaded and launched Ingenuity 1.2.0 (after downloading and launching Infinity 1.6.2).

The dual mod install issue happened with Ingenuity, and it did not launch.

Log file uploaded, link is http://paste.feed-the-beast.com/view/2395cfdb

 

[jikuja]

@jikuja
The dual mod install issue happened with Ingenuity, and it did not launch.

Log file uploaded, link is http://paste.feed-the-beast.com/view/2395cfdb

Duplicate mods seems to be bug in the pack but I'm not sure about your crash. It might be caused by duplicate mods or not, but at least it is not directly telling that duplicate mods caused crash. Crash is caused by CodeChickenLib's ASM code, better wait until pack is fixed before trying to do more debugging job.

 

[jordsta95]

Duplicate mods seems to be bug in the pack but I'm not sure about your crash. It might be caused by duplicate mods or not, but at least it is not directly telling that duplicate mods caused crash. Crash is caused by CodeChickenLib's ASM code, better wait until pack is fixed before trying to do more debugging job.

There aren't duplicate mods in the pack :/
And the pack runs fine with the mods in it....

Unless different Java versions (i.e. Java8) don't work with that mod

 

[nolaw70]

Duplicate mods seems to be bug in the pack but I'm not sure about your crash. It might be caused by duplicate mods or not, but at least it is not directly telling that duplicate mods caused crash. Crash is caused by CodeChickenLib's ASM code, better wait until pack is fixed before trying to do more debugging job.

When the the older duplicates of the mods (see my post earlier in this thread for the list) are removed (either manually or from the Edit Modpack function), the pack launches normally.

 

[jordsta95]

Hence why I pushed 1.2.1 which removes them

 

[nolaw70]

Hence why I pushed 1.2.1 which removes them

I just installed 1.2.1 over a 1.2.0 installation that I had removed the duplicate mods from. With 1.2.1, Minecraft actually launches, but Forge Mod Loader reports a problem with the installation (duplicate mod sources) on Carnivora, ForgeMicroblock, ForgeMultipart, McMultipart and TConstruct. Navigating to the mods folder, I confirmed the older versions are there with the new ones as they were with 1.2.0. I removed the older versions of the mods and subsequently started the pack successfully.

 

[jordsta95]

>_> What the hell is wrong with my uploads >_>

 

[Magzie]

Guys, please if you have problems (with launcher) always post a log:


That will make finding cause of the problem faster.

Hmm! I thought someone suggested that as the problem would be posted on it like the launcher version or java version ex. ROFL I

 

[Magzie]

Could newer mod be que as a different file and that is why it isn't overriding the mods.

 

[jordsta95]

Could newer mod be que as a different file and that is why it isn't overriding the mods.

Who knows :/

 

[lenscas]

doesn't the launcher just deletes all the old files in the mods folder and then put the new ones in or got that changed?

 

[Magzie]

Ether way if the DUP mods are not the cause of the crash then fixing that first then worry about the dups. It is clearly not the pack of there is other packs with dups.

 

[nolaw70]

Hmm! I thought someone suggested that as the problem would be posted on it like the launcher version or java version ex. ROFL I

Well, the issue jikuja identifed as causing the crash is also not the problem causing the duplicate uploads with the pack.

 

[Magzie]

No

doesn't the launcher just deletes all the old files in the mods folder and then put the new ones in or got that changed?

It creates a new item in the folder not a new folder as far as I know. If it is qued up as a new folder the updates will not put the update change in. PR that is how I understand it.

 

[ZephyrWindSpirit]

So when I did the 1.2.0 update, I removed the doubles. I updated to 1.2.1, and so far its loading fine.
I'm not sure what's up, but at this rate you all will give poor @jordsta95 gray hair.
Go through your client, and take out the doubles yourself.

 

[nolaw70]

So when I did the 1.2.0 update, I removed the doubles. I updated to 1.2.1, and so far its loading fine.
I'm not sure what's up, but at this rate you all will give poor @jordsta95 gray hair.
Go through your client, and take out the doubles yourself.

I suspect jordsta95 would rather try to figure out what the issue is and attempt to solve it rather than deal with a multitude of messages asking for help with getting the modpack to install. Not everyone would decide to figure out what the issue was with pack not loading, they would just move on to another pack.

 

[Magzie]

So when I did the 1.2.0 update, I removed the doubles. I updated to 1.2.1, and so far its loading fine.
I'm not sure what's up, but at this rate you all will give poor @jordsta95 gray hair.
Go through your client, and take out the doubles yourself.

The dups could have been in for a while and no one saw it till a problem arose like this one.

 

[jordsta95]

So when I did the 1.2.0 update, I removed the doubles. I updated to 1.2.1, and so far its loading fine.
I'm not sure what's up, but at this rate you all will give poor @jordsta95 gray hair.
Go through your client, and take out the doubles yourself.

No, I know what the issue is. But it's weird why it did it. WON'T HAPPEN AGAIN

 

[jikuja]

No, I know what the issue is. But it's weird why it did it. WON'T HAPPEN AGAIN

until there is new issue with mmc's export feature.

 

[jordsta95]

until there is new issue with mmc's export feature.

Nah, I will just do it differently