The project is not meant to be a large mod. It is a rules sandbox.

What it changes

The pack includes features such as:

• sprint regeneration
• random player effects
• torch drops on non-player entity death
• local snow effect on player death
• random material drops from broken blocks
• adjusted fishing loot weights

These are intentionally playful mechanics. The point is to test how small rule changes affect the feel of a world.

Why behavior-only matters

Keeping the pack behavior-only lowers the setup cost. There is no custom client asset pipeline and no experimental toggle requirement.

That makes it easier to share across devices:

• package as .mcpack
• import on iOS or Windows
• activate in world settings
• play immediately

For a small personal pack, install friction matters more than architectural elegance.

The design lesson

Game modding is a good reminder that systems can be fun without being complicated. A simple rule like “breaking blocks produces random materials” changes the entire resource economy.

The engineering lesson is to make each rule easy to remove. If a mechanic stops being fun, it should not be tangled with the rest of the pack.

What I learned

Small game experiments should be packaged early. A mechanic that only works in a local development folder is not really tested. It needs to be imported, activated, and played in the actual environment.

Bedrock Lab’s value is that it turns ideas into a package quickly. That makes it easier to decide whether a mechanic is worth keeping.

Current status

Bedrock Lab is private and small. It is the kind of project that is more useful as a personal sandbox than as a maintained public mod.