Datapacks lack a safe, extensible command entry point

Since Minecraft 1.13, datapacks have greatly expanded creator capabilities, but player input remains limited to indirect methods like signs, clickable text, or complex GUI flows.

Simple inputs (numbers, selectors) often require fragile workarounds such as chat parsing or scoreboard reconstruction, which are unnecessarily complex.

Proposed concept:
A sandboxed, namespaced command entry mechanism, scoped strictly to the datapack.
This is not arbitrary command registration or plugin-level access, but a declarative way to define input, validation, and execution.

Conceptual example (not final syntax):

{
  "give_cookie": {
    "arguments": { "amount": { "type": "integer", "range": "1..128" } },
    "execute": "function example:give_cookie"
  }
}

Usage:

/example give_cookie 64

This would improve datapack maintainability, reduce fragile input workarounds, and remain fully compatible with vanilla design and security principles.

Registered User commented

April 23, 2026 17:33
Edited
Report a Concern
Comment actions Permalink

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.

You are reporting this post or comment!

Datapacks lack a safe, extensible command entry point

1 Comments