rojo/.cursor/rules/roblox/reference/engine/classes/RigidConstraint.yaml
2026-02-02 12:08:47 -06:00

46 lines
1.8 KiB
YAML

# This file is automatically generated. Please don't edit it manually.
# To submit a bug report on the content, see
# https://devforum.roblox.com/c/bug-reports/documentation-issues/72
name: RigidConstraint
type: class
memory_category: BaseParts
summary: |
Creates a rigid connection between two `Class.Attachment|Attachments` or
`Class.Bone|Bones`.
description: |
**RigidConstraint** connects two `Class.Attachment|Attachments` or
`Class.Bone|Bones` and ensures they stay in the same relative
position/orientation to each other. This flexibility gives it additional
functionality beyond `Class.WeldConstraint`, such as attaching accessories to
`Class.Attachment|Attachments` on a character rig.
The fastest way to create this constraint is by selecting
**Rigid Constraint** through Studio's **Create** menu in the toolbar's
**Model** tab.
Note that this tool behaves differently depending on whether you click on
existing `Class.BasePart|BaseParts`, `Class.Attachment|Attachments`, or
`Class.Bone|Bones` after the tool is activated:
- Clicking on an existing `Class.BasePart` creates a new `Class.Attachment`
upon it as the intended `Class.RigidConstraint.Attachment0` or
`Class.RigidConstraint.Attachment1`.
- Clicking on an existing `Class.Attachment` or `Class.Bone` uses that
instance as the intended `Class.RigidConstraint.Attachment0` or
`Class.RigidConstraint.Attachment1`.
Following the second valid click, a new `Class.RigidConstraint` is created to
connect the two new attachments. If either the first or second click is
**not** made on a `Class.BasePart`, `Class.Attachment`, or `Class.Bone`, the
workflow is canceled and no constraint is created.
code_samples: []
inherits:
- Constraint
descendants: []
tags: []
deprecation_message: ''
properties: []
methods: []
events: []
callbacks: []