Overclocked Horizons

• I removed the stale enabled Sodium/Embeddium Dynamic Lights addon entry from <button class="cursor-interaction inline-block max-w-full appearance-none border-0 bg-transparent p-0 text-left align-baseline whitespace-normal text-token-text-link-foreground hover:underline" type="button">minecraftinstance.json</button>, so new CurseForge exports should stop telling downloaders to install sodiumdynamiclights-neoforge-1.0.10-1.21.1.jar.
• I deleted the leftover disabled copies so the instance folder itself no longer carries that jar around:
  • <button class="cursor-interaction inline-block max-w-full appearance-none border-0 bg-transparent p-0 text-left align-baseline whitespace-normal text-token-text-link-foreground hover:underline" type="button">sodiumdynamiclights-neoforge-1.0.10-1.21.1.jar.disabled</button>
  • <button class="cursor-interaction inline-block max-w-full appearance-none border-0 bg-transparent p-0 text-left align-baseline whitespace-normal text-token-text-link-foreground hover:underline" type="button">sodiumdynamiclights-neoforge-1.0.10-1.21.1.jar.pre_disable_backup</button>

I also verified there are no remaining sodiumdynamiclights entries in installedAddons. The only references left are harmless leftovers in old crash reports, user-prefs.json, a local crash-assistant cache file, and the old client config file.

The important next step is to export and share a brand new CurseForge zip now. Anyone using an older exported zip can still get the same crash even though the instance is fixed now