Economy

# REDEMPIRE Business
`jrs_business` is the REDEMPIRE business/company resource for RedM. This build was reviewed directly against:
- `jrs_core` **1.0.18**
- `jrs_character` **3.4.7**
- `jrs_inventory` **1.6.37**
The integration is direct and server-authoritative. No legacy multi-framework compatibility layer is used.
## REDEMPIRE Core + jrs_character employee hiring (1.2.0)
The Employees panel is tied to the actual selected REDEMPIRE character, not only the RedM server ID.
- Online candidates are read from the authoritative `jrs_core` selected character and require a ready REDEMPIRE character.
- Offline hiring uses the exact `characters.charidentifier` row used by `jrs_character` 3.4.7.
- Character identity is always the pair `identifier` + `charidentifier`; names are display data only.
- Full-access administrators can hire even while a company has no assigned owner.
- The Employees tab requests a fresh candidate list when opened and after every hire/fire.
- Self-hire, owners/partners, duplicates, invalid characters, disconnected targets and cross-company duplicate employment are rejected server-side.
- Hiring writes the configured business job to REDEMPIRE Core. Online characters use the stable `exports.jrs_core:SetJob(...)` path; offline characters update t
- The previous REDEMPIRE job/grade is stored with the employee record. Firing restores it only when the character still has the job assigned by this company, so
- If company persistence fails after a REDEMPIRE job change, the job is rolled back. If the REDEMPIRE job cannot be synchronized and `requireJobSyncSuccess` is 
- Online hired/fired characters receive notifications; payroll remains bound to their exact REDEMPIRE character identity.
Default job mapping is configurable in `Config.Employees`:
'''lua
jobByCompany = {
    cotton = "cotton",
    mill = "mill",
    oil = "oil",
},
gradeByRole = {
    worker = 0,
    driver = 1,
    engineer = 2,
},
'''
Set `syncJRSJob = false` if you want company membership without changing the REDEMPIRE primary job.
## Requirements
Start resources in this order:
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_inventory
ensure jrs_clothing
ensure jrs_barber
ensure jrs_character
ensure jrs_business
'''
## Installation
1. Copy the folder as `jrs_business`.

# jrs_lottery 2.2.0
Persistent lottery for JRS Core. Original: Markus Mueller / RetryR1v2. JRS port and hardening: JRS.
- Open with **E** next to the clerk at a station (Blackwater, Valentine, Rhodes, Saint Denis).
- $1 per ticket (10% house cut leaves the pot), 5 tickets per character per draw, draw every 100 minutes, first ticket adds a $2 seed.
  All of it is in `config.lua`. The winner takes the whole pot and collects it at any station (offline wins are kept).
- UI is a NUI window in the jrs_stores skin (textures are copies of `jrs_stores/html/theme`), EN/AR follows the character language.
- Tables are created automatically on first start (`sql/jrs_lottery.sql` is the same schema for manual installs).
- Never run together with the old `mms-lottery`; its rows have no character id and are not migrated.
## Security model
Every purchase/claim is validated on the server: character ready, routing bucket, distance to a station,
price/limits read from config and DB (the client sends only the station index), one operation at a time,
per-player cooldowns, ticket reserved in SQL before cash is taken, prize reserved before it is paid.
No draw/pick/reset events are network-exposed; webhook URL lives in `server/config.lua` only.
## Admin (in-game with jrs_core admin rights, or server console)
- `jrs_lottery_draw` - draw now.
- `jrs_lottery_review` - print unresolved tickets/claims to the console.
- `jrs_lottery_resolve ticket <id> <activate|cancel>` / `jrs_lottery_resolve claim <token> <paid|pending>` -
  settle a held payment after checking the player's real balance. Never set `processing` back to `pending`
  unless you confirmed the cash was NOT paid.
## Interrupted payments
Cash (jrs_core) and lottery rows (SQL) cannot share one transaction. If the server dies between the two, the row stays
`preparing` (ticket) or `processing` (prize) and blocks that character until an admin resolves it with the commands above.
A failing draw is retried every `Config.DrawRetrySeconds`, not every second.
## Tickets from the General Store (2.2.0)
`Config.TicketMode = 'item'`: players buy the `lottery_ticket` item at the General Store (jrs_stores `store_config.lua`,
Miscellaneous tab, stock `globalLimit = 40` per `resetHours = 2`, server-wide, $1.00) and hand it in at a station
(consumed server-side, one per press, still limited by `MaxTickets` per draw). Keep the store price equal to `Config.TicketPrice`.
Set `Config.TicketMode = 'cash'` to go back to paying cash at the station. The item row is registered automatically.