You shouldn't modify a thing when implementing TimerUtils
You
can change the configuration to your liking of course:
JASS:
private constant boolean USE_HASH_TABLE = true
private constant boolean USE_FLEXIBLE_OFFSET = false
//Timers to preload at map init:
private constant integer QUANTITY = 256
QUANTITY is the amount of timers the system will preload.
If you have a very large map, you may want to increase it to something like 512.
Keep it at 256 for now though.
If you receive errors that tell you you're out of timers, make sure you're releasing them (the timers) when they are of no use to you anymore.
If you are, then you need to increase QUANTITY.
If it's at 256 and you need more timers, set it to 384 or 512.
The other booleans control the speed.
if USE_HASH_TABLE is true, you're going for safe data attachment
else, you're going for really fast data attachment.
In my maps, I use another version of TimerUtils that creates timers dynamically so I'm never going to have more timers than I need.
It can be found here:
http://www.hiveworkshop.com/forums/graveyard-418/system-timerutilsex-204500/
I wouldn't recommend using it for public resources though.
You can only use Vexorian's TimerUtils in public.