- The Broken Script bedrock is a Bedrock port designed to closely follow the Java mod.
- Core content includes entities, dimensions, Null chatting, events, and additional horror elements.
- World safety matters because the addon may affect chunks, bases, farms, and other builds.
- Fog removal may use
!render_10or/fog @s pop moonglitch. - Best practice is to test the addon in a copied world before using it on a primary save.
The Broken Script bedrock Overview
The Broken Script bedrock is Makeradam’s Bedrock port of The Broken Script Java mod. Its stated goal is to remain closely aligned with the Java version rather than adding unrelated fan-made content. The CurseForge listing identifies it as an authorized port, with permission requested from RedstoneWizard08, who maintains the original Java project after Wendigodrip.
The addon is built for players who want the project’s horror atmosphere and major systems inside Minecraft Bedrock. Its current listing describes several major content groups, but it also warns that some areas still need attention. Treat the addon as an experimental horror experience rather than a low-risk decoration pack.
| Topic | Current information |
|---|---|
| Project | The Broken Script BE |
| Creator | Makeradam |
| Format | Minecraft Bedrock addon |
| Design goal | Close Java-port accuracy |
| Listed content | Entities, dimensions, Null chatting, events |
| Known concern | World griefing may occur |
Java-Port Direction
The project aims to reproduce the Java mod’s content and behavior instead of presenting a separate fan-made interpretation.
Horror Systems
Entities, unusual chat interactions, dimensions, and events form the main atmosphere described by the project listing.
Experimental State
Dimensions are listed as needing fixes, so testing and backups should be part of every installation plan.
Use a separate test world first. This makes it easier to inspect entities, events, dimensions, and visual effects without placing a primary build at unnecessary risk.
World Safety and Compatibility
The most important preparation step is protecting your save. The project listing explicitly warns that The Broken Script bedrock may grief a world, including chunks, bases, and farms. That warning affects both survival players and builders: a backup is useful, but a separate test world is safer because it limits the addon’s access to valuable progress.
Before activating the addon, copy the world and record its current condition. Note the locations of large builds, automated farms, important storage, and any areas that already use experimental features. If the test world develops broken chunks or damaged structures, remove the addon from that test environment rather than attempting to repair the original immediately.
| Risk area | What may be affected | Recommended response |
|---|---|---|
| Chunks | Loading, terrain, or area stability | Test away from important builds |
| Bases | Structures and storage areas | Use a copied world |
| Farms | Redstone or automated production | Keep a clean backup |
| Dimensions | Travel and world state | Expect unfinished behavior |
| Visual effects | Fog and atmosphere | Keep the listed commands available |
The addon is described as capable of griefing chunks, bases, and farms. Do not activate it on a valuable primary world unless you accept the possibility of damage.
A practical safety routine has three layers:
- Keep the original world untouched.
- Create a duplicate specifically for addon testing.
- Make another backup before major exploration or dimension travel.
This approach also helps identify whether a problem comes from the addon, the current world, or another active pack. Remove unrelated experimental content from the test environment whenever possible. A clean setup produces clearer results and makes troubleshooting less complicated.
Step-by-Step Bedrock Setup
The following setup flow focuses on controlled testing. It does not assume that every feature is stable, and it avoids presenting unverified version-specific instructions. Use the project’s official CurseForge page for the current file and release information: The Broken Script BE on CurseForge.
Prepare a Test World
Duplicate a world or create a new test world before activating the addon. Keep valuable bases, farms, and storage outside the test environment.
Use the Project Listing
Obtain the Bedrock addon from the project’s CurseForge page and review its current file details, notes, and compatibility information before importing it.
Activate the Addon Carefully
Enable the addon in the test world using the normal Bedrock world configuration flow. Avoid combining it with unrelated experimental packs during the first test.
Check Core Features
Explore cautiously for entities, chat behavior, events, dimensions, and fog effects. Record anything unusual before expanding the test area.
Decide Whether to Continue
If the world remains stable, continue testing with backups. If chunks, farms, or builds become damaged, leave the primary world unchanged and remove the addon from the test copy.
| Setup phase | Main objective | Stop condition |
|---|---|---|
| Backup | Preserve the original save | No backup available |
| Import | Add the project safely | File details are unclear |
| First launch | Observe baseline behavior | Immediate world damage |
| Feature test | Check entities and events | Severe instability |
| Extended test | Explore cautiously | Repeated griefing |
A clean test world, a preserved original save, and gradual exploration provide the clearest way to evaluate the addon in 2026.
Avoid rushing directly into a long survival session. First confirm that the world loads, ordinary terrain remains accessible, and the addon’s primary effects appear as expected. Test one area at a time, then exit and inspect the world again. This makes rollback decisions easier if the environment behaves unexpectedly.
Features, Fog Commands, and Troubleshooting
The project listing identifies entities, dimensions, Null chatting, events, and additional content as key features. “Mostly all entities from the Java mod” suggests broad coverage, but it does not guarantee that every entity behaves identically on Bedrock. Dimensions are also marked as needing fixes, so players should expect unfinished or inconsistent behavior during exploration.
Fog can be especially disruptive because it changes visibility and may obscure ordinary navigation. The listing provides a chat line first, followed by a command alternative if the chat line does not work.
| Issue | First action | Alternative action |
|---|---|---|
| Heavy fog | Enter !render_10 in chat | Run /fog @s pop moonglitch |
| Unclear entity behavior | Observe from a safe area | Test in a fresh copy |
| Dimension instability | Leave the area carefully | Restore the test backup |
| Damaged farm or base | Stop exploring | Use the untouched original save |
| Unusual event | Record the location | Repeat only in the test world |
If the fog remains after entering !render_10, the listing recommends trying /fog @s pop moonglitch instead. Keep both options available while testing.
For troubleshooting, change only one variable at a time. If fog disappears after the first line, do not immediately add other commands. If the command fails, check the chat syntax and then try the alternative. When a dimension or event appears unstable, return to a safe area and compare the result with a fresh test world.
The addon’s horror design may make ordinary Minecraft spaces feel unfamiliar. Build temporary shelters, keep emergency supplies separate from the main test area, and avoid placing irreplaceable items near newly generated content. These habits do not prevent every issue, but they reduce the cost of experimentation.
Best Practices and FAQ
The Broken Script bedrock works best when approached as a contained horror-mod experiment. Its Java-port objective, broad entity coverage, dimensions, Null chatting, and events create a strong foundation for atmospheric play, while the world-griefing warning requires a more careful setup than a conventional texture pack.
Before You Play:
- Create a new test world or duplicate an existing save
- Keep the primary world separate from addon testing
- Inspect entities, events, dimensions, and fog one feature at a time
- Save the fog commands for quick visual troubleshooting
- Stop testing if chunks, bases, or farms show damage
| Player type | Recommended approach | Why it fits |
|---|---|---|
| New Bedrock user | Start in a fresh world | Limits configuration risk |
| Horror fan | Explore gradually | Preserves tension without risking a main save |
| Builder | Use a disposable test map | Protects detailed structures |
| Technical player | Isolate the addon | Makes farm and chunk issues easier to identify |
Keep the first session short and observational. Learn how the addon affects your world before committing to a long survival run or a permanent build.
Q: What is The Broken Script bedrock?
It is Makeradam’s Bedrock port of The Broken Script Java mod, designed to stay closely aligned with the original project.
Q: Can the addon damage my Minecraft world?
The project listing warns that it may grief chunks, bases, and farms. Use a copied or newly created test world before trying it.
Q: What features are listed for the Bedrock port?
The listing names mostly the Java mod’s entities, dimensions, Null chatting, events, and additional content. Dimensions are also marked as needing fixes.
Q: How can I remove the fog?
Try `!render_10` in chat first. If that does not work, the listing provides `/fog @s pop moonglitch` as an alternative.