WorldEdit Version

7.3.3

Platform Version

Fabric 0.15.11

Confirmations

• I am using the most recent Minecraft release.
• I am using a version of WorldEdit compatible with my Minecraft version.
• I am using the latest or recommended version of my platform software.
• I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
• I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

Commands allow players to place disabled blocks.

For example, on picture: Playing minecraft 1.20.6 with no extra datapacks, I can place crafter block (from 1_21_update datapack).

This is also works in minecraft 1.21, but it is harder to reproduce (there is no experiments with new blocks), but it is bad for mods, that use custom feature-flags to enable/disable content in different saves

Expected Behavior

Disabled blocks are filtered and not suggested in commands arguments

Reproduction Steps

1. Start a creative world in minecraft 1.20.6 with latest fabric and worldedit and no experiments selected
2. Try to place any block from 1_21_update experiment datapack with worldedit commands. (For example: Crafter)

Anything Else?

No response

Does it cause a crash or other performance issue? If not, I don't see why we would restrict it.

This doesn't add any functionality (you still can't interact with the placed block) and only confuses users.
If a user specifically wants to use the blocks added by a datapack, they can create a world with that datapack.
As I wrote before, mods can use feature flags and add many more blocks that will not actually be available without datapacks.

Doesn't sound like a bug. If minecraft is registering the block in the registry, and it can be modified without issue, then it sounds like everything is fine.