Minecraft 2025 Wishlist

Things I wish to come to the Bedrock APIs

Author: SmokeyStack

Published: 21st December 2024

2024 is almost over!

2024 has been an incredible year for Minecraft Bedrock, especially for creators. However, despite Mojang's efforts on churning out new APIs for creators, there are still some things that are missing that I greatly wish to see arrive in 2025. It will be divided into three sections: blocks, items, miscellaneous. The first two category will have 10 things and the last will have 5 that I wish to come in no particular order. These are things I thought of whether it was Marketplace work, chatting with a friend or personal projects.

Blocks

1. Block Dynamic Properties

Block Dynamic Properties is something I've always wanted. World, Items, and Entities all have dynamic property support. Dynamic property support essentially allows you to store data dynamically. In a way, we can use this mechanic to mimic block entities.

2. Biome Tinting Support

Biome tinting support is something we need for things like custom foliage. I suspect we'll get it sooner than later due to items recently getting support for being dyeable which is essentially the same technology(not really).

3. Distance Based Rendering

This one is a big issue for custom leaves. Currently, there is no way to change a custom block's rendering method based on distance. Due to this, custom leaf blocks that use alpha_test will unrender when you're more than 70 blocks away which can lead to ugly visuals such as leafless trees. Vanilla leaves will fallback to an opaque texture so that it can still be viewed when you're out of the alpha_test render distance.

4. Multi-Collision Hitboxes

Multi-collision boxes are what is used for blocks such as stairs and cauldrons. Instead of their hitbox being one cube that is scaled in different axes, their hitbox can be made of multiple cubes allowing unique collision boxes.

5. Solidity

Yes, custom blocks are not solid, which means mobs can't spawn on it for example. We just need a way to define solidity again for custom blocks.

6. Redstone Support

Self-explanatory, just need blocks to be able to interact with the redstone system.

7. Better Placement Filter

The current placement filter is so tedious. It requires you to either define every block or use block tags. And since not all blocks have block tags, you usally have to use a combination of the two. Here is a link to a feedback post in the official feedback discord where I go over in detail what I propose a better placement filter is.

8. Double Block Support

We need easier double block support so we can create blocks such as doors and tall flowers.

9. Block To Block Communication

This one is a niche feature in my opinion, but having the ability for Block A to tell Block B to do x would open up more possibilities for machinery add-ons.

10. Client Block File

I really want this, but I highly doubt it will happen. But splitting the block JSON file into client and server files instead of everything being defined in the behaviour pack. It makes no sense to me that the geometry and textures of a block is defined in the behaviour pack.

Items

1. onBeforeDurabilityDamage Applying to all Damage Sources

This is really a scripting thing, but only custom items can use it so I'm counting it as items. We have the ability to modify or cancel if an item takes durability damage only if it is taking damage from hitting an entity. I want this to expand to other damage sources such as when you're equipping the item as armour and it takes damage. This will be useful to create something like the elytra where it can never break.

2. Texture Based on Durability

I wish for the ability to change an item's texture based on how much durability it has left similar to the elytra or brush.

3. Elytra Component

Just give us the ability to make a custom elytra.

4. Custom Trims

I want to be able to make my own custom trims without overriding vanilla ones. This gives add-ons a more unique experience to give to players.

5. Custom Enchantments

Self-explanatory, the ability to register custom enchantments for our custom items.

6. Weapon Reach

This will likely only come when Combat v3 is released, but having the ability for weapons to have different reach creates a more unique experience.

7. Animated Item Textures

Animated Item Textures would be amazing. Currently there is no way to do so without using flipbook blocks or attachables(and even then this is bugged).

8. Actual Custom Music Discs

This one seriously baffles me, we have the ability to define an item is a music disc via the minecraft:record component...but we're only allowed to use vanilla sounds. What we need is to be allowed to use custom sounds, that's the whole point of custom music discs.

9. Item Properties

While items do have dynamic properties, they're not the same as normal properties and thus cannot be queried by the client. Very useful to have an item render in different states depending on certain conditions.

10. Custom Descriptions

You might have noticed some vanilla items have additional text below its name such as music discs, enchantments, etc. While we can set our own descriptiong using the ScriptAPI, it won't work if it's in the creative menu.

Miscellaneous

1. Custom Components Parameters

This is easily my most requested feature I want. Right now, custom components kind of act like tags rather than actual components.

2. Loot Table Parity

Java has some loot table functionality and conditions that Bedrock does not. I do wish for them to come to Bedrock so we can make our blocks have better loot tables.

3. Custom Biomes

This one is a big one. I doubt it will come in 2025 but having this will be a huge advancement for add-ons.

4. Custom Advancements

A sort of advancement system for add-ons to have including the toast pop up.

5. Remove Runtime Identifiers

Runtime identifiers are essentially used to give custom entities some vanilla entities hardcoded behaviour. Projectiles are the worst offenders of this case with dolphins being a close second. If you copy/paste the vanilla files, it will not work the same. The moment you add the runtime identifier, then it will act exactly the same as the vanilla ones. The downsides of course it brings all the vanilla hardcoded which you might not want. I want this feature remove and for Mojang to fully fully data drive entity behaviours.

Conclusion

That's all folks! Thanks for reading my wishlist for what I want to come in 2025. If by some rare chance you're a Mojangster reading this, I just ask you don't put all of them in the backburner or under the "NEVER GIVE THESE TO BEDROCK CREATORS" pile. Hope you all had a wonderful 2024, let's see what 2025 brings us.