#samp timers

10 messages · Page 1 of 1 (latest)

red loom
#

As far as I understand (checked) there is a limit on timers (not simultaneously working, but in general. Because each id is unique) According to my calculations, I will run into this limit.
I tried using the plugin:
https://github.com/KashCherry/Timer-Fix-plugin
this plugin stops calling the timer after some time
Tried to use this one:
https://github.com/ziggi/samp-plugin-timerfix
But it has the disadvantage of standard timers with limits. id is also unique.

The request of all who have something to say about SAMP timers is to speak here

GitHub

This plugin makes timers more accurate. Contribute to KashCherry/Timer-Fix-plugin development by creating an account on GitHub.

GitHub

High accuracy timing events for SA-MP servers. Contribute to ziggi/samp-plugin-timerfix development by creating an account on GitHub.

distant ember
#

how do you use 2 billion timers

shadow oracle
#

actually 4

red loom
#

my server crashes after ~ id > 50_000_000

restive matrix
#

yeah, even if you set one every millisecond it will still take over three weeks to run out of ids. Servers should be restarted every two to three weeks anyway but it will likely already have restarted before that

red loom
#

more precisely the server does not fall. The new timers just don't work

#

considering that there are 1000 players and I have at least 1 timer when connecting and ~ 3 that solve samp bugs, it looks bad

fast raptor
#

How do you have 50 million timers?

And thats not the limit. You are very far from it.

red loom