Qadr_rc - Native Role Creator & Progression System

RedM Releases
,
1

qadr_rc
qadr_rc1376×768 258 KB

This script will not work without qadr_ui, and qadr_ui is a paid script.

I’m sharing qadr_rc, a standalone role progression and reward system designed specifically for RedM.

It uses Red Dead Redemption 2’s native Scaleform interface (role_progression) directly in the Pause Menu. It also includes an in-game NUI editor (/create_role) made with React and Tailwind to configure your roles, ranks, and item rewards in real time.

Preview Video

Features

  • Native Pause Menu role screen and UI sounds
  • Live in-game role editor via /create_role command
  • Character-based role tokens and progression saving
  • Automatic rank unlock items and token purchase items
  • Framework agnostic: standalone base, easily integrated with any inventory
  • Automated database table setup via oxmysql

Requirements

Reward Integration

When a player reaches a rank or purchases an item with tokens, the server triggers qadr_rc:onRewardClaimed. You can give items/rewards using your own inventory exports inside this event:

AddEventHandler("qadr_rc:onRewardClaimed", function(src, roleName, item, itemType, rank)
    -- itemType: "rank_item" or "kit_item"
    -- Example: GiveItem(src, item.id, 1)
end)

Download & Documentation

1 Like
2

**Requirements

**
qadr_ui (v3.6+) - Native Scaleform rendering library

So you give something for free but not usable unless I pay 27 euros for your ‘‘qadr_ui’’ what’s the point of giving the role creator script for free if it needs the UI as a dependency ? Please expand your point or correct your missleading post.

1 Like
3

I completely understand your point, and I agree that you have a valid concern. A free script requiring a paid resource to function can be confusing, especially if that dependency isn’t made clear enough from the beginning.

I probably should have explained my intention better. qadr_ui is a standalone paid project, while qadr_rc (Role Creator) is completely free and open source.

I’m developing qadr_ui not as a single ready-to-use script, but more as a UI resource that developers can use to build their own systems. The idea is to have different UI features optimized and available in one place, so they can be reused across different scripts.

So qadr_rc is essentially one of the free, plug-and-play systems I’m creating for people who already own qadr_ui. A developer who owns qadr_ui could build the same system themselves, but not everyone has the time or development experience to do that. My goal is to provide these additional systems for free so qadr_ui users don’t have to build everything from scratch.

This also isn’t the first project I’ve released this way. I’ve previously released qadr_pass and QADR Poster Creator, which are also free and open source while depending on qadr_ui. So my intention isn’t to use a “free” script to force people into buying a paid resource. It’s to provide additional free systems for people who already own qadr_ui, while also giving others real, working examples of what can be built with it.

That being said, I understand your criticism. I should have made it more obvious from the start that qadr_ui is a paid dependency, and I don’t want the post to give anyone the wrong impression.

Because of your feedback, I’ve added this notice at the very top of the post:

“This script will not work without qadr_ui, and qadr_ui is a paid script.”

Thank you for pointing it out. I appreciate the feedback, and I agree that this should have been clearer from the beginning.

1 Like
4

Thanks for taking the time to explain it and for adding the notice. I appreciate that.

Just to clarify my original point, I’m not here to bash your products or question the work you’re putting into them. I actually appreciate the effort that goes into creating and releasing things for the community, and I wish I could support you and make use of more of your work.

It’s more about a situation I’ve seen happen many times where something is presented as “free”, and people naturally get that little spark of “wow, this is a really cool script and I get to enjoy it for free.” Then they discover that a paid dependency is required, and that can leave people confused or feeling like the initial impression was different from the reality.

Now that you’ve made the dependency clear at the top, I think that removes most of that confusion. Your explanation also makes the intention behind the projects much clearer.

No hard feelings from my side, and I appreciate you taking the feedback constructively. :+1:

2 Likes