Minecraft JavaForge 1.20.1Horror
A horror mod that quietly breaks an ordinary survival world: strange entities, random events, misplaced structures and a moon that looks wrong. You set how much of it is switched on.
Forge 1.20.1
55 events listed
Builds v0.71 to 1.9.3
Java Edition
A Forge mod for Minecraft: Java Edition 1.20.1 that turns normal survival play into a slow-building horror game. Here is how the pieces fit together.
Gathering, building, exploring, the usual.
The mod adds
Forge 1.20.1, Java Edition
12.5 MB the earliest archived build, a v0.71 beta
86 MB around the size of the 1.9 line
4 switches entities, events, structures, block breaking
The mod adds its own entities to your world. Some you see, some you only hear or notice afterwards. The config can stop them spawning if you want a calmer run, and a separate switch controls whether they can break blocks.
Scripted events can fire at any time. The community Patches add-on lists 55 of them and gives each its own toggle, so you can drop one event without losing the rest.
The mod generates its own structures. Datamined files in the archive carry names like bedrock hallways, field bases and void rooms, which hints at the range without spoiling it.
Familiar things stop looking right, the moon most famously. The Patches add-on even has an option to bring back the mod's older corrupted moon textures.
An in-game menu covers entity spawning, events, structures and block breaking, per world. Keep one save gentle and let another run wild.
Four levels from an empty game folder to your first night with the mod.
Install Minecraft: Java Edition 1.20.1 and Forge for that version, then launch the Forge profile once.
Download the community archive, open its index page and pick a build. Most players want 1.9.3.
Copy the .jar into the mods folder. One version only, and never the archive ZIP.
Launch Forge, create a fresh world and set the mod's config before exploring.
The same mod plays very differently depending on how you set it up.
Everything on, fresh world, no spoilers. The intended way in.
Start with features off via the Patches add-on and switch them on as the episode builds.
Disable block breaking and structures, keep the atmosphere.
Several community packs on CurseForge and Modrinth are built around it for Forge 1.20.1.
Replay early builds from the archive and compare how the mod changed.
Built from archived build names and public listings. Search terms are not treated as proof of support.
Every archived build is labelled forge-1.20.1.
Not documented.
Not in the catalogue for Forge 1.20.1; manual install works.
No build. Forge jars do not load on Fabric. Why
Java mods cannot run on Bedrock.
%appdata%\.minecraft\mods. macOS:
~/Library/Application Support/minecraft/mods.Full walkthrough: installing on Forge 1.20.1 step by step.
This button downloads a community archive of The Broken Script hosted on GitHub, a ZIP of roughly 0.4 MB.
Unzip it and open index.html to see the archived Forge 1.20.1 builds, from the v0.71 beta to
1.9.3, each with its size and its own download link.
Community-maintained archive, not a listing from the mod's developer. Builds marked unsafe show a warning first. Scan files before running them and read the safety notice.
1.9.3 Forge 1.20.1, 86.1 MB
Notes as listed in the community archive. Full version history
Newest Shows a warning before download
Fix: use Minecraft 1.20.1 with Forge for 1.20.1. Other versions will not load these builds.
Fix: launch the Forge profile and put the build .jar, not the archive ZIP, in that profile's mods folder.
Fix: remove extra copies. Keep one Broken Script jar.
Fix: raise the profile's memory, often to around 4 GB.
Fix: disable entity block breaking in the mod's config.
Fix: it is a Forge mod. Use a separate Forge 1.20.1 instance.
More detail in the crash fixes guide.
A Minecraft mod runs with the same access as the game, and some archived builds of this mod are labelled unsafe by the community archive. Play it smart:
It is a horror mod for Minecraft: Java Edition. It adds hostile and unexplained entities, random scripted events, unusual structures and corrupted visual effects to a normal survival world. Most of its behaviour can be switched on or off from an in-game configuration menu.
Every build listed in the community archive is labelled for Minecraft 1.20.1. If you try to load it on another game version, Forge will normally refuse to start or report a version mismatch.
Yes. The archived builds are Forge mods, so you need a Forge installation for Minecraft 1.20.1 before the mod can load.
No Fabric build is listed in the archive, and we have not found one documented elsewhere. A Forge jar placed in a Fabric profile will not load. If you see a file claiming to be a Fabric port, check carefully who made it before running it.
No. It is a Java Edition mod, and Java mods cannot run on Minecraft: Bedrock Edition, which includes the mobile version people often call MCPE. Bedrock add-ons that borrow the name are separate projects.
The CurseForge page of a community add-on for the mod states that the 1.20.1 Forge version of The Broken Script is not available on CurseForge, and points to Modrinth instead. You can still add the jar manually to a Forge 1.20.1 profile in the CurseForge app.
The button downloads a small ZIP of a community archive hosted on GitHub. It contains an index page listing archived builds from the v0.71 beta to 1.9.3, each with its own file size and download link, plus datamined structure files. It is not the mod jar itself.
For most players the newest listed build, thebrokenscript-1.9.3-forge-1.20.1, is the sensible choice. Older builds are mainly useful for comparing versions or replaying an earlier experience. The archive marks some builds as safe, even safer or unsafe, and shows a warning before unsafe ones.
Place the .jar file in the mods folder of your Forge 1.20.1 game directory, then start Minecraft with the Forge profile. Do not unzip the jar and do not drop the archive ZIP into the mods folder.
No. This is an independent reference site. It is not affiliated with the developer of The Broken Script, Mojang Studios or Microsoft, and it does not host the mod files.
The archive lists some builds with an unsafe label, including a community patch of 1.9.1 and the plain 1.9 build, and shows a warning before you can download them. The archive does not explain the label in detail, so treat unsafe builds as the most aggressive variants, play them only in a separate instance and back up anything you care about first.
Any jar you download runs code on your computer, so the source matters. Prefer files from places you trust, scan downloads with your security software, keep the mod in its own launcher profile and avoid re-uploads that bundle installers or ask for extra permissions.
Yes. The mod has an in-game configuration menu with options for entity spawning, events, structures and whether entities can break blocks. A community add-on called The Broken Script Patches changes the default values of these options so the mod starts out less destructive.
The Broken Script Patches add-on lists 55 random events and offers a config option for each one. The exact number in your game can differ between versions of the main mod.
It can. The configuration includes an option for entities breaking blocks, which tells you that terrain changes are part of the design. Play in a new world or keep a backup of the save folder before you start.
Technically you can load an existing 1.20.1 world with the mod installed, but structures and world changes are designed around new exploration. Copy the world first so you can return to the untouched version.
Corrupted visuals are part of the mod's atmosphere, and the moon texture is one of them. The Patches add-on even includes an option to bring back the mod's older corrupted moon textures.
Plenty of players record it. If you want more control on camera, The Broken Script Patches was made with content creators in mind and lets you start with entities, events and structures disabled, then enable them as you go.
Recent archived builds are around 86 MB, much larger than early versions. For a Forge 1.20.1 profile with this mod, 4 GB of allocated RAM is a common starting point, rising if you add shaders or other large mods.
Delete the jar from the mods folder. When you reopen a world that was played with the mod, Forge may warn about missing blocks or entities. Their content will be removed from that save, so keep a copy if you might want to go back.