Back to mods
Chocolate Fix project artwork

CurseForge · Minecraft mod

Chocolate Fix

Fixes vanilla bugs - mostly to do with custom world generation - which have a much larger impact on modded.

Choose a version Pick your version below, then grab the matching file.

This page is having a moment, so a few details may be a little behind.

Quick answer

Which Chocolate Fix release should I use?

Updated 5 years ago
Latest stable file chocolate-1.3.0-1.16.4.jar
Game version 1.16.5, 1.16.4
Loader Forge

Chocolate Fix chocolate-1.3.0-1.16.4.jar targets 1.16.5, 1.16.4 with Forge. The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server. No extra mods listed for this file.

Where it goes

Is Chocolate Fix required on the client, server, or both?

The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release Forge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Chocolate Fix chocolate-1.3.0-1.16.4.jar need?

chocolate-1.3.0-1.16.4.jar. Change the file and its required mods may change too.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional mods.

Before you install it

Add Chocolate Fix without breaking your instance.

Built for Chocolate Fix chocolate-1.3.0-1.16.4.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use chocolate-1.3.0-1.16.4.jar. It targets 1.16.5, 1.16.4 with Forge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Put it on the correct side

    The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside chocolate-1.3.0-1.16.4.jar. It opens that exact file at the source.

About this project

What does Chocolate Fix add?

Chocolate

Vanilla is good - but chocolate is better. ;)

This mod exists to fix vanilla bugs - mostly to do with custom world generation - which have a much larger impact on modded.

Fixes

MC-202036: Biomes IDs may become shuffled when adding or removing biomes

In vanilla, adding or removing a biome datapack may lead to shuffled biome IDs in existing worlds. This has a much larger impact on modded, as adding or removing biome mods, or even blacklisting certain biomes may cause biomes in existing worlds to shuffle, or even if a mod changed the order of their biome registrations.

Chocolate fixes this by adding a palette of biomes to each chunk when it is saved. This means chunks saved while this mod is active will never experience biome shuffling as long as the biome exists. If a biome is removed from the world, Chocolate will detect this also and re-generate the biome according to the vanilla world generation at that location (as opposed to assigning it a random biome based on the previous ID, as in vanilla).

Update 2021-01-28: Forge attempted (unsuccessfully) to fix this issue in 34.1.42. Several weeks later, they did successfully fix* this issue (as per my own testing) in 36.0.2. Their fix does not conflict with Chocolate's, which incidentally also fixes MC-197616 (which Forge does not). However, if you are here for biome ID shuffling, I recommend you just update Forge instead.

* Per my testing, there still seems to be reproduction cases of this issue, however, they will only occur with datapack-only biomes, but every reproduction case I've found thus far has been overshadowed by MC-197616 (below). Meaning that, unless you run into the below issue, you will never see biome ID shuffling.

MC-197616: Data Pack Biomes with the "Single Biome" world preset causes massive log spam and invalid client biomes.

Related to the above issue, when using the "Single Biome" world type, biomes in world do not exist in the runtime biome registry. Chocolate is able to fix biome serialization over the network in this case, which prevents the aforementioned ill effects when trying to deserialize invalid biomes on a client.

Chocolate also previously fixed MC-197860, but that has been incorporated into Forge as of 35.1.32, and as such is no longer also fixed by Chocolate.

This mod's name is a play on the "Vanilla Fix" mod as the name "Chocolate" was already taken.

Project description from CurseForge.

Pick your setup

Chocolate Fix by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

3 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Chocolate Fix versions and loaders

6 of 6 releases match

Looking for an older file? The official CurseForge project page is in Resources.