Tsa6 Posted June 16, 2015 Share Posted June 16, 2015 Hi, I'm building a modpack (early stages), and getting a crash when I launch the pack. It doesn't launch normally, but if I swap out the minecraft.jar (after its installed) with a healthy one, the pack launches fine. This leads me to believe it's a problem with my original modpack.jar, though I do believe I installed it correctly. I downloaded forge universal for 1.7.10, and renamed it to modpack.jar. Anyone know what I did wrong? (Link to modpack files) (Link to Crash Log) Thank you for helping! Link to comment Share on other sites More sharing options...
Discord Moderator plowmanplow Posted June 16, 2015 Discord Moderator Share Posted June 16, 2015 Always provide the API URL for your pack or a link to the pack's details page when requesting custom modpack assistance. That crash report does not match the data in your modpack archive. The crash report indicates Forge #1448 but the modpack contains Forge #1291. Where is the discrepancy coming from? Forge for MC 1.7.10 does not use a coremods folder in any way. It should be removed from the pack archive. All mods belong in or below the 1.7.10 folder. Legacy Java Fixer is not required for Forge >= 1230 and should be removed from your pack. Please address these issues and return here if you have more issues. Link to comment Share on other sites More sharing options...
Tsa6 Posted June 18, 2015 Author Share Posted June 18, 2015 (edited) Always provide the API URL for your pack or a link to the pack's details page when requesting custom modpack assistance. That crash report does not match the data in your modpack archive. The crash report indicates Forge #1448 but the modpack contains Forge #1291. Where is the discrepancy coming from? Forge for MC 1.7.10 does not use a coremods folder in any way. It should be removed from the pack archive. All mods belong in or below the 1.7.10 folder. Legacy Java Fixer is not required for Forge >= 1230 and should be removed from your pack. Please address these issues and return here if you have more issues. Thanks for helping, I have updated the modpack, also, here is the link to the api (http://api.technicpack.net/modpack/testpackfossilsbiblioharvest for easy copying) URL. I have removed the coremods folder, and removed legacy Java fixer. As for the forge version, I don't know why the log is different, so just in case, I updated forge to version 1448. However, I still get a crash, presumably the same one. Again thank you very much for the help, and sorry for not including the api URL previously. Edited June 18, 2015 by Tsa6 Fixed link Link to comment Share on other sites More sharing options...
Discord Moderator plowmanplow Posted June 18, 2015 Discord Moderator Share Posted June 18, 2015 (edited) The link you provided is not an API URL. It looks like you linked the same URL twice instead of a crash report and the API URL. Additionally, the log data you are providing is not the crash report. Those are generated in the modpack's crash-reports folder. Edited June 18, 2015 by plowmanplow Link to comment Share on other sites More sharing options...
Tsa6 Posted June 18, 2015 Author Share Posted June 18, 2015 The link you provided is not an API URL. It looks like you linked the same URL twice instead of a crash report and the API URL. Additionally, the log data you are providing is not the crash report. Those are generated in the modpack's crash-reports folder. My apologies, the api link is fixed, but the crash report was not generated, as Minecraft seems to crash before such processes take place. The one provided does have crash details in it however. (See line 43) Link to comment Share on other sites More sharing options...
Discord Moderator plowmanplow Posted June 19, 2015 Discord Moderator Share Posted June 19, 2015 This is why having the API URL is so important: Your pack settings are configured to be a 1.8.3 modpack, but you have mods and Forge for 1.7.10. You need to change your pack settings to 1.7.10. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now