Corrupted files

JsonSyntaxException: Expected BEGIN_OBJECT but was STRING (Corrupted JSON File)

What it looks like in the log

java.util.concurrent.CompletionException: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING a

How to fix it

  1. Check the stack trace lines directly beneath 'Caused by: com.google.gson.JsonSyntaxException' in your log to see whether a mod or your launcher was reading the broken file.
  2. If the issue occurs when Minecraft loads mods or loops on the main menu, open your instance's 'config' folder and check recently modified .json files (such as sodium-extra-options.json) with a text editor.
  3. Delete any .json config file that appears completely blank, contains strange symbols/null characters, or belongs to the mod mentioned in the log so it can regenerate cleanly on the next launch.
  4. If the crash happens in your launcher before the game starts (for example, HMCL failing at readModpackConfiguration), back up your 'saves' folder and reinstall the modpack or recreate the launcher profile to restore a valid modpack.json.
LoadersFabric, Forge, Neoforge, Quilt, Vanilla
SeverityStops the game
CategoryCorrupted files

Check your own log

Related errors