Cannot start my modpack

[JustNoble]

Help me guys i have problems with my new and first modpack

Crash report:  http://pastebin.com/GtpJajn1

My modpack API:  http://api.technicpack.net/modpack/ark-survivalcraft-evolved

[Lenzh]

thats not a good crash report

go to your technic folder then modpack, your modpack crash-reports

and copy the latest crashreport in a pastebin

 

i can run the modpack

[JustNoble]

This is my latest crash report

[Lenzh]

this doesnt seem like a crashreport
http://pastebin.com/DcnUsiNE
this 
is a crash report

 

[JustNoble]

My crash isn't a minecraft crash

I have issues with my modpack that doesn't start, my technic launcher reopens itself instead of running my modpack

[Lenzh]

what java do you got?

and how many ram do you put in the technic launcher (how many ram does your pc have)

 

[JustNoble]

i've the jdk 1.8.0_11, jre8

I put 1 GB on my technic launcher and my pc has 4 GB Ram

Edited July 7, 2015 by JustNoble

[Lenzh]

try to add legacyjavafixer to your mods

[JustNoble]

I did, still not working

[Lenzh]

maybe your ram cant support it

[plowmanplow]

• Forge for 1.7.10 >= #1207 does not require the Legacy Java Fixer and it should not be included.
• Many of your mods are from illegitimate sources. Any mod named in the format of "ModName-Mod-1.7.10.jar" is likely to be from an illegitimate source. Always get your mods directly from the mod authors.
• You should update to the latest Java 8 64bit.
• Do not allocate more than 2G of RAM in the Launcher if your machine only has 4G total.

The following mods must be updated: (along with all the illegitimate sourced mods)

• CodeChickenCore
• Fossils and Archeology Revival
• NEI

Address these issues and come back if you are still having troubles.

[JustNoble]

I did all you said, still crashing

http://pastebin.com/QH51Q433

http://api.technicpack.net/modpack/ark-survivalcraft-evolved

[plowmanplow]

• You have altered your modpack archive but not incremented the pack version number. The Launcher is only notified of changes to a pack when the version number changes.

 

[JustNoble]

I updated my modpack but it crashes again

http://pastebin.com/H8tWLcga

[plowmanplow]

1. Increase your pack version number (again).
2. Remove and re-add the pack to your Launcher.
3. Launch the pack.

[JustNoble]

Nothing, same crash as before, i don't know what to do

[plowmanplow]

Please provide the most recent crash report from the crash-reports folder.

[JustNoble]

I haven't a crash-reports folder in my modpack folder, i don't know why.

I took reports from logs folder

Edited July 8, 2015 by JustNoble

[plowmanplow]

The pack adds and launches successfully for me. Not sure what to suggest other than removing mods individually (or as a set when a dependency is involved) until it works.

[JustNoble]

I tried to remove mods but the launcher crashes also without any mod, but i'm happy to hear that modpack works for you

[plowmanplow]

If your Launcher crashes with no mods in the pack (just Forge), then you have a Launcher issue and should be posting in Bug Reports for the Launcher.

[Shadowthekidr5]

Im having the same problem And im getting angry ive read other Comments from other post and i dont understand from what i understand you seem to belive i have a shader mod file if so thats not true also Legacy has a extremely slim chance of working however in most situations it is not needed But however i did mess around with the mods and there was a mod that was incompatible however when i removed it i still got the crash and i request assistance

[plowmanplow]

@Shadowthekidr5: Don't hijack someone else's thread. If you have an issue start a new thread and provide as much detail as possible. Always provide the API URL or a link to the pack details page.

[Shadowthekidr5]

You just said not to start a thread with the same problem and the rules say so as well soo im requesing help here

[plowmanplow]

@Shadowthekidr5: I never said to not start a thread. Neither in this thread or any other. The forum rules/guidelines do not state that either. Start a new thread as you will get no help in this one and you are distracting from the original poster. You almost certainly have a different issue, and even if you didn't you should start your own thread.