Physics

What scripts do to the simulated world.

Methods

Method	What it does
Explode(center, radius, power, options?)	Detonates a blast at `center`. Returns a table of hits, one per pushed body, each with `Instance`, `Position`, `Distance`, `Direction`, and `DeltaVelocity`.

Call it from a Script. A LocalScript raises an error instead, because a client cannot change the simulation.

center is a Vector3 in studs. radius is the blast's reach in studs. power is the speed, in studs per second, that a 1x1x1 brick gains at the epicenter. Bigger bodies get pushed proportionally less, so a wall barely lifts while loose bricks fly. Everything past radius is untouched.

options is a table, and every field has a default:

Field	Default	What it does
Falloff	Enum.BlastFalloff.Quadratic	How fast the push fades toward the edge of the radius.
UpwardBias	0.25	How much the push tilts upward, 0 to 1. High values throw debris into the air.
RespectWalls	true	When true, anchored geometry between the blast and a body blocks it.
Visual	true	Whether clients draw the fireball and the light flash.
VisualColor	warm orange	The Color3 of the explosion sphere.
FilterDescendantsInstances	empty	Instances to skip, with everything under them.

Falloff takes an Enum.BlastFalloff: Enum lists Constant, Linear, Quadratic, and Sharp. Quadratic is the default.

A raw number works too: it is the exponent on the fade curve, so 1.5 sits between Linear and Quadratic.

The return value is a table of hits, one per pushed body. Use it for damage, sounds, and scorch marks without running a second query. Each hit holds:

Field	Type	What it holds
Instance	Instance	The body that was pushed.
Position	Vector3	The point the blast applied its push to, in studs.
Distance	number	Studs from the epicenter to the body, and 0 when the epicenter sits inside it.
Direction	Vector3	The unit vector the push points along.
DeltaVelocity	Vector3	The speed change the body received, in studs per second.

Characters

A big enough blast sends a character flying. They tumble through the air, land wherever the debris and geometry leave them, stay down for about three seconds, then get back up. The tumble runs on the player’s own machine, so it looks smooth to them, and the server shares the resulting poses with everyone else.

Softer blasts don’t knock anyone over. The character gets shoved and staggers for a moment but stays on their feet. The cutoff is the same speed a debris strike needs. Fast debris also staggers characters anywhere in the game, not just near a blast.

Anchored obstacles at head height can topple a character too. If you walk into a block or overhang above the waist, the character leans toward it, and if you keep pressing they fall over backward. Let go early and they straighten up, so you can brush a low beam while running under it. Walking straight into one is a different story.

Slopes steeper than about 45 degrees get climbed rather than walked. The legs angle up the hill and the character moves slower, while the torso and head stay upright like a person climbing. Gentler ramps are crossed at full speed.

Contacts

Parts report touches as events, so scripts can react to collisions without polling positions. Connect to a part's Touched event from a server script:

local pad = workspace.SpeedPad

pad.Touched:Connect(function(other)
    print(other.Name, "reached the pad")
end)

The event fires once when contact begins, with the other part as the argument, and again only after the parts separate and meet again. The server detects the contact and the event replays on clients, so the same handler works in a Script or a LocalScript.

Example

local Physics = game:GetService("Physics")

local hits = Physics:Explode(barrel.Position, 12, 400)
for _, hit in hits do
    print(hit.Instance.Name, "pushed", hit.Distance, "studs from the blast")
end

Physics

Methods

Characters

Contacts

Example

See also