Free RedM Framework Core and Auto-Updater Poggy Core

The free, open-source RedM framework core that every Poggy script runs on, for VORP Core, RSG Core and QBCore RedM: it installs each script's updates, merges your config, creates the database tables, and adds account bans with a shared ban network against cheaters. Script authors get one API for all three frameworks.

Scripts that update themselves

• When the server starts, poggy_core checks the Poggy update feed and installs every script with a higher published version.
• Config and translation files are merged: new settings are added, removed ones are cleaned up, and every value you changed stays.
• A list you rewrote, such as law job ranks with your own jobs in place of the shipped ones, is left exactly as you wrote it (0.25.1).
• Every file it replaces is backed up in poggy_core/update_backups/ first.
• Updated scripts are restarted for you. poggy_core never restarts itself; its own update takes effect at the next server restart.
• Escrowed scripts update the same way: nobody re-downloads from the Cfx portal.
• Prefer to review first? Set AutoUpdate and ApplyOnStart to false, then install with poggycore update all apply.

No SQL to import

Each Poggy script's tables, columns and indexes are created when it starts, on MariaDB and MySQL 8. Nothing is dropped.

Account bans and the ban network

• A ban is on the player's account, not the character, so it follows them to every character. Someone who already left can be banned by identifier.
• Ban from /poggy, the console (poggycore ban 12 7d combat logging) or a script such as Poggy Tickets.
• If the database cannot be read, nobody is refused.
• A ban marked as cheating is shared as one vote with other servers running poggy_core. A player with votes from 3 servers is refused on all of them that enforce the network.
• Rule-break bans never leave your server. Only scrambled identifiers and your player count are shared: never a name or a reason.
• The network is on by default. Sharing and refusing are separate switches in /poggy, and poggycore banallow lets one blocked player into your server.

Settings and screens in game

• /poggy opens a settings hub with a card for every Poggy script: settings, lists, commands and help pages. It edits the script's own config.lua in place, backs it up and records who changed what.
• A script with a radial menu has it edited on a picture of the wheel (0.26.0): click an option to change it, drag one onto another to swap them, and preview the wheel as a player with a given job would see it.
• One look for every Poggy screen: nine ready-made themes plus a custom one, under /poggy → Poggy Core → Theme.
• /poggyui lets each player set screen size (50% to 200%), a light look and less motion for themselves.
• Script folders can be renamed; updates and stored data follow the script.

Commands

For script authors

• One call shape, Poggy(verb, payload), for characters, money, jobs, inventory, storage, notifications, callbacks, menus, text inputs, prompts and permissions.
• Every call returns a result or a reason, never a silent failure.
• From 0.25.0: every job a character holds (including VORP's own multijob and rsg-multijob), and everyone who holds a job, offline characters included.

What you need to run it

• VORP Core, RSG Core or QBCore RedM (QBR). RedEM:RP and RPX are not supported.
• oxmysql, for scripts that use the database.
• Start it after your framework and before every Poggy script, with add_ace resource.poggy_core command.refresh allow and add_ace resource.poggy_core command.ensure allow (and the same line for command.start and command.stop) so it can restart what it updates.
• No vorp_menu or vorp_inputs needed.
• Free, and every file is readable.