4
Datapacks lack a safe, extensible command entry point
_54n5nbb5_
Datapacks still lack a safe, extensible way to accept player input. We've been stuck with /trigger workarounds since 1.13 — and it's showing.
I've written a detailed proposal on the official Minecraft Feedback site covering a sandboxed, namespaced command entry mechanism that stays fully within vanilla design principles:
feedback.minecraft.net/hc/en-us/community/posts/42628589887117-Datapacks-lack-a-safe-extensible-command-entry-point
If this is something you've struggled with too, please drop a vote. The more visibility it gets, the better the chance Mojang actually considers it.
I've written a detailed proposal on the official Minecraft Feedback site covering a sandboxed, namespaced command entry mechanism that stays fully within vanilla design principles:
feedback.minecraft.net/hc/en-us/community/posts/42628589887117-Datapacks-lack-a-safe-extensible-command-entry-point
If this is something you've struggled with too, please drop a vote. The more visibility it gets, the better the chance Mojang actually considers it.
2
I think in general adding a feature that allows having a kind of "shortcut" to a function that looks like a regular command to the user may make it way easier for players who are not that familiar with datapacks and especially /function to use datapacks utilizing this.
I already voted for it.
I already voted for it.
Here's hoping
(I'm not facile with that area, but this at least looks like a viable solution.)
(I'm not facile with that area, but this at least looks like a viable solution.)
