Event hooks. When KAC detect something it's sending a forward where other plugins can either allow, modify or block the event (that is blocking KAC's actions).
The forward should provide:
- client index (or maybe userid)
- what type of "cheat" it detected
- what action KAC is doing by default for that type (this action should be possible to modify)
The forward can be blocked in the same way as with SM events using those Plugin_* states. Cheat type and actions done by KAC are defined in their own enumerations in the KAC's include file.
Maybe even make use of the SM's event system by creating and sending your custom events?
__________________