RedM Dance Pack: 27 Custom Dance Animations

All 27 dances ship twice, once for a male character and once for a female one, across eight animation dictionaries. The female name is always the male one with @f appended, so redmorrow_dance_24@dance becomes redmorrow_dance_24@dance@f and the choice is a suffix rather than a lookup.

The breakdown is published, not summarised: five samba dances, four hip hop, four northern soul and four general dance loops, with swing, house, running man, maraschino step, breakdance and silly dance all named in the listing. What arrives is a list you can check.

Twenty-four main dances, then three more counted separately as bonus. The pack's own breakdown keeps those three apart from the main set, and twenty-seven is simply the two figures added together. The clip list in the download names every one of them.

The shortest clip is half a second, a beat that repeats. The longest runs to just under twenty-eight, which is a routine with somewhere to go, and the middle of the set sits near nine. Every one is set to loop, so a dance holds until something stops it.

A dance is not a private effect on the dancer's own machine. The files reach everyone connected, so the crowd in the room watches the thing the dancer started, which is the only way a dance is worth having in a roleplay scene.

There is no command, no keybind and no menu in the download. If your players expect to type /dance, that comes from whatever you wire these clips into. The pack's job ends at making the animations available and naming them.

clips.lua arrives unencrypted, so its rows copy straight into the emote menu you already run, and the labels your players read are editable in the same file. Key your menu on the id rather than the clip name: two dances share the clip name jazz_dancing and only their ids tell them apart.

The README carries install steps and a table setting every dance against its dictionary, its clip name and its length. That is the document you work from when you are wiring twenty-seven dances into a menu.

On the client there are no threads and no loops, which is the whole of where the 0.00 ms figure comes from. The streamed animation files come to about four megabytes. Nothing is ticking on a player's machine while the dance is simply available to be played.

The animations are escrow protected, so the server key in server.cfg has to belong to the Cfx.re account the purchase sits under. A key from a different account starts nothing and reports a missing entitlement, which is a configuration problem and not a bad download.