Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
guidelines:adding_message_to_gamebots [2012/02/08 21:27] martin.cerny |
guidelines:adding_message_to_gamebots [2012/02/08 21:34] martin.cerny |
||
---|---|---|---|
Line 95: | Line 95: | ||
In your handler method, you are free to use method GetArgVal(argName) to parse command arguments (it is automagically filled with arguments from most recent command. | In your handler method, you are free to use method GetArgVal(argName) to parse command arguments (it is automagically filled with arguments from most recent command. | ||
+ | |||
+ | If you want to handle commands for the control connection, the process is the same, but use ControlConnection instead of BotConnection. | ||
====== Triggering Kismet event with a command ====== | ====== Triggering Kismet event with a command ====== | ||
Line 162: | Line 164: | ||
The ConnectionClass is a string containing fully qualified name of the connection class. If you are not trying to achieve something complicated, | The ConnectionClass is a string containing fully qualified name of the connection class. If you are not trying to achieve something complicated, | ||
- | If you have done that, try running UDK with GameBots as usual you should see "Using YOURCLASS for connection" | + | If you have done that, try running UDK with GameBots as usual you should see "Using YOURCLASS for bot connection" |
+ | |||
+ | In a similar way you can replace the default implementation of ControlConnection to parse custom messages. You extend the ControlConnection class, override ProcessRegularAction there, create file called DefaultControlServer.ini and specify your class' | ||