[Bacardi]

Cheking trough sm_dump_handles, TIMER_DATA_HNDL_CLOSE will close created Events.
Without TIMER_DATA_HNDL_CLOSE Handles are begin stack

*edit
Read post below. Must Cancel created Event

[Fyren]

The CreateEvent docs say not to just close the handle. I didn't look at the implementation to see why, but it may leak memory with the handle being closed.

[Powerlord]

Originally Posted by Fyren The CreateEvent docs say not to just close the handle. I didn't look at the implementation to see why, but it may leak memory with the handle being closed.

Both FireEvent / event.Fire and CancelCreatedEvent / event.Cancel will close the event handle when they finish.

In fact, you have to call one of these two methods if you've called CreateEvent or else the event handle will leak. You can't close event handles yourself because they're owned by the SourceMod core and not your plugin.

[eyal282]

Originally Posted by 1337norway This is actually a really good idea. You can pass data with custom names you give and use the native binary write system the source engine utilizes. Since sourcemod isn't freaking out about non existing event parameters and you aren't firing the event that would clog up the event system, I don't see any issue with using that. Assuming the TIMER_DATA_HNDL_CLOSE parameter is actually freeing the memory. I like it because you can define a string that represents an array index like in python.

I think Close handle is forbidden for events. Only cancel and fire.