Jump to content

My Custom Modpack Crashes on the Mojang Screen


Recommended Posts

- Title: My custom modpack crashes on the mojang screen

- Type of bug: Launcher bug

- Reproduction rate: 10/10

- Steps to reproduce:

Opened the Technic Launcher

Selected my custom modpack (Narcotic Craft)

Clicked Play

Launcher disappeared

Mojang screen appears

Mojang screen disappears

Launcher reappeared

- Expected result: My modpack should fully load without crashing

- Observed result: Minecraft closes/crashes and the launcher reappears

- Logs: Launcher error report: http://pastebin.com/dGrmDc5y

             Platform URL: http://api.technicpack.net/modpack/narcotic-craft

             Download link: https://dl.dropbox.com/s/f8t96o3r4ieaf3s/modpack.zip?dl=1

- Extra Comments: I have downloaded and tested all of these mods on the vanilla client without the technic launcher and it works fine, I even have my own server for this modpack. My problem is that this modpack will not run on technic launcher and I can't figure this out...

I would appreciate any help that I could get!

Edited by Legomaniac359
Link to comment
Share on other sites

  • Discord Moderator
  • The /mods/VoxelMods/ folder should not be included in your client modpack. This will overwrite local client settings when the pack updates.
  • You have the Minechem source and API in the mods folder. Both of these should be removed.
  • You have voxelmapNoRadar, but neither VoxelMap.litemod nor LiteLoader on which it depends.
  • Many of your mods are very old, some fatally so (OptiFine for instance). You need to update all your mods to their latest versions.
Link to comment
Share on other sites

Thanks for the replies but I'm still stuck...

  • I have deleted voxelmap totally (haven't gotten around yet to finding a new minimap, so there are no maps right now)
  • I am confused when you tell me to remove the Minechem source. Is that he .jar file or the .zip file (there are two Minechem .zip files. One of them is API, but is the other .zip the source, or is the source file the .jar file?).
  • My mods are old because my server runs off of 1.7.10 & im not really in the mood to update that to 1.8 just yet. Is it because these are old mods, though, that are messing up the technic launcher? And if so, which ones? Because all of these mods work fine on the vanilla launcher...

Although I'm still stuck, after removing voxelmap I can at least make it to the main menu of Narcotic Craft using the technic launcher. It doesn't crash untill I create a new world.

Here are the links:

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

         Platform URL: http://api.technicpack.net/modpack/narcotic-craft

         Updated Narcotic Craft download: https://dl.dropbox.com/s/f8t96o3r4ieaf3s/modpack.zip?dl=1

Once again, help is very much appreciated; I know you guys got alot of other posts to read.

Link to comment
Share on other sites

  • Discord Moderator
  • The Minechem source is the file named: Minechem-1.7.10-
  • You have old versions of mods for 1.7.10. For example: OptiFine 1.7.10_HD_B5 instead of 1.7.10_HD_B7, BiblioCraft 1.7.10_1.9.2 instead of 1.7.10_1.10.4, all your ChickenBones mods (CodeChickenCore, NEI, etc), All your CoFH mods (CoFHCore, ThermalExpansion, ThermalFoundation), BuildCraft 6.4.1 instead of 6.4.18. Chisel instead of Chisel 2 ( http://coloredlightscore.us.to:8080/job/Chisel-2 v1.7.10-Dev/ )

Your crash is caused by one of your mods not being updated for the fluid registry changes that happened in Forge #1355. If you update ALL your mods to their latest versions the crash will likely be fixed.

Link to comment
Share on other sites

  • 2 weeks later...

Heeyyy!! Finally!

After taking a long break from modding & coming back to minecraft I decided the best way to solve the problem was to just delete everything and start fresh because there was so many mods to update; I ended up updating to the latest versions for each mod. After doing some research I found out that it was Minechem that was causing the fluid registry errors.

Thanks for the help Mr. Plow!!! :cheers:

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...