RunService

The Heartbeat event fires every frame, after the physics simulation has completed. The step argument indicates the time that has elapsed since the previous frame.

As Heartbeat fires every frame, it runs on a variable frequency. This means the rate will vary depending on the performance of the machine. If the game is running at 40 FPS, then Heartbeat will fire 40 times per second and the step argument will be roughly 1/40th of a second.

The step argument can be used to account for the variable frequency of this event, for example:

1local RunService = game:GetService("RunService")
2
3local RATE_PER_SECOND = 2
4
5RunService.Heartbeat:Connect(function(step)
6	local increment = RATE_PER_SECOND * step
7end)
8

There is no guarantee that functions connected to this event will fire at the exact same time, or in any specific order. For an alternative where the priority can be specified, see RunService:BindToRenderStep().

The RenderStepped event fires every frame, prior to the frame being rendered. The step argument indicates the time that has elapsed since the previous frame.

RenderStepped does not run in parallel to Roblox's rendering tasks and code connected to RenderStepped must be executed prior to the frame being rendered. This can lead to significant performance issues if RenderStepped is used inappropriately. To avoid this, only use RenderStepped for code that works with the camera or character. Otherwise, RunService.Heartbeat should be used.

As RenderStepped fires every frame, it runs on a variable frequency. This means the rate will vary depending on the performance of the machine. If the game is running at 40 FPS, then RenderStepped will fire 40 times per second and the step argument will be roughly 1/40th of a second.

The step argument can be used to account for the variable frequency of this event, for example:

1local RunService = game:GetService("RunService")
2
3local RATE_PER_SECOND = 2
4
5RunService.RenderStepped:Connect(function(step)
6	local increment = RATE_PER_SECOND * step
7end)
8

There is no guarantee that functions connected to this event will fire at the exact same time, or in any specific order. For an alternative where the priority can be specified, see RunService:BindToRenderStep().

As RenderStepped is client-side only, it can be used in a LocalScript or a ModuleScript required by a LocalScript.

The Stepped event fires every frame prior to the physics simulation. The step argument indicates the time that has elapsed since the previous frame.

As Stepped fires every frame, it runs on a variable frequency. This means the rate will vary depending on the performance of the machine. If the game is running at 40 FPS, then Stepped will fire 40 times per second and the step argument will be roughly 1/40th of a second.

The step argument can be used to account for the variable frequency of this event, for example:

1local RunService = game:GetService("RunService")
2
3local RATE_PER_SECOND = 2
4
5RunService.Stepped:Connect(function(time, step)
6	local increment = RATE_PER_SECOND * step
7end)
8

There is no guarantee that functions connected to this event will fire at the exact same time, or in any specific order. For an alternative where the priority can be specified, see RunService:BindToRenderStep().

The BindToRenderStep function binds a custom function to be called at a specific time during the render step. There are three main arguments for BindToRenderStep: name, priority, and what function to call.

As it is linked to the client's rendering process, BindToRenderStep can only be called on the client.

Name

The name parameter is a label for the binding, and can be used with RunService:UnbindFromRenderStep() if the binding is no longer needed.

1local RunService = game:GetService("RunService")
2
3local function functionToBind() end
4
5-- Bind the function above to the binding named "tempBinding"
6RunService:BindToRenderStep("tempBinding", 1, functionToBind)
7-- Unbind the function bound to "tempBinding"
8RunService:UnbindFromRenderStep("tempBinding")
9

Priority

The priority of the binding is an integer, and determines when during the render step to call the custom function. The lower this number, the sooner the custom function will be called. If two bindings have the same priority the Roblox engine will randomly pick one to run first. The default Roblox control scripts run with these specific priorities:

• Player Input: 100
• Camera Controls: 200 For convenience, the RenderPriority enum can be used to determine the integer value to set a binding. For example, to make a binding right before the default camera update, simply subtract 1 from the camera priority level.

When using Enum.RenderPriority, remember to use InlineCode.Value at the end of the desired enum. BindToRenderStep will not work if just the enum on its own is used.

1local RunService = game:GetService("RunService")
2
3local function beforeCamera(delta)
4	-- Code in here will run before the default Roblox camera script
5end
6
7RunService:BindToRenderStep("Before camera", Enum.RenderPriority.Camera.Value - 1, beforeCamera)
8

Custom Function and Delta Time

The last argument of BindToRenderStep is the custom function to call. This function will be passed one parameter called deltaTime. DeltaTime shows how much time passed between the beginning of the previous render step and the beginning of the current render step.

All rendering updates will wait until the code in the render step finishes. Make sure that any code called by BindToRenderStep runs quickly and efficiently. If code in BindToRenderStep takes too long, then the game visuals will be choppy.

This function returns whether the current environment is running on the client.

If the code that invoked this method is running in a client context (in a LocalScript or a ModuleScript required by a LocalScript) then this method will return true. In all other cases, this function will return false.

If this function returns true, then the current environment can access client-only features like RunService.RenderStepped or Players.LocalPlayer.

RunService test function results

See also:

• RunService:IsServer()
• RunService:IsStudio()
• RunService:IsEdit()
• RunService:IsRunning()
• RunService:IsRunMode()

This function returns whether the current environment is in 'Edit' mode. For example, Roblox Studio is in 'Edit Mode' when the game is not running.

IsEdit will return the inverse of RunService:IsRunning() with one exception, if the simulation has been 'paused' then both IsEdit and RunService:IsRunning() will return false.

See also:

• RunService:IsClient()
• RunService:IsServer()
• RunService:IsStudio()
• RunService:IsRunning()
• RunService:IsRunMode()

This function returns whether the 'Run' button has been pressed to run the simulation in Roblox Studio.

If the user has pressed 'Run', then this function will return true. This function will continue to return true if the simulation has been paused using the 'Pause' button. However, once it has been stopped using the 'Stop' button it will revert to returning false.

Roblox Studio only enters run mode when the 'Run' button is pressed, not the 'Play' button. This function will also return false if the simulation was started using RunService:Run() rather than the 'Run' button.

RunService test function results

See also:

• RunService:IsClient()
• RunService:IsServer()
• RunService:IsStudio()
• RunService:IsRunning()
• RunService:IsEdit()

Returns whether the game is currently running

The game is considered running when it is not in edit mode in Roblox Studio. This means, if the simulation has been run using the 'Run' or 'Play' buttons the game is running.

IsRunning will always return the inverse of RunService:IsEdit() with one exception, if the simulation has been 'paused' then both RunService:IsEdit() and IsRunning will return false.

RunService test function results

See also:

• RunService:IsClient()
• RunService:IsServer()
• RunService:IsStudio()
• RunService:IsEdit()
• RunService:IsRunMode()

This function returns whether the current environment is running on the server.

If the code that invoked this method is running in a server context (in a Script or a ModuleScript required by a Script) then this method will return true. In all other cases, this function will return false.

If this function returns true, then the current environment can access server-only features like ServerStorage or ServerScriptService.

See also:

• RunService:IsClient()
• RunService:IsStudio()
• RunService:IsEdit()
• RunService:IsRunning()
• RunService:IsRunMode()

This function returns whether the current environment is running in Roblox Studio.

This function will only return true when using Roblox Studio and can be used to add code to test your game within Studio.

See also:

• RunService:IsClient()
• RunService:IsServer()
• RunService:IsStudio()
• RunService:IsEdit()
• RunService:IsRunMode()

This function pauses the games' simulation if it is running, suspending physics and scripts.

The simulation can be started using RunService:Run() or the 'Run' button in Roblox Studio. When the simulation is paused, RunService:IsRunning() will return false.

Pausing the simulation can be used to assist with debugging in Roblox Studio, it cannot be used in real game sessions.

See also:

• RunService:IsRunning()
• RunService:Run()
• RunService:Stop()

This function runs the game's simulation, running physics and scripts.

When the simulation is running, RunService:IsRunning() will return true. However, RunService:IsRunMode() will only return true if the simulation was started using the 'Run' button in Roblox Studio. This means when this function is used to start the simulation, IsRunMode will return false even though the simulation is running.

The simulation can be paused using RunService:Pause() or the 'Pause' button in Roblox Studio. It can also be ended using RunService:Stop().

Running the simulation can be used to assist with debugging in Roblox Studio. Currently it is not possible to restore the game to the state it was in prior to running the simulation if the simulation was started using this function. If this is a problem, instead use the 'Run' button in Roblox Studio.

See also:

• RunService:IsRunning()
• RunService:Pause()
• RunService:Stop()

This function ends the game's simulation if it is running.

The simulation can be started using RunService:Run() or the 'Run' button in Roblox Studio. When the simulation is stopped, RunService:IsRunning() will return false and RunService:IsEdit() will return true.

In contrast to the 'Stop' button in Roblox Studio, calling this function will not restore the game to the state it was in prior to the simulation being run. This means any changes made to the game by the physics simulation and scripts will persist after the simulation has ended.

See also:

• RunService:IsRunning()
• RunService:Run()
• RunService:Pause()

Given a name of a function sent to BindToRenderStep, this method will unbind the function from being called during RenderStepped. This is used to unbind bound functions once they are no longer needed, or when they no longer need to fire every step.

If there is no bound function by the given name, this method raises an error. You can prevent such an error from being raised by using pcall. For example, if you bind a function named drawImage using BindToRenderStep, the following code would unbind the function, suppressing errors if there wasn't already a function with the name drawImage bound.

1local RunService = game:GetService("RunService")
2
3local success, message = pcall(function() RunService:UnbindFromRenderStep("drawImage") end)
4if success then
5	print("Success: Function unbound!")
6else
7	print("An error occurred: "..message)
8end
9```"
10