The Multicharacter Emote Library

The pose browser at the bottom of the Scene Creator's Placements tab. Everything in it lives in config_emotes.lua, which is a plain readable Lua file like the rest of the resource.

Poses	305
Categories	12
Scenario	51 — grounded by the engine
Kit emote	150 — RDO emote kit actions
Raw clip	104 — not grounded
Need something to use	7, flagged needsProp
Paired (two marks)	9

The twelve categories

Category	cat	Poses	Made up of
Idles	idle	15	15 scenario
With props	prop	8	8 scenario
Seated	seated	4	4 scenario
Working	work	17	3 scenario, 14 emote
Music	music	3	3 scenario
Dances	dance	38	24 kit, 14 emote
Greetings	greet	7	7 kit
Actions	action	13	13 kit
Shared (two marks)	shared	9	8 emote, 1 kit
Gestures	gesture	68	68 emote
More emotes	emote	105	105 kit
More scenarios	scenario	18	18 scenario

The browser shows them in this order, and scenarios are listed first inside every category — for the reason in the next section.

Three kinds, and why the difference matters

This is the single most useful thing to understand about the library, because it predicts which poses will give you trouble.

Kind	type	Grounded by the engine	Loops	What goes wrong
Scenario	scenario	Yes	Yes	Nothing. It cannot float or sink
Kit emote	kit	No	One-shot	Needs replaying, so it is retriggered on a timer
Raw clip	emote	No	Depends on the flag	Carries the height of the set it was authored on, so it can float

A scenario is a packaged behaviour. You hand the engine a name like MP_LOBBY_STANDING_A and it places, grounds and loops the character itself. There is no height for you to get wrong.

A raw clip is an animation played directly on the ped. The engine does not adjust the ped's position to suit it, so a clip authored two metres above a set's floor brings that two metres with it. This is the cause of almost every floating character.

If a pose floats, sinks or drifts, check its kind first

It is almost certainly a raw clip. Swap it for a scenario from the same category, or set ConfigSelector.ScenariosOnly = true to hide every non-scenario pose everywhere at once.

PROP_HUMAN_* scenarios bring their own prop

And it arrives already aligned to the hand or the body. That is far more reliable than attaching an object by hand with the prop-attach fields, which is covered on Scene Creator reference.

Poses that need something to use

7 entries are flagged needsProp = true, meaning the pose expects furniture or an object that has to be there for it to read correctly:

• seat_bench
• seat_back
• seat_chair
• campfire
• piano
• fiddle
• squeezebox

The editor warns on these, and /scenedebug fails a seated pose with nothing underneath. The Seated category snaps to the nearest seat automatically — see Seats and hovering characters.

Paired poses

The Shared (two marks) category holds the 9 poses written for two people. Each carries a partner table describing the second half, an offset in metres and a facing heading — 180 means the two face each other.

Picking one applies both halves across two marks and creates the second mark if it does not exist. The mechanics, and why RedM makes paired poses harder than they sound, are on Poses.

Adding your own

config_emotes.lua is yours to edit — nothing in this resource is escrowed. A row looks like one of these three shapes:

{ id = "stand_a", label = "Stand (A)", cat = "idle", type = "scenario",
  scenario = "MP_LOBBY_STANDING_A" }

{ id = "hype", label = "Yeehaw", cat = "action", type = "kit",
  emote = "KIT_EMOTE_REACTION_YEEHAW_1" }

{ id = "wait", label = "Waiting", cat = "idle", type = "emote",
  dict = "some@dictionary", anim = "some_clip", flag = 1 }

cat has to match one of the twelve ids in ConfigEmotes.Categories, or the row will not appear under any tab in the browser. Adding a category is a row in that table and a matching cat on the poses that belong to it.

This library is the Scene Creator's, not the player's

The poses players cycle with E come from animations.lua, which is a separate and much shorter list. Adding a row here gives it to whoever is building scenes; it does not put it in front of players. See Poses for the player-facing list.