RedM Dance Pack
Bring your saloons, camps and events to life with 27 custom dance animations, each with a male and a female version. From samba and hip hop to northern soul spins, swing and a cheeky…
Resources that run standalone, with no framework dependency at all. Drop them onto any Red Dead Redemption 2 roleplay server, whether it runs VORP, RSG Core, RedEM:RP or a core your team wrote yourselves, and configure them from a single file.
Not sure which framework your server runs? Ask in our Discord and we'll help you pick the right build.
No products match your search.
Bring your saloons, camps and events to life with 27 custom dance animations, each with a male and a female version. From samba and hip hop to northern soul spins, swing and a cheeky…
100+ custom female pose animations for RedM , delivered as native RDR2 .ycd animation dictionaries and streamed straight from the resource. Poses, leans, smoking, hats down and regard…
Four combat mechanics in one resource. Slide, roll, gun tricks, and a dive that puts you on the ground still shooting. Built for servers where a gunfight is currently two people standing…
Build your map inside the game. Open /mapeditor, place what you want, export when you are done. This RedM map editor gives you 17,473 in-game props, people, animals and wagons, four export…
30+ custom female poses for RedM , each one a native RDR2 .ycd dictionary streamed straight from the resource. Natural standing and portrait-style poses, ready to drop into whatever you…
Your server has rules and nobody reads them , because they are in a Discord channel three months up, and no new player is scrolling that far to find them. This RedM guidebook script puts…
4,300+ RedM emotes out of the box , curated and filtered for clean looping poses. Hover any one of them and a translucent mannequin performs it in front of you before you commit, so players…
A lantern costs you a hand , so nobody carries one and your nights stay dark. This puts it on the belt, hangs it off the saddle, or leaves it burning in the dirt where you set it down…
RedM Pause Menu Script turns the pause screen into the heart of your server: a gold-framed, leather-and-parchment menu that opens with a cinematic camera while your character unfolds a…
A carryable phonograph your players set down anywhere: records live in their bags, the needle drop is server-authoritative, and every listener stays in perfect sync, with no audio resource…
Crayfish beds worth walking to. Forty-three holes across Bayou Nwa, Lagras and Lakay stock and empty on the world clock. The lure you drop in decides the odds, and every roll is taken on…
RedM Reports turns player help requests into a full moderation workflow. Players file categorized tickets with priorities, custom forms, captured location and nearby players; staff claim…
No framework dependency, not merely no library stack. Five of the six qualify: Reports, Crayfish, the Phonograph, the Pause Menu and the Lantern. Each one looks for a framework at start-up and carries on without it. Fireworks is the exception and is not listed above, because it needs VORP or RSG for its inventory.
The Pause Menu keeps its menu, events, journal and admin desk and simply hides the money rows. The Phonograph falls back to the licence identifier for identity, binds placement to a command instead of a usable item, and opens its whole record catalogue to everyone, since there are no inventories to check against. The Lantern skips its optional item gate, so a player just needs the lantern weapon, exactly as in singleplayer.
Very little. The Pause Menu has one hard dependency, oxmysql, for its own self-migrating tables. The Lantern needs oxmysql only if you turn on MySQL persistence for placed lanterns, and not at all on JSON. Nothing here needs ox_lib, NUI libraries, streamed assets or a SQL file imported by hand.
It means no framework. A couple of scripts still want oxmysql for their own tables: the Pause Menu always, the Lantern only if you choose MySQL persistence over JSON.
Only what a framework provides: money readouts, inventory items and framework identity. Every other feature stays, which is the point of building them this way.
No. The same resource detects the framework at the next start-up and begins using it. Nothing needs rebuying and no file gets swapped.