Shell commands ("slash commands") can not be activated programmatically, they can only be registered, unregistered and iterated programmatically.
You don't need an actual /command, you can monitor the Standard channel for anything generated with Turbine.Shell.WriteLine(). This is easier to implement than the shell command method. The major drawback to using this method is that it will display in the chat window instead of being transparent as the shell command method is. If you are sending lots of information or sending it frequently, it can be a little disruptive to the user. Unfortunately, the WriteLine method bypasses the process that evaluates ";" and "/" tokens so it can not activate shell commands. I have editted my Turbine forum post to mention this option.
Last edited by Garan : 11-26-2011 at 10:05 AM.
|