Suty
Player Carry System

Troubleshooting

Troubleshooting

Carried player floats / is in the wrong pose

The attach offsets in config/carry.lua are tuned per animation dict. If you switch Config.AnimationType from "custom" to "default" (or vice versa), the attach offsets won't match the new anim — adjust attachX/Y/Z and rotX/Y/Z for the new dict.

"Baby Carry" style does nothing on adult peds

By design — brazos has restrictToQbxPeds = true, so it only triggers on qbx_peds toddler/kid models. To allow adults: set restrictToQbxPeds = false for the brazos entry. The pose will look ridiculous on adults but it'll work.

Animation doesn't play / "Animation failed to load"

  • The required animation dict failed to stream. For custom dicts, check that stream/ ships them and the resource started cleanly.
  • For the brazos style: suty-emotes must be installed (provides suty@parent2 / suty@child2).

Movement speed isn't reduced

Config.MovementSpeedReduction = 0.7 should slow you to 70%. If it doesn't work:

  • Other resources may be overriding SetPlayerMaxStamina or SetPedMaxMoveBlendRatio
  • Check Config.AnimationCheckInterval — default 1000ms; the speed clamp re-applies on each tick

Player keeps being able to sprint / jump while carrying

  • Config.DisableSprintWhileCarrying = true
  • Config.DisableJumpWhileCarrying = true

If you've added a custom keybind script that fires +sprint directly, it can bypass the disable. Standard SHIFT-to-sprint is correctly blocked.

"Cannot do that while carrying"

This is the Config.Messages.cantDoThat message. You're trying to interact with something (use weapons, open inventory, drive) while still carrying. Drop first (/carry again), then do the action.

Notification system shows wrong messages

Config.NotificationSystem doesn't match what's installed. Confirm with start console — does the listed notify resource actually appear in the started list?

Still stuck?

Discord — include Config.AnimationType, Config.NotificationSystem, and which carry style you were attempting.