Skip to content
Tutorials

Designing a FiveM Roleplay Economy: Sources, Sinks and Inflation

ATY Development
·
·Updated ·
28 views
QBCoreESXQbox
Designing a FiveM Roleplay Economy: Sources, Sinks and Inflation

Most FiveM roleplay economies fail the same way. A few weeks after launch, money stops meaning anything, every second car in Legion Square is a supercar, and new players cannot catch up with anyone. That is rarely a scripting bug. It is a design problem, and you can fix it with a money map, a few targets and a habit of checking your numbers.

Start with a money map

Before you tune a single payout, write down every way money enters and leaves your server. Most owners never do this, which is why they cannot explain where inflation comes from.

Sources are anything that creates money out of nothing:

  • Legal job payouts (delivery, garbage, bus, mining, fishing)
  • Paychecks for government jobs and on-duty salaries
  • Selling items to NPC shops
  • Illegal activities: drug sales to NPCs, robberies, heists
  • Starting cash and any admin or event rewards

Sinks are anything that destroys money:

  • Vehicle, house and item purchases from NPC shops
  • Repairs, fuel, impound and towing fees
  • Rent, property tax, business licenses
  • Fines and hospital bills paid to the state, not to a player
  • Crafting materials bought from NPCs

Player-to-player trades are neither. Buying a car from another player moves money around but does not change the total. That distinction matters: if your only big sink is a player-owned dealership where the money goes to the owner, you have no real sink at all.

Price jobs by time, not by task

Setting a delivery to pay a round number because it feels right is how you end up with one job paying five times another. Work backwards from an hourly target instead.

  1. Decide what a new player should earn per hour of honest legal work. Pick a number relative to your prices, for example enough that a modest first car takes three to four hours of play.
  2. Time each job yourself, including travel, loading and the walk back to the vehicle. Do it at least three times.
  3. Divide the hourly target by the number of runs per hour. That is your per-run pay.
  4. Adjust for risk and effort. Jobs that need a group, special equipment or carry danger can pay more per hour, but within a defined band, not without limits.

Keep a simple spreadsheet with job name, minutes per run, pay per run and resulting hourly rate. When someone reports that a job is "broken", you can check whether it is outside its band in seconds.

Illegal income needs a ceiling too

Criminal activities should pay better per hour than legal work, because they carry risk of arrest, losing items and time spent in prison. The mistake is letting that premium grow unchecked. If selling drugs to NPCs pays ten times a legal job with little real risk, your entire population turns into dealers and police get overwhelmed. Keep illegal hourly income in a band, add cooldowns, and make sure the risk is real: active police, item loss on arrest and limited NPC demand.

Sinks players do not resent

Players hate taxes that feel like punishment. They accept costs that feel like part of the world. A few that tend to work:

  • Maintenance: vehicles that slowly need repairs, fuel that costs something, tyres and parts that wear. Ownership has an ongoing cost, which is realistic.
  • Property upkeep: weekly rent or tax on houses and businesses. This also frees inactive properties for active players if you reclaim them after missed payments.
  • Status items: expensive clothing, unique plates, custom paint and high-end apartments. Wealthy players spend voluntarily and remove a lot of money.
  • Convenience fees: paying for fast travel, instant impound retrieval or a private garage slot instead of waiting.
  • Licenses: driving, weapon, business and hunting licenses that also give police something to check during roleplay.

Avoid sinks that hit poor players hardest, such as flat daily fees on everyone. Scale costs with what the player owns.

Inflation warning signs

You do not need complex analytics. Check these regularly, weekly on a new server and monthly later on:

  • Total money in circulation: sum all cash and bank balances. If it grows much faster than your active player count, sources are outrunning sinks.
  • Top balances: look at the richest 10 characters. A single account far above the rest usually means an exploit, a duplication bug or a payout that is far too generous.
  • Expensive vehicle ownership: if the most expensive tier of cars becomes common, prices no longer mean anything.
  • Player-set prices: when players start pricing services in huge numbers, the currency has lost value.
  • New player complaints: "there is no point working, everything costs too much" often means veterans have pushed player market prices out of reach.

Log every transaction that matters

You cannot fix what you cannot see. Make sure every money addition from a script runs on the server and leaves a trace with the resource name and a reason. Most frameworks let you pass a reason when adding or removing money; use it consistently and send larger amounts to a log channel or database table.

A server-side rate limit on payouts also protects you from both exploits and badly tuned jobs. A framework-agnostic sketch:

-- server side, example values only
local HOURLY_LIMIT = 25000
local earned = {}

local function canPay(src, amount)
    local now = os.time()
    local entry = earned[src]
    if not entry or now - entry.start >= 3600 then
        entry = { start = now, total = 0 }
        earned[src] = entry
    end
    if entry.total + amount > HOURLY_LIMIT then
        return false
    end
    entry.total = entry.total + amount
    return true
end

AddEventHandler('playerDropped', function()
    earned[source] = nil
end)

When canPay returns false, do not silently drop the payout. Log it. A legitimate player hitting the limit means your limit or your job tuning is wrong; a player hitting it repeatedly through an unusual path is worth investigating. Pair this with the basics of never trusting client-sent amounts: the server decides how much a job pays, the client only says "I finished".

Changing the economy on a live server

At some point you will need to cut a payout or raise a price. Done badly, this causes more drama than any other update.

  • Announce first. Give players a few days of notice and explain why. "Fishing paid three times more per hour than any other legal job" is easier to accept than a silent nerf.
  • Change in steps. Two smaller adjustments a week apart are better than one big cut.
  • Raise sinks before cutting sources. Adding a desirable new item or property soaks up money without making anyone feel poorer.
  • Test on a copy. Run a development server with a recent database backup and check that the new values behave as expected.
  • Write it down. Keep a changelog of economy changes with dates so you can connect them to the numbers you track.

About wipes

A full economy wipe is the nuclear option. It resets inflation, but you lose players who spent months building their characters. If you must wipe, consider a partial reset: money above a cap is reduced, owned properties and vehicles are kept, and you announce it well ahead of time. Better still, design sinks early enough that a wipe is never needed.

Practical takeaway

  1. List every money source and sink on your server and remove anything you cannot account for.
  2. Set an hourly income band for new legal work, experienced legal work and illegal work, then price every job against it.
  3. Add ongoing ownership costs and voluntary luxury purchases as your main sinks.
  4. Keep all money changes server-side, with a reason, and log the large ones.
  5. Check total circulation and top balances on a schedule.
  6. Change values gradually, with notice, and test on a copy of your live data first.

An economy is not something you configure once at launch. Treat it like any other part of server maintenance, and your money will keep meaning something to the players who earn it.