From the Fog Reimagined Installation Guide

Install with CurseForge

1. Find the creator’s pack

   Open From the Fog Reimagined on CurseForge ↗. Confirm the creator is SoumXD and the project ID is 964725. Using this link avoids confusing the pack with the base From The Fog mod.

2. Install the profile

   Use the project’s Install via App option, or find the exact pack in the CurseForge app’s Minecraft modpacks section and choose Install. If you need the app, use CurseForge’s own download page ↗.

3. Check the release

   For the release covered here, the profile should be 6.3.2 with Minecraft 1.20.1 and Forge. If joining friends, confirm their server release before changing your profile.

4. Set allocated memory

   Open My Modpacks, select the profile, open the three-dot menu and choose Profile Options. Use Custom RAM Allocation to set at least 6144 MB, then select Done. Keep enough memory free for your operating system and other apps.

5. Launch the profile

   Select the installed profile and choose Play. Keep this profile separate from unrelated mod collections. If startup fails, use the symptom-based troubleshooting guide below rather than adding random replacement mods.

What does 6144 MB mean?

This is the amount allocated to Minecraft, not a recommendation that your whole computer only needs that much RAM. Allocating all system memory to the game can leave other applications without room. CurseForge’s memory guide also describes the F3 display as a way to check the game’s maximum allocated memory.

Avoid mixing old and current instructions

The project description still contains a historical OptiFine step explicitly marked for version 1.5 and below. The current notes say not to use OptiFine. The linked Alex-addition tutorial is also marked as unnecessary for 6.3+. Neither is an extra setup step for this 6.3.2 guide.

If the game does not start

For a black screen, the creator recommends pressing R to reload shaders. For a crash or an “nbt is null” error, the initial recommendation is to relaunch the game or restart the server. See troubleshooting for the limits of these suggestions and the support checklist.