GetTickCount - Revision history

Srslyyyy: Improve example.

2021-09-12T11:54:33Z

Improve example.

← Older revision		Revision as of 11:54, 12 September 2021
Line 46:		Line 46:
	This example will start a timer displayed at the top of the screen displayed every frame. You can log any specific moment in time by outputting the currentCount variable.		This example will start a timer displayed at the top of the screen displayed every frame. You can log any specific moment in time by outputting the currentCount variable.

	<syntaxhighlight lang="lua">screenX,screenY = guiGetScreenSize()		<syntaxhighlight lang="lua">
	~~function startTheClock ()~~		local firstColor = tocolor(0, 0, 0, 150)
			local secondColor = tocolor(255, 255, 255, 255)
	~~if not systemUpTime then~~		local screenX, screenY = guiGetScreenSize()
	systemUpTime = getTickCount() --Store the system tick count, this will be 0 for us		local currentCount = 0
	~~end~~		local systemUpTime = getTickCount() -- Store the system tick count, this will be 0 for us

			function onClientRenderClock()
	currentCount = getTickCount()		currentCount = getTickCount()

	dxDrawRectangle (screenX .40, screenY .09, 250, 50, ~~tocolor(0,0,0,150)~~)		dxDrawRectangle(screenX .40, screenY .09, 250, 50, firstColor)
	dxDrawText (currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, ~~tocolor(255,255,255)~~, 2)		dxDrawText(currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, secondColor, 2)
	end		end
	addEventHandler ("onClientRender", root, ~~startTheClock~~)		addEventHandler("onClientRender", root, onClientRenderClock)
	</syntaxhighlight>		</syntaxhighlight>

Pirulax at 14:04, 4 February 2021

2021-02-04T14:04:13Z

← Older revision		Revision as of 14:04, 4 February 2021
Line 2:		Line 2:
	{{Server client function}}		{{Server client function}}
	This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[getTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.		This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[getTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.

			{{Server client function}}{{Important Note\|The value returned by this function client-side may not be reliable if a client is maliciously modifying their operating system speed.}}

	==Syntax==		==Syntax==

Dutchman101: added example

2020-08-29T10:40:33Z

added example

← Older revision		Revision as of 10:40, 29 August 2020
Line 10:		Line 10:

	==Example==		==Example==
	This will start a timer displayed at the top of the screen displayed every frame. You can log any specific moment in time by outputting the currentCount variable.		The below code is a good example on how to implement basic anti-spam protection for a command, for which using getTickCount is better than the regular timer functions.
			<syntaxhighlight lang="lua">
			local spam = {}

			function setSkin(player, cmd, skin)
			if spam[player] and getTickCount() - spam[player] < 4000 then
			return outputChatBox("You cannot change skin that often!", player, 255, 0, 0)
			end

			skin = skin and tonumber(skin)

			if getElementModel(player) == skin or isPedDead(player) then
			return
			end

			if skin and skin <= 99999 then -- what do we know about dynamic ped ID range?
			setElementModel(player, skin)
			spam[player] = getTickCount()
			else
			outputChatBox("Invalid skin ID!", player, 255, 0, 0)
			end
			end
			addCommandHandler("skin", setSkin)

			function cleanUp()
			if spam[source] then
			spam[source] = nil
			end
			end
			addEventHandler("onPlayerQuit", root, cleanUp)
			</syntaxhighlight>

			This example will start a timer displayed at the top of the screen displayed every frame. You can log any specific moment in time by outputting the currentCount variable.

	<syntaxhighlight lang="lua">screenX,screenY = guiGetScreenSize()		<syntaxhighlight lang="lua">screenX,screenY = guiGetScreenSize()
Line 16:		Line 48:

	if not systemUpTime then		if not systemUpTime then
	systemUpTime = getTickCount () --Store the system tick count, this will be 0 for us		systemUpTime = getTickCount() --Store the system tick count, this will be 0 for us
	end		end

	currentCount = getTickCount ()		currentCount = getTickCount()

	dxDrawRectangle (screenX .40, screenY .09, 250, 50, tocolor(0,0,0,150))		dxDrawRectangle (screenX .40, screenY .09, 250, 50, tocolor(0,0,0,150))
	dxDrawText ( currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, tocolor(255,255,255), 2)		dxDrawText (currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, tocolor(255,255,255), 2)
	end		end
	addEventHandler ( "onClientRender", root, startTheClock )</syntaxhighlight>		addEventHandler ("onClientRender", root, startTheClock)
			</syntaxhighlight>

	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}
	[[ru:GetTickCount]]		[[ru:GetTickCount]]

Yoodie at 12:00, 27 February 2020

2020-02-27T12:00:20Z

← Older revision		Revision as of 12:00, 27 February 2020
Line 28:		Line 28:
	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}
			[[ru:GetTickCount]]

Dustin Wouldn't you like to know: /* Example */

2012-12-29T18:21:43Z

Example

← Older revision		Revision as of 18:21, 29 December 2012
Line 24:		Line 24:
	dxDrawText ( currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, tocolor(255,255,255), 2)		dxDrawText ( currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, tocolor(255,255,255), 2)
	end		end
	addEventHandler ( "onClientRender", root, startTheClock )		addEventHandler ( "onClientRender", root, startTheClock )</syntaxhighlight>

	~~startTheClock(~~)</syntaxhighlight>

	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}

Ransom: /* Example */ new example

2012-09-29T21:23:10Z

Example: new example

← Older revision		Revision as of 21:23, 29 September 2012
Line 10:		Line 10:

	==Example==		==Example==
	This ~~example shows how you~~ can ~~benchmark some code to see how long it takes to run~~.		This will start a timer displayed at the top of the screen displayed every frame. You can log any specific moment in time by outputting the currentCount variable.
	~~<syntaxhighlight lang="lua">local getTickStart = getTickCount ()~~

	-- ~~Insert your code here~~		<syntaxhighlight lang="lua">screenX,screenY = guiGetScreenSize()
			function startTheClock ()

			if not systemUpTime then
			systemUpTime = getTickCount () --Store the system tick count, this will be 0 for us
			end

			currentCount = getTickCount ()

			dxDrawRectangle (screenX .40, screenY .09, 250, 50, tocolor(0,0,0,150))
			dxDrawText ( currentCount - systemUpTime, screenX * .48, screenY * .1, screenX, screenY, tocolor(255,255,255), 2)
			end
			addEventHandler ( "onClientRender", root, startTheClock )

	~~local getTickEnd = getTickCount~~ ()		startTheClock()</syntaxhighlight>
	~~outputChatBox ( "Time elapsed: " .. getTickEnd - getTickStart .. " milliseconds"~~ )</syntaxhighlight>

	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}

Norby89 at 16:22, 10 August 2007

2007-08-10T16:22:22Z

← Older revision		Revision as of 16:22, 10 August 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
			{{Server client function}}
	This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[getTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.		This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[getTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.

Line 10:		Line 11:
	==Example==		==Example==
	This example shows how you can benchmark some code to see how long it takes to run.		This example shows how you can benchmark some code to see how long it takes to run.
	<syntaxhighlight lang="lua">getTickStart = getTickCount ( )		<syntaxhighlight lang="lua">local getTickStart = getTickCount ()

	-- Insert your code here		-- Insert your code here

	getTickEnd = getTickCount ( )		local getTickEnd = getTickCount ()
	outputChatBox ( "Time elapsed: " .. ~~GetTickEnd~~ - ~~GetTickStart~~ .. " milliseconds" )</syntaxhighlight>		outputChatBox ( "Time elapsed: " .. getTickEnd - getTickStart .. " milliseconds" )</syntaxhighlight>

	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}

Jbeta at 16:23, 11 March 2007

2007-03-11T16:23:15Z

← Older revision		Revision as of 16:23, 11 March 2007
Line 1:		Line 1:
	~~{{Needs_Checking\|Unspecified}}~~

	__NOTOC__		__NOTOC__
	This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[~~GetTickCount~~]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.		This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[getTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.

	==Syntax==		==Syntax==
Line 8:		Line 6:

	===Returns===		===Returns===
	Returns an integer containing the number of milliseconds since the system the server is running on started. This has the potential to wrap-around ~~'''(needs confirming when and what the result is)~~.~~'''~~		Returns an integer containing the number of milliseconds since the system the server is running on started. This has the potential to wrap-around.

	==Example==		==Example==

Ransom at 04:10, 10 September 2006

2006-09-10T04:10:10Z

← Older revision		Revision as of 04:10, 10 September 2006
Line 1:		Line 1:
			{{Needs_Checking\|Unspecified}}

	__NOTOC__		__NOTOC__
	This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[GetTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.		This function returns amount of time that your system has been running in milliseconds. By comparing two values of [[GetTickCount]], you can determine how much time has passed (in milliseconds) between two events. This could be used to determine how efficient your code is, or to time how long a player takes to complete a task.
Line 19:		Line 21:
	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}
	~~[[Category:Needs Checking]]~~

EAi: /* Example */

2006-08-14T11:09:21Z

Example

← Older revision		Revision as of 11:09, 14 August 2006
Line 9:		Line 9:

	==Example==		==Example==
	<syntaxhighlight lang="lua">~~GetTickStart~~ = getTickCount ( )		This example shows how you can benchmark some code to see how long it takes to run.
	Insert ~~custom~~ code here~~...~~		<syntaxhighlight lang="lua">getTickStart = getTickCount ( )
	~~GetTickEnd~~ = getTickCount ( )
	outputChatBox ( "Time elapsed:", GetTickEnd - GetTickStart )</syntaxhighlight>		-- Insert your code here

			getTickEnd = getTickCount ( )
			outputChatBox ( "Time elapsed: " .. GetTickEnd - GetTickStart .. " milliseconds" )</syntaxhighlight>

	==See Also==		==See Also==
	{{Utility functions}}		{{Utility functions}}
	[[Category:Needs Checking]]		[[Category:Needs Checking]]