Feature: config to prevent implicit sending to server

[vglocus]

If I have a complex set of aliases calling each other and I misspell something (eg a refactoring didn't take everywhere) then the now-not-alias call will be sent to the server instead.

In order to prevent any accidental sending to the server (you might be playing a MUD with strict trigger rules, or spam might cause dangerous in game situations) I would like a config that when enabled will only send to the server when using send from within an action/alias/function/trigger/etc context.

For example

#alias my-alias { 
  another-alias {1, 2, 3};
  drop axe;
}

Currently, if another-alias does not exist this will be unintentionally sent to the MUD server.

With this wished for config enabled, one would have to

#alias my-alias { 
  another-alias {1, 2, 3};
  #send {drop axe};
}

But in return a missing another-alias would not be unintentionally entered as a command.

Bonus would be that if this happens a debug message like "alias not found" or to a similar effect would be posted to the user.

This would enable those who prefer to run scripts in a safer mode.

[scandum]

Try:

#alias {%*} {#showme <118>alias (%0) not found.} {9}