Rigidbody2D

Realot Studio Rigidbody2D component reference: fields, script API, behavior and examples.

#What it does

2D physics body backed by the engine physics runtime. Dynamic, Kinematic and Static bodies have different script controls.

#How to add and use Rigidbody2D

Editor path: Select the target entity in the Hierarchy (left side) → look at the Inspector (right side) → click Add Component at the bottom of the Inspector → search for Rigidbody2D → click the component row. The Add Component picker is a centered modal with a search box; it only lists components not already attached.

For components with a dedicated editor tool, the tool is opened or activated from the location described below. Do not assume that adding the component alone activates its editor; some systems require a separate window, panel, or viewport tool.

#Component setup & editor tools

• Select entity → Inspector → Add Component → Rigidbody 2D. After adding it, the Rigidbody2D section exposes body type, gravity/damping, velocity/drive values, rotation locking, and controller/ground state fields.

#What you should see after adding it

The component appears as its own section in the Inspector. Its serialized settings are listed in the Component data table below. If a field is conditional, it appears only when the relevant mode/type is selected. If a field is a runtime state field (for example grounded or resolved velocity), treat it as read-only diagnostic state unless the API reference explicitly documents it as writable.

#How to read the settings

For every setting below, the documentation distinguishes type, default, meaning, and tuning direction where behavior is known. When a value represents a direction, use the engine's coordinate convention documented in Coordinate system; do not substitute Unity/Godot conventions.

#Component data

#Tuning behavior

These are the practical direction-of-change rules for the most important controls on this component.

#Automatic mass and force at a point

• autoMass (default true): a Dynamic body computes its mass from the attached collider geometry and density. Uncheck it in the Inspector to use the mass value instead.
• angularDamping: resistance to spinning, separate from linear damping.
• addForceAtPoint(...) in the script API pushes the body at a world point, so it also creates torque.

#Script API

#Notes & behavior

• Kinematic-only methods are meaningful for Kinematic bodies; Dynamic-only force methods apply to Dynamic bodies.
• Position assignment through this.x/this.y is treated as a physics teleport target for non-static bodies.

#Examples

this.rigidbody.addImpulse(0, -350);

this.rigidbody.velocityX = 200;

this.rigidbody.move(100 * time.deltaTime, 0);