There is currently no standardized way to define and handle commands in the scripting API. While the UserMessageCallback event provides basic message handling, it is too low-level to serve as a complete command system.

As a result, every script that wants to support commands must implement its own parsing, registration, permission checks, and help output. Even for simple use cases, this leads to repetitive boilerplate and inconsistent behavior between scripts.

A built-in command framework would greatly simplify script development. Even a minimal implementation consisting of a Command class and a central command registry would provide substantial value.