Free RedM scripts worth installing on any VORP, RSG or QBCore server

Free RedM scripts are either abandoned GitHub repositories or the loss leaders of a paid store. Ours are the second kind, and we say so: every script below is maintained because the paid scripts depend on it or because our own server runs it. This is what each one does, what it needs, and the limits you should know before you install it.

1. poggy_core: the one every other script needs

Poggy Core (Free) is the foundation every Poggy script runs on, and it is the most useful thing on this page even if you never buy anything. Once it is installed, every Poggy script on your server checks an update feed at start and every hour, installs its own update, backs up the files it replaced, and restarts. Config files are merged rather than overwritten, so an update that adds a setting adds it, an update that removes one cleans it up, and your own values are never touched. Database tables are created and upgraded when a script starts, so there is no SQL to import.

It is also a framework layer developers can use directly: one Poggy(verb, payload) call for money, items, jobs, storage, notifications, menus and inputs, on VORP Core, RSG Core and QBCore RedM alike. Using Poggy Core in Your Own RedM Scripts walks through it.

Limits: VORP Core, RSG Core and QBCore RedM are the supported frameworks, each with its own adapter proven on a live server. On a server with no framework, or one it has no adapter for, poggy_core refuses framework calls rather than pretending to succeed. The whole thing is readable Lua.

2. Poggy Multijob: several jobs per character

Poggy Multijob (Free) lets a character hold several jobs and switch between them with /multijob or /mj 2. The part server owners notice is the admin panel: every player with jobs, online and offline, with the active job, grade and label editable in place, plus job presets you can apply in one click. Jobs are saved to the database and survive restarts.

Limits: one job active at a time, and it does not cap how many a character holds, so hand jobs out through the admin panel. It uses poggy_core's own menu, so it needs no vorp_menu, and it writes the active job through poggy_core so every other script sees it on VORP Core, RSG Core or QBCore RedM.

3. Poggy Util: eleven small things in one resource

Poggy Util (Free) bundles the utilities most servers end up installing one at a time: an area-of-play box with player count, clock and weather, on-duty law and doctor counts, a searchable help menu with an "I'm stuck" button, weapon jams for dirty guns, wearable armor with a repair kit, /unstuck, music zones, object removal on a timer, dead entity cleanup and a stipend for unemployed characters. Each has its own switch in config.lua; armor, dead entity cleanup and the stipend start switched off.

Limits: the clock and weather widget needs weathersync, and the government stipend is VORP-only today. The other ten utilities work on VORP Core, RSG Core and QBCore RedM with oxmysql.

4. Poggy Storage: player-owned containers

Poggy Storage (Free) gives players a container they own, share with named friends or a whole job, and keep through restarts. Items live in your framework's own inventory as a stash, so the grid your players know is the one they see. Preset storages cover job locations such as police evidence and the doctor's office, and NPC clerks and blips are shown only to players who can actually open the stash.

Limits: containers are vorp_inventory, rsg-inventory or qbr-inventory stashes through poggy_core, all three verified. On QBCore RedM the stashes need the stashitems table; poggy_core prints the CREATE statement at start if it is missing.

5. Poggy Skillcheck: a minigame any script can call

Poggy Skillcheck (Free) is a circular skillcheck with a rotating needle, success and great zones, multi-rep chains and screen jitter. It is one client export that blocks until the player passes or fails, with ten optional parameters. Poggy Fishing and Poggy Crafting run on it; your own lockpicking can too.

Limits: none worth naming. It has no framework, database or server side. The client script is escrowed; the config and interface are open.

6. Admin Blips: every player on the map

Admin Blips (Free) shows admins every player's live position with server ID and character name, toggled with /ahb. Who sees the blips is a name whitelist or, when that is empty, your admin groups, read through poggy_core so the same list works on VORP Core (character groups), RSG Core and QBCore RedM (ACE levels). The update interval, sprite, colour and name format are all in the config.

Limits: it is a monitoring tool, not an anti-cheat.

7. Poggy Crafting: recipes you can follow to the source

Poggy Crafting (Free) opens a recipe browser at benches you set, at every campfire, oven and forge the game already places, and at a campfire players place themselves. Opening a recipe draws its whole chain: each ingredient, whether it can be crafted, and how far you are from having enough, with a card that says where each ingredient comes from. Players keep a shopping list and an on-screen gathering tracker. Recipes can be locked to jobs and places, cost or pay money, and ask for skillchecks through the free Poggy Skillcheck, and the server checks the job and bench locks itself on every craft. Every file is readable, under GPL v2, because it is based on VORP's original vorp_crafting.

Limits: the fourteen recipes that ship are examples, so you write your own; how to set up crafting covers writing them. The server cannot see world props, so it cannot check that a player is standing at one. On RSG Core and QBCore RedM, add the campfire item to your item list by hand.

8. Server Controller: backups without a resource

Server Controller (from $2.99/mo) is not a script. It is a Windows program that runs beside your server and takes scheduled database and file backups with retention and one-click restore, updates txAdmin hands-free and manages the server remotely. The free tier exists so that no server has an excuse for not having a backup; the paid tiers add the rest.

Limits: Windows only, and database backups need the MySQL client tools installed.

Install order

All of them start after oxmysql and your framework. poggy_core goes before every other Poggy script (on RSG Core the two framework lines are ensure rsg-core and ensure rsg-inventory; on QBCore RedM, ensure qbr-core and ensure qbr-inventory):

ensure oxmysql
ensure vorp_core
ensure vorp_inventory
ensure poggy_core
ensure poggy_skillcheck
ensure poggy_util
ensure poggy_multijob
ensure poggy_storage
ensure poggy_crafting
ensure poggy_admin_blips

The rest of the checklist is in how to install a RedM script.

What free does not cover

The systems players build a session around, an economy, a reason to fear the law, an activity for a quiet night, are the paid scripts, and the best RedM scripts guide works through them by need. If you want several, the All Access subscription is usually cheaper than buying two outright.