Jobs

REDEMPIRE Bounty Board v2.1.0
=======================
Dependencies
------------
- oxmysql
- jrs_core
Recommended start order
-----------------------
ensure oxmysql
ensure jrs_core
ensure jrs_bounty
Installation
------------
1. Replace the old jrs_bounty resource with this folder.
2. Keep the resource folder name as: jrs_bounty
3. The server creates the required tables automatically.
4. Review config.lua before starting the resource.
Bounty-only build
-----------------
- The complete heist/robbery system was removed.
- jrs_lockpick is no longer used.
- jrs_inventory is no longer required by this resource.
- Available bounty missions and sheriff bounty notices remain.
Group bounty system
-------------------
- Open the Group tab on the bounty board.
- The leader adds players directly by server ID.
- Config.GroupMaxMembers controls the total group size including the leader.
- Only the group leader can start or abort a bounty mission while grouped.
- Starting a bounty sends the same mission to every current group member.
- Only one networked enemy wave is spawned by the leader, preventing duplicate NPC waves.
- Group membership is locked while a mission is active.
- Group members cannot start another bounty while assigned to the leader's active mission.
- The poster reward is a TOTAL reward. It is split between online mission participants at completion.
- Integer remainders are distributed one dollar at a time so the full configured reward is paid.
- The normal bounty cooldown is applied to every mission participant after success.
- Groups are session-only and are not stored in the database.
Important config options
------------------------
- Config.Jobs
- Config.BountyBoards
- Config.GroupMaxMembers
- Config.MaxSheriffReward
- Config.MinimumMissionSeconds
- Config.MissionCompletionDistance

# jrs_delivery 3.3.3 — jrs_core
This resource is built for `jrs_core` and uses the core for character data, money, XP, notifications and the 3D destination waypoint.
## SS-Deliveryjob port
Locations, item names and per-mission XP were ported from the SS-Deliveryjob asset pack's `config.lua`
(SS-Deliveryjob's actual game logic is escrow-protected, so only its readable config data could be
carried over — the engine below is jrs_delivery's own). `Config.AllowAllRoutes = false` and each
location's single `destinations` entry recreate SS-Deliveryjob's one-city, one-cargo, one-fixed-destination
design as a 12-city ring: Valentine -> Wallace Station -> Strawberry -> Blackwater -> McFarlane's Ranch ->
Armadillo -> Wapiti Indian Reservation -> Van Horn -> Saint Denis -> Rhodes -> Emerald Ranch -> Annesburg -> (back to Valentine).
A Discord webhook log on delivery completion is available via `Config.Discord` (disabled by default —
set your own webhook URL, never reuse one shipped inside a downloaded pack).
## Multi-cargo contracts
A destination can offer multiple cargo contracts. The player selects:
1. Destination.
2. Cargo type.
3. The contract with its own time, payment, XP, wagon model and maximum speed.
The selected cargo is validated on the server when the delivery starts, when the wagon is registered and when the delivery is completed.
## Cargo defaults
Each cargo type has default settings in `Config.CargoPresets`:
'''lua
Config.CargoPresets.coal_shipment = {
    label = 'Coal',
    description = 'Heavy coal load out of Emerald Ranch. 30-50 units, slows the wagon.',
    wagon = 'wagon04x',
    timer = 1850,
    priceMin = 650,
    priceMax = 850,
    xp = 58,
    maxSpeed = 6.0,
    props = {
        -- Cargo objects...
    }
}
'''
`maxSpeed` uses game speed units in meters per second. The UI displays the approximate value in km/h.
## Cargo offered by a departure city
When no exact route configuration exists, the route uses the departure city's `cargoOptions`:
'''lua
Config.Locations.valentine = {
    cargoOptions = { 'raspberry' },
    destinations = { 'wallace_station' },
    -- ...
}
'''
This makes `raspberry` available from Valentine to Wallace Station only (`Config.AllowAllRoutes = false`).

## REDEMPIRE Inventory legacy item migration
Older `jrs_doctors` SQL used the `items.limit` column as a stack limit (for example `birdalert = 10`). The current `jrs_inventory` uses the same column as **wei
This build automatically normalizes all REDEMPIRE Doctors item definitions. If the console prints that legacy definitions were repaired, run `restart jrs_invent
# REDEMPIRE Doctors 4.4.5-jrs
`jrs_doctors` is the REDEMPIRE-only medical/doctor system for RedM. The runtime is connected directly to `jrs_core` and `jrs_inventory`; there is no framework a
## Requirements
- `oxmysql`
- `jrs_core`
- `jrs_inventory`
Recommended start order:
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_inventory
ensure jrs_doctors
'''
## Installation
1. Keep the resource folder name exactly `jrs_doctors`.
2. Import `sql/jrs_doctors.sql` into the server database.
3. Copy the PNG files from `items/` into `jrs_inventory/html/img/items/` when your inventory build loads item images from that folder.
4. Configure jobs, hospitals, payments, access, diseases, storage and doctor features under `config/`.
5. Start the resource after `jrs_core` and `jrs_inventory`.
The main SQL file creates the REDEMPIRE Doctors tables and registers the medical inventory items using the REDEMPIRE inventory item schema. A copy of only the i
## REDEMPIRE Core integration
Server-side integration is implemented in `server/jrs_bridge.lua` and uses:
'''lua
local REDEMPIRE = exports.jrs_core:getCoreApi()
local character = REDEMPIRE.getCharacter(source)
'''
The script uses REDEMPIRE character data for:
- character identifier and character name
- doctor job and grade
- cash, gold and role currency
- job changes
- server-authoritative payments
- access checks and medical actions
Currency mapping is configured in `config/core.lua`:
'''lua
Config.REDEMPIRE.Currency = {
    cash = 0,
    gold = 1,
    rol = 2
}
'''
Character-ready integration uses the REDEMPIRE character-ready exports/events. This allows the resource to recover correctly when it is restarted while players 

# JRS Fight Arena
An open reimplementation of the SS-FightArena feature set, rebuilt on `jrs_core`
with no escrow, no jQuery/materialize and no external menu or input resource.
Every string is English and lives in `config/config.lua`.
## Features
- Multiple configurable arenas, each with an organizer NPC and a fight zone.
- Native prompts on the organizer: **Training (G)**, **Start Fight (Q)**,
  **Scoreboard (B)**.
- Paid training bouts against configurable opponents (model, random health
  range, combat movement) with the nine numbered fighting lessons.
- **Challenge browser**: pick an opponent from a searchable list of eligible
  players showing their win/loss record, or enter a server id by hand.
- Incoming challenge card with the challenger's initials, record and a live
  request-timeout bar.
- Both fighters walk to the fight zone; the countdown only starts once both are
  inside it, and shows a versus header plus a draining progress ring.
- **Live HUD**: opponents remaining during training; both fighters' health bars
  and a fight clock during a duel.
- **Result banner** with the fresh record and win streak.
- Duels resolve server-side on the health floor, on death, or on leaving the
  arena. Quitting mid-fight counts as a loss.
- Persistent rankings with win streaks and a full scoreboard: medal ranks, win
  ratio, streak column, search box and your own row pinned and highlighted.
- Unified notifications through `jrs_core`, so arena messages use the same
  renderer and language styling as the rest of the server.
- Per-job XP through `jrs_core` (job key `fight`).
- Owner-only administration through the shared `jrs_scriptadmin` panel, the same
  way `jrs_farming` does it.
## Dependencies
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_scriptadmin   # optional; required only for the owner admin panel
ensure jrs_fight
'''
`jrs_fight` lives in `[JOBS]`, which `server.cfg` already starts with
`ensure [JOBS]` after `jrs_core`, `oxmysql` and the shared JRS resources.
## Flow
| Step | Where | What happens |
| --- | --- | --- |
| Training | organizer prompt (G) | `Config.TrainingPrice` is charged, the arena's `training` peds spawn, the HUD counts opponents, lessons 1..8 play, lesson 9 
| Challenge | organizer prompt (Q) | The challenge browser lists eligible players with their records; pick one or type an id. |
| Walk in | after accept | Both fighters are told to go to the fight zone and report when they arrive. |
| Countdown | both in zone | Versus header, draining ring, 9..1, both frozen, then `FIGHT`. |
| Duel | after the countdown | Both health bars are live in the HUD; health is relayed server-side. |

# REDEMPIRE Fishing Modifications
This version includes a fishing skill game, a circular waiting indicator, bait consumption on cast, optional job restrictions, and configurable XP rewards per f
## Skill Game
When a fish bites, press `R` while the moving fish icon overlaps the target fish icon. The target moves after every successful hit. The default requirement is t
Configure the system in `Config.FishingSkillGame` inside `config.lua`:
- `Enabled`: Enables or disables the skill game.
- `RequiredHits`: Number of successful hits required.
- `AllowedMisses`: Number of allowed misses.
- `ZoneWidth`: Target area width.
- `TravelTimeMs`: Time for the moving icon to cross the bar.
- `TimeLimitMs`: Total attempt time.
- `PullToPlayerSpeed`: Fish pull speed after success.
- `LandingDistance`: Distance required to begin the landing animation.
- `AutoLandTimeoutMs`: Fallback timeout to prevent the fish from getting stuck.
- `DefaultKey`: Default key label.
- `ControlHash`: RedM control hash used as the fallback input.
## Waiting Indicator
Configure the circular waiting indicator in `Config.FishingWaitUI`.
## Job Restriction
Configure job access in `Config.FishingJob`. The restriction is disabled by default with `Enabled = false`.
## Fishing XP
Configure XP rewards in `Config.FishingXP`. Each fish model can have its own XP value in the `Rewards` table. XP is awarded through the REDEMPIRE Core API after