Money Wash

Features

• Works with any setup: ESX, QBCore, Qbox or no framework; ox_inventory or the framework's inventory; ox_target, qb-target or a built-in "press E" prompt. All detected automatically.
• IPL or MLO: IPL money washes teleport players in and out through entrances/exits; MLO money washes are part of the map and players simply walk in.
• In-game editor (/washadmin): create money washes, aim to place entrances, exits and dryers, set fees and blips, duplicate dryers down a row, teleport around, finish or empty running loads.
• Per-wash and per-dryer settings: fee, wash speed, max load, and an optional required item (e.g. detergent), used up or not.
• Walk-away washing: a short load animation, then the dryer runs on its own. The owner is notified when it's done.
• Dirty money as an item, an account (ESX black_money) or QBCore marked bills (with change handed back).
• Saved on the server: money washes and running loads survive restarts and disconnects. No database needed.
• Secure: every check happens on the server; the load animation can't be skipped; a load can't be collected twice.
• Discord logs with a separate channel per log type, and optional console logs.
• Fully translatable: every text (players and staff) is in one language file.
• Customisable look: colors, fonts, notification position, third-eye labels and icons.
• Optimised: no loops running while nobody is near a money wash, and no database queries.

Requirements

Files

orynt_moneywash/
├── config.lua            Settings (editable)
├── fxmanifest.lua
├── README.md             This file
├── LICENSE.md            Terms of use
├── locales/
│   └── en.lua            All text players and staff see (editable, copy to translate)
├── shared/
│   └── text.lua          Loads the language
├── client/
│   ├── main.lua          Zones, blips, doors, washing
│   ├── placement.lua     The aim-to-place tool in /washadmin
│   └── target.lua        ox_target / qb-target / built-in prompt (editable)
├── server/
│   ├── sv_config.lua     Discord and console logs (editable, server only)
│   ├── bridge.lua        Framework and inventory support (editable)
│   ├── logs.lua          Discord webhook sender
│   └── main.lua          Money washes, loads, payouts, /washadmin
└── html/                 The washer screen and the /washadmin editor
    ├── index.html
    ├── style.css
    ├── script.js
    └── img/              Orynt logo

Files marked editable stay readable when the resource is escrowed.

Installation

1. Add the resource

Put the orynt_moneywash folder in your resources folder (any sub-folder like [orynt] is fine).

Don't rename the folder. Saved money washes are stored under the resource name. A renamed folder starts empty.

2. Add the dirty money item (if you use an item)

By default players wash the item dirty_money (Config.DirtyMoney). If your server doesn't have it, add it, or point Config.DirtyMoney at the dirty money you already use (see Money).

ox_inventory - ox_inventory/data/items.lua:

['dirty_money'] = {
    label = 'Dirty Money',
    weight = 0,
    stack = true,
},

QBCore - qb-core/shared/items.lua:

dirty_money = { name = 'dirty_money', label = 'Dirty Money', weight = 0, type = 'item', image = 'dirty_money.png', unique = false, useable = false, shouldClose = false, description = 'Needs washing' },

ESX usually uses the black_money account instead: set Config.DirtyMoney = { type = 'account', name = 'black_money' } (with ox_inventory, { type = 'item', name = 'black_money' } works too).

3. server.cfg

Start it after ox_lib and your framework, inventory and target resources:

ensure ox_lib
ensure orynt_bridge
ensure es_extended        # or qb-core / qbx_core
ensure ox_inventory       # if you use it
ensure ox_target          # or qb-target
ensure bob74_ipl          # optional, for IPL money washes

ensure orynt_moneywash

4. Permissions

Admins in your framework's admin, superadmin or god group can already use /washadmin. To give access by ace instead (or as well), add to server.cfg:

add_ace group.admin orynt_moneywash.admin allow

5. Start it

Restart the server, or type in the server console:

refresh
ensure orynt_moneywash

The console should show:

[Orynt MoneyWash] framework: esx, inventory: ox_inventory

with no red errors. Then set up your first money wash.

Setting up your first money wash

Type /washadmin in-game.

MLO money wash (players walk in)

1. Click New money wash. Give it a name, pick MLO, set the fee, optionally turn on a blip, and click Create money wash.
2. Go to the MLO. Open the Dryers tab, click Add dryer, then Aim: look at the spot, press E, and click Save.
3. Add more dryers the same way, or open a saved dryer and click Duplicate to copy it to the next spot.

Done: the "Not ready" tag disappears from the money wash in the list.

IPL money wash (players teleport in and out)

1. Click New money wash. Name it, pick IPL interior, set the fee and blip, and click Create money wash.
2. Click Teleport inside (new IPL washes start in the bob74_ipl counterfeit cash factory), stand where players should appear, and click Set to my position. To use a different interior, go there and click Set to my position instead.
3. Exits tab: Add exit at the inside door.
4. Dryers tab: Add dryer for each dryer.
5. Go outside. Entrances tab: Add entrance on the door players should use (as many as you like).

How it plays

1. Get inside: walk in (MLO), or third eye the entrance and pick Enter (IPL).
2. Third eye a dryer and pick Use washing machine. The screen shows how much dirty money you have, the fee, what you'll collect and how long it takes.
3. Click Load machine. The player does a 15-second animation (it can be cancelled, and no money is taken), then is free to go.
4. Check machine shows the time left. The owner gets a notification when it's done, even if they left.
5. Collect money pays out the clean cash. Only the person who loaded it can collect, unless Config.AnyoneCanCollect is on.
6. IPL: leaving through an exit takes players back out the entrance they came in by.

Each player can have one load running at a time (Config.MaxLoadsPerPlayer).

The /washadmin editor

Money washes are listed on the left with their type, fee and status. Click one to open it.

Entrances / Exits / Dryers tabs list that money wash's locations. Each location has:

Placing a location (Aim)

Other tools

• Duplicate copies a saved location's settings to a new spot you aim at, and counts numbered labels up ("Dryer 1" → "Dryer 2").
• On a running dryer: Finish now (handy for testing) or Empty (the money is lost).
• Delete asks twice. Deleting a money wash deletes all its locations and anything in its dryers.

Configuration (config.lua)

1. Admin

2. Framework, inventory and third eye

3. Money

Config.DirtyMoney:

• { type = 'item', name = 'dirty_money' }: an inventory item, $1 each.
• { type = 'account', name = 'black_money' }: a framework money account (e.g. ESX black_money).
• { type = 'markedbills', name = 'markedbills' }: QBCore/Qbox marked bills. Each bag's worth counts towards the load, and any change is handed back as a new bag.

Config.CleanMoney:

• { type = 'account', name = 'auto' }: money on ESX, cash on QBCore/Qbox.
• { type = 'item', name = 'money' }: an inventory item. Use this when running without a framework.

4. Washing

5. Interaction zones

6. IPL interior

7. Blips

8. Look and feel

Server configuration (server/sv_config.lua)

This file is never sent to players, so webhook links stay private.

Discord logs

1. In Discord: Server Settings → Integrations → Webhooks → New Webhook, pick the channel, Copy Webhook URL.
2. In server/sv_config.lua, paste it into SvConfig.Logs.webhook and set enabled = true.
3. Optional: make a webhook per channel and paste them into webhooks (load, collect, admin, exploit).
4. ensure orynt_moneywash.

Every log shows the player's name, server id and the identifiers you chose. Logs are sent one at a time and wait when Discord rate-limits, so none are lost. Keep webhook links private: anyone with one can post in that channel.

Translating

Every text players and staff see (messages, the washer screen, the /washadmin editor and Discord logs) is in locales/en.lua.

1. Copy locales/en.lua to e.g. locales/de.lua.
2. At the top, change Locales['en'] to Locales['de'].
3. Translate the text. Keep the words in {braces}: the script fills them in.
4. Set Config.Locale = 'de' and ensure orynt_moneywash (after refresh, since it's a new file).

Anything left out falls back to English.

Commands and permissions

Access: the ace in Config.AdminAce, or a framework group in Config.AdminGroups. All admin actions are checked on the server.

Saved data

Money washes, locations and running loads are saved in the server's resource storage (KVP), not in a database. They survive restarts, and loads keep running while the server is off (the wash timer uses real time).

• Saved data belongs to the resource name orynt_moneywash: don't rename the folder.
• To start over, delete the money washes in /washadmin.

Updating

Replace the resource folder with the new version and start it (refresh, then ensure orynt_moneywash, or restart the server). Nothing to copy over:

• Your settings come back by themselves. Every start, config.lua, server/sv_config.lua and your own translation are copied to the server (its KVP, outside the resource folder). When the new version starts with the files from the download, yours are put back and the resource restarts once to load them.
• New options your config doesn't have yet use their defaults, and the console lists them once (the changelog below says what they do).
• Your money washes and running loads are saved on the server, not in the resource folder: they stay.
• Changed server/bridge.lua or client/target.lua? The new version's file is used (it may need it), and yours is saved next to it as <file>.before-update so you can move your changes over. The console says so.
• Keep the resource's name (orynt_moneywash): the saved settings belong to it.

To let it restart itself after putting your settings back, add this to server.cfg (without it, the console asks you to type ensure orynt_moneywash once):

add_ace resource.orynt_moneywash command.ensure allow

To go back to the default settings on purpose: type orynt_moneywash:resetsettings in the server console, put the files from the download back and restart the resource.

Updating from a version before 1.1.0: those don't save your settings yet, so this one time keep a copy of your config.lua, server/sv_config.lua and language files, and put them back after replacing the folder. From 1.1.0 on, updates keep them by themselves.

Troubleshooting

Performance

• Nothing runs every frame unless a player is at a money wash location (or an admin is placing one).
• No database queries. The server only does work when someone uses a money wash, plus a light check every 5 seconds for finished loads.

Changelog

• 1.2.0: now runs on orynt_bridge, the free Orynt resource that handles your framework, inventory, third eye, keys and fuel. That also adds qs-inventory, codem-inventory, tgiann-inventory, origen_inventory, core_inventory, ps-inventory and lj-inventory, and more key and fuel scripts, for every Orynt script. Install it once (see Installation); your settings and data stay.
• 1.1.0: new Orynt look (Orynt purple, new emblem and wordmark, Orbitron titles, glowing buttons and selection). Keys typed in the window can no longer reach the game, even if another resource leaves NUI "keep input" on. Fixed: with several IPL money washes (which share the counterfeit factory), you only see and use the exits and dryers of the money wash you went into, and its exit takes you back out its own entrance. New Config.Interior.instances. Inside spawn: a Reset location button and a warning. Default third-eye distance is now 0.8 m. Updates keep your settings now: replace the folder and your config comes back by itself (see Updating).
• 1.0.0: first release.

Escrow and license

When escrowed, these files stay readable so you can configure, translate and adapt the script to a custom framework or target: config.lua, server/sv_config.lua, locales/, server/bridge.lua and client/target.lua.

See LICENSE.md for the terms of use. In short: use it on your own servers; don't resell, share or leak it; keep the Orynt Development branding.

© Orynt Development