Mac Mindcrack pack won't launch.

[Jess887cp]

Alright. I have a white macbook, 2 ghz, with a gig of memory allocated. I'm running Java SE 6. I'm using a crappy intel gma 950 graphics card.

Anyway, I've been playing the direwolf pack for awhile after watching a bunch of the ftb lets plays of the mindcrack server. I got direwolf because it had more mods, soit appeared.

I decided to switch over to the mindcrack pack for the gregtech, seeing as I was getting bored of just ic2. I downloaded the pack, and when I launch it, I get this log: http://pastebin.com/qtaqtsxQ

I'm guessing it's a problem with my version of java. If it is, what is breaking it? Could I just add gregtech to the other pack?

In any case, any help would be much appreciated.

 

[Booker The Geek]

1. Laptop?
2. Mac?

I think there are your two big problems...

Otherwise, Could you please post both the console log and the crash-log?

 

[Jess887cp]

Bah, i thought that was the log I needed. Anyway, I just decided to manually install gregtech into the direwolf launcher. I got this:

2013-03-02 19:43:06 [SEVERE] [fml.ItemTracker] FML has detected item discrepancies
2013-03-02 19:43:06 [SEVERE] [fml.ItemTracker] Missing items : {}
2013-03-02 19:43:06 [SEVERE] [fml.ItemTracker] Mismatched items : {30101=(Item 30101, Type ic2.core.item.reactor.ItemReactorUranium, owned by IC2, ordinal 2, name null, claimedModId null, Item 30101, Type gregtechmod.common.items.GT_RadioactiveCell_Item, owned by GregTech_Addon, ordinal 6, name null, claimedModId null), 30086=(Item 30086, Type ic2.core.item.reactor.ItemReactorReflector, owned by IC2, ordinal 1, name null, claimedModId null, Item 30086, Type gregtechmod.common.items.GT_NeutronReflector_Item, owned by GregTech_Addon, ordinal 1, name null, claimedModId null), 30102=(Item 30102, Type ic2.core.item.reactor.ItemReactorUranium, owned by IC2, ordinal 1, name null, claimedModId null, Item 30102, Type gregtechmod.common.items.GT_RadioactiveCell_Item, owned by GregTech_Addon, ordinal 7, name null, claimedModId null), 30087=(Item 30087, Type ic2.core.item.reactor.ItemReactorReflector, owned by IC2, ordinal 0, name null, claimedModId null, Item 30087, Type gregtechmod.common.items.GT_NeutronReflector_Item, owned by GregTech_Addon, ordinal 2, name null, claimedModId null), 30207=(Item 30207, Type ic2.core.item.reactor.ItemReactorUranium, owned by IC2, ordinal 0, name null, claimedModId null, Item 30207, Type gregtechmod.common.items.GT_RadioactiveCell_Item, owned by GregTech_Addon, ordinal 8, name null, claimedModId null)}

Is this relevant? If you need the other logs I'll post them. Note that this happened when I put gregtech into direwolf. Any fix for this in particular would be helpful. I hope that it is simpler.

 

[Whovian]

1. Laptop?
2. Mac?

I think there are your two big problems...

Haha! Though I can tell you that (other than minor issues with the Launcher that MultiMC can fix and a few frame rate issues that aren't too important) my MAC laptop works fine.

To the first crash, unfortunately, there's an unknown paste ID, so I can't see it. The GT DW20 crash seems unfamiliar, though it looks a lot like a problem I was having a little while ago that I thought was a but but wasn't really. There's a minor bug with some IC2 Nuclear Reactor components (I think their durability doesn't work properly, though I could be wrong about what the bug is) and the way Greg fixed that was to add items with the same IDs which overload them and aren't buggy. IDK if that's the only way, but I suppose it works. So I don't think the bit you quoted was significant other than we now know you didn't lie and did install GT.

 

[Booker The Geek]

Was the direwolf20 pack the Recommended version?
Did you make sure to grab the right version of Gregtech for the version of forge that is in DW20?
How did you install GT into DW20?

 

[Jess887cp]

The GT is working fine now. Everything is still a bit weird. I grabbed gregtech from the mindcrack pack and dragged it to my desktop. Then I just used the edit mod pack button in the launcher to add it in. Seems to work fine now. I would say that the issue is resolved, so I'm very sorry for the bump. I don't know what the lock policy on this forum is...

Erm, I'mma go hang out in some other hreads now, kthanksbye.