Sevtech-ages: Start up Crash: Null Pointer on language detection

Created on 16 Aug 2018  路  13Comments  路  Source: DarkPacks/SevTech-Ages

Bug Report

Start up crash with a clean install.
I had befor a crash with Astral (I wanted to do this : https://ftb.gamepedia.com/Armara )

Expected Behaviour

No crash.

Possible Solution

Update Geolosys? (Crash log say something with Geo.)

Steps to Reproduce (for bugs)

  1. Start game
  2. Wait
  3. Crash

Logs

Client Information

  • Modpack Version: 3.0.8
  • Java Version: J8_U51 (from MC launcher, but it also dont work with J8_U181 + 10 GB)
  • Launcher Used: Curse
  • Memory Allocated: default Curse (7GB)
  • Server/LAN/Single Player: Client, but I want to connect to a Server
  • Optifine Installed: No
  • Shaders Enabled: No

World Information

  • Modpack Version world created in: 3.0.8
  • Additional Content Installed: No
Completed Bug

All 13 comments

mine is crashing now too. Been playing for weeks and something updated this morning when I went to load the pack. Now crashes on launch.

https://pastebin.com/guAA39cp

The game crashed whilst initializing game
Error: java.lang.NullPointerException: Initializing game

Same thing happens to me and the log is similar. It's the geolosys getTranslation for me too that throws the NullPointerException.

Same here for me, gonna upload my error log.

https://pastebin.com/LcxKW6Yh

I think there was a windows update last night since I woke up to my PC being on the lock screen even though I left it on last night.

Me too. Crashed every time after Loading Entity Render stage
https://pastebin.com/LAtjfcEQ
p.s. and yes Windows10 was updated last night

Here is a band-aide fix...
I had the same errors start this morning on 3 different PCs (Win7 and Win10). They were working fine last night!
I went into the Twitch client's settings, then selected 'Minecraft' on the left menu, set 'Launch Method' to Jar Launcher instead of Native, then made sure the Java Version was pointed to my PC's installed Java folder. Tested using jre 1.8.0_171 and 181 on Win7, then jre 1.8.0_144 on Win10.
After making this change, it allowed me to boot the game just fine, though it uses a different style launcher. So, you will want to sign back in to that launcher, then close it, then reopen it to get the Sevtech profile loaded.

@akaikishi 's fix worked for me. Thanks man.

I'm having the exact same issue as everyone else. The game ran fine yesterday, but today it's crashing on init with a Null Pointer Exception in Geolosys. I've uploaded my crash report, but I doubt it contains anything new: https://paste.ee/p/z1psG

I'm playing under Linux and using the MultiMC launcher, so the above workaround doesn't work for me.

How might one implement @akaikishi 's fix in MultiMC?

I manually updated Geolysis mod to v2.1.0 and it seems to have worked also using the standard launcher from the Twitch client.

Whatever you do. Don't update Geolysis unless you want to lose your world...

I'm going to lock this as the issue needs confirming by the developers of the modpack. Not "ideas"

This has been identified as a bug on Mojang's side. They are aware and patching the files. You'll need to wait for the cache to reset and re-launch your game, which will re-download the assets files which contains the fix.

This will take a bit to propagate. So keep trying and it will eventually work. Note: You may need to restart the launcher each time for it to force check/download the files.

Thanks for the report guys! This was a fun one. 馃槅

As you may be aware there has been a bug introduced from a change by Mojang to support language files which don't contain an underscore in the name. I.E. brb.lang It was originally thought to of been a mistake by Mojang but the change was intentional. So the case failed on Forges side when it builds the language mapping. A pull request was created to Forge to resolve the issue and allow the understanding of the new files. (Which has been merged)

But we (DarkPacks) have taken the decision to not create a patch update for the modpack. As 3.1.0 is around the corner and we'd rather spend time on that. So what does this mean for you? The short story your game won't load if your client has downloaded the new assets from Mojang. 3.1.0 will contain the updated Forge when it gets released, so it won't be an issue then. We understand that people may want to play the pack, but we don't have the time to create a single update for Twitch/ATLauncher for Forge change. So we're going to ask you politely to wait for this update.

You can however if using the Twitch Launcher to change to the Jar launcher, but this does not work for all cases.

If you can't wait you can manually update Forge (When the build is live) but some mods in the 3.1.0 had to be updated to support other versions of Forge, which lead to world/client crashing. However, if you do this, you void all support from the team. As your using an unsupported version of Forge for 3.0.8 of the pack.

Closing this now. As Mojang changed the files on their end. And the update would be "patched" in the update to Forge. But the band-aid from Mojang will stick for the time being.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Petkip picture Petkip  路  5Comments

GearsOfClockwork picture GearsOfClockwork  路  3Comments

Xavfire picture Xavfire  路  5Comments

darkphan picture darkphan  路  4Comments

Dystilled picture Dystilled  路  3Comments