setInterval - Revision history

Vortrex at 13:56, 3 February 2024

2024-02-03T13:56:53Z

← Older revision		Revision as of 13:56, 3 February 2024
Line 13:		Line 13:
	\|returnInfo = a handle to the timer		\|returnInfo = a handle to the timer
	\|returnFail1 = null n/a		\|returnFail1 = null n/a
	\|notes = GTA Connected guarantees that the timer will be triggered after at least the interval you specify. The resolution of the timer is tied to the frame rate (server side and client-side). All the overdue timers are triggered at a single point each frame. This means that if, for example, the player is running at 30 frames per second, then two timers specified to occur after 100ms and 110ms would more than likely occur during the same frame, as the difference in time between the two timers (10ms) is less than half the length of the frame (33ms). As with most timers provided by other languages, you shouldn't rely on the timer triggering at an exact point in the future.		\|notes = GTA Connected guarantees that the timer will be triggered ''after'' at least the interval you specify. The resolution of the timer is tied to the frame rate (server side and client-side). All the overdue timers are triggered at a single point each frame. This means that if, for example, the player is running at 30 frames per second, then two timers specified to occur after 100ms and 110ms would more than likely occur during the same frame, as the difference in time between the two timers (10ms) is less than half the length of the frame (33ms). As with most timers provided by other languages, you shouldn't rely on the timer triggering at an exact point in the future.
	}}		}}

Vortrex at 13:56, 3 February 2024

2024-02-03T13:56:40Z

← Older revision		Revision as of 13:56, 3 February 2024
Line 13:		Line 13:
	\|returnInfo = a handle to the timer		\|returnInfo = a handle to the timer
	\|returnFail1 = null n/a		\|returnFail1 = null n/a
	\|notes = GTA Connected guarantees that the timer will be triggered after at least the interval you specify. The resolution of the timer is tied to the frame rate (server side and client-side). All the overdue timers are triggered at a single point each frame. This means that if, for example, the player is running at 30 frames per second, then two timers specified to occur after 100ms and 110ms would more than likely occur during the same frame, as the difference in time between the two timers (10ms) is less than half the length of the frame (33ms). As with most timers provided by other languages, you shouldn't rely on the timer triggering at an exact point in the future.		\|notes = GTA Connected guarantees that the timer will be triggered after at least the interval you specify. The resolution of the timer is tied to the frame rate (server side and client-side). All the overdue timers are triggered at a single point each frame. This means that if, for example, the player is running at 30 frames per second, then two timers specified to occur after 100ms and 110ms would more than likely occur during the same frame, as the difference in time between the two timers (10ms) is less than half the length of the frame (33ms). As with most timers provided by other languages, you shouldn't rely on the timer triggering at an exact point in the future.
	}}		}}

Vortrex at 01:44, 31 January 2024

2024-01-31T01:44:17Z

← Older revision		Revision as of 01:44, 31 January 2024
Line 13:		Line 13:
	\|returnInfo = a handle to the timer		\|returnInfo = a handle to the timer
	\|returnFail1 = null n/a		\|returnFail1 = null n/a
			\|notes = GTA Connected guarantees that the timer will be triggered after at least the interval you specify. The resolution of the timer is tied to the frame rate (server side and client-side). All the overdue timers are triggered at a single point each frame. This means that if, for example, the player is running at 30 frames per second, then two timers specified to occur after 100ms and 110ms would more than likely occur during the same frame, as the difference in time between the two timers (10ms) is less than half the length of the frame (33ms). As with most timers provided by other languages, you shouldn't rely on the timer triggering at an exact point in the future.
	}}		}}

Mex at 20:03, 8 May 2020

2020-05-08T20:03:21Z

New page

{{ScriptItem
|endpoint = shared
|type = function
|name = setInterval
|parameters = function callback, int durationMilliseconds, [ ... ]
|parameter1 = int durationMilliseconds The interval, in milliseconds, to call the scripting function.
|parameter2 = function callback The scripting function to call when each interval has occurred.
|parameter3 = vararg ... optional n/a The arguments to send to the callback function.
|callback2Syntax = [...]
|callback2Parameter1 = ... vararg The arguments that were sent to the <code>setInterval</code> function.
|returnTypes = Timer
|usage = add a timer with a callback function that is invoked each time the specified duration has passed
|returnInfo = a handle to the timer
|returnFail1 = null n/a
}}