Proposal to add gamerule to disable "Confirm command execution"

(Translator used.)

The clickEvent function has become seriously difficult to use. Many people are complaining about the inconvenience because a warning message is always displayed unless a trigger is used to bypass it. It is different from the numerous command structure changes that existed before. They were done for the purpose of adding functionality (eg: CustomModelData related) or consistency of names (eg: clickEvent->click_event), but the warning message is not. There is a way to bypass it through the trigger command, but this requires several times more commands, is much harder to use than the existing method, and makes the game much less attractive.

I sincerely hope that the next minor update will include disabling the Confirm Command Execution screen in the near future.