Interface

# JRS Animation Menu
Animation, dance, walking-style, prop, favorite and contextual furniture interaction menu for RedM using `jrs_core`.
## Requirements
- `jrs_core`
- `oxmysql`
Start order:
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_animmenu
'''
## Database
No manual SQL import is required. The resource automatically creates the table configured in:
'''lua
Config.DatabaseTable = "jrs_animmenu"
'''
Favorites and custom animation commands are stored per character using the active JRS character `identifier` and `charidentifier`.
## Core integration
The resource connects directly to `jrs_core`.
- Character loading uses the JRS character-ready API/events.
- Current job is read from the active JRS character.
- No external menu/input API is required.
- Shared animations are routed through the server and validated for nearby players.
## Menu categories
The NUI is English and separates content into four tabs:
- Animations
- Walking
- Dances
- Props
Dance emotes, looped dance animations and shared dance animations are routed to the Dances tab. Walking styles are kept out of the normal animation list.
### JRS interaction refresh
- Uses a native RedM contextual prompt on **E**.
- Uses a projected, animated proximity arrow over supported furniture.
- The translucent preview ped is created **only after Interact is completed**; proximity alone never spawns it.
- The old header image was removed from both the main menu and input dialog.
- The old ground marker is disabled by default; a subtle proximity light remains configurable.
- Furniture scan/update intervals were tightened while avoiding per-frame object scans.
## Expanded animation library
This build adds 207 additional entries that were not already present by their underlying animation/scenario/emote/walking-style data:
- 88 animations
- 59 scenarios
- 18 emotes
- 24 walking styles/reset entries
- 18 clothing-motion animations
When a new animation had the same visible name as an existing entry but used different animation data, it is kept as an alternate entry instead of replacing the

# jrs_announce v2.0.0
Complete replacement for the old `jrs_announceV2` resource.
## What changed
- No VORP dependency.
- Uses `jrs_core`, `jrs_inventory`, and `oxmysql` only.
- One inventory item only: `newspaper`.
- Every item instance stores only `{ newspaper_id = <id> }` in JRS inventory metadata.
- Newspaper name, tribe name, logo and background are stored centrally in `jrs_newspapers`.
- Editing a newspaper updates every existing item immediately because items resolve the current database record when used.
- Deleting a newspaper invalidates every existing item linked to that ID.
- Server validates the exact `itemId` and `newspaper_id` before publishing.
- Admin UI supports create, edit, enable/disable, delete, refresh, and issuing another copy.
- Publications are saved in `jrs_newspaper_publications`.
## Installation
1. Import `install/jrs_announce.sql`.
2. Copy `install/item_images/newspaper.png` into the item-image directory used by your `jrs_inventory` UI if your inventory expects item images there.
3. Put the resource folder in your resources directory as `jrs_announce`.
4. Start in this order:
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_inventory
ensure jrs_announce
'''
5. In game, admins use:
'''text
/newspaperadmin
'''
Admin permission is read directly from `jrs_core` (`User.group`). No ACE permission or direct users-table lookup is used. Allowed JRS groups are configured in `
'''lua
Config.AdminGroups = {
    owner = true,
    admin = true,
    support = true,
}
'''
## Important item behavior
The `newspaper` definition's `items.metadata` column is a `varchar(1)` on this server - too narrow to ever hold real JSON, so `jrs_inventory`'s default-metadata
## Editing behavior
Editing does **not** create a new inventory item. An existing copy only keeps its stable `newspaper_id`, so a changed name/logo/background is read live from the
## v2.0.2
- Newspaper use now captures the exact `itemId` directly from the JRS inventory `jrs:use` event.
- No longer depends only on `jrsCore:getLastUsedId`, preventing false `missing valid data` errors when the inventory definition cache has not refreshed.
## v2.0.3 inventory compatibility
This build targets the current JRS Inventory API. The usable-item callback receives the exact `itemId` and `metaData` from `jrs_inventory`, so `jrs_announce` no

# jrs_backpack
Three wearable backpacks built specifically for REDEMPIRE Core (`jrs_core` and `jrs_inventory`).
## Backpack types
| Item name | Label | Object | Capacity |
| --- | --- | --- | ---: |
| `backpack_small` | Small Backpack | `p_ambpack02x` | 15 kg |
| `backpack_medium` | Medium Backpack | `p_ambpack01x` | 25 kg |
| `backpack` | Large Backpack | `p_ambpack04x` | 40 kg |
The original `backpack` item is retained as the large backpack, so existing player items continue to work.
## Features
- Every physical backpack item has its own persistent storage.
- Storage capacity is selected from the backpack type.
- Storage follows the same item when it is given, dropped or picked up.
- Using a backpack places its matching object in front of the player and starts a crouched inspection animation.
- Closing the backpack storage removes the ground object and returns the backpack to the player's back.
- Equipping another backpack replaces the visible object immediately.
- `/bag` shows or hides the equipped backpack object.
- Backpack objects are synchronized for nearby players.
- No backpack type can be placed inside another backpack.
- The object is removed when the player no longer owns its item.
## Starting the resource
The resource is inside `[JRS_newscript]`, so an existing server configuration line such as:
'''cfg
ensure [JRS_newscript]
'''
starts it automatically. After updating the resource, run:
'''text
restart jrs_backpack
'''
Item definitions are installed and reloaded automatically. If the inventory does not show the two new items immediately, restart it once:
'''text
restart jrs_inventory
restart jrs_backpack
'''
## Configuration
Edit `Config.Backpacks` in `config.lua` to change:
- Item names, labels and descriptions.
- Backpack item weights.
- Storage capacities.
- Object models.
- Bone, position and rotation values for each wearable object.
- Ground placement distance, rotation and inspection animation in `Config.Ground`.
The default attachment values are individually tuned for the three included RedM objects.

# JRS Camera Pro (v2.3.0)
Authentic 1890s RedM photography suite with server-authorized sessions, handheld cameras, synchronized tripod cameras, period photo studios, vintage shutter ani
---
## Key Features
1. **Authentic 1890s Magnesium Flash & Screen Blur**
   - Implements full-screen optical lens defocus/depth blur via `OJDominoBlur` animpostfx.
   - Smooth quadratic exposure bloom fade recreating physical photographic plate exposure.
   - 3D environmental dynamic lighting (`DrawLightWithRange`) synchronized across all nearby players.
   - Magnesium flash powder particle smoke effect (`exp_grd_flashbang` on `scr_net_photographer`).
   - Authentic camera shutter audio cues.
2. **Vintage Shutter & Operating Animations**
   - Authentic photographer stance: photographer positions behind the tripod camera holding the bulb shutter cable.
   - Shutter action: triggers `script_rc@abi3@ig@stage_01@ig2_photopose` -> `idle_takepic_blwphotographer` upon capture.
   - Grounded placement and pickup: uses crouching inspection animations (`WORLD_HUMAN_CROUCH_INSPECT`).
3. **Photo Studios (Blackwater & Saint Denis)**
   - **Correct Real-World Headings**: Camera faces backdrop directly (Blackwater: Camera 268° -> Backdrop; Saint Denis: Camera 88° -> Backdrop).
   - **Synchronized Backdrops**: 8 native Rockstar studio backdrop variations, switchable via `[W]` and `[S]` keys.
   - **Customer Posing Mechanics**: When standing on the studio portrait marker, clients can press `[A]` and `[D]` to cycle through 8 period poses (Gentleman, T
4. **Fixed / Tripod Camera (`fixedcamera`)**
   - Placed in the world using the `fixedcamera` inventory item (via `jrs_inventory` or `/fixedcam` command).
   - Deducts item on placement and restores it when picked up by the owner.
   - Solid collision and ground alignment using `p_camera01x`.
5. **Security & Synchronization**
   - Server-side token validation and distance verification for all capture and studio operations.
   - Clean network event architecture with zero memory leaks.
---
## Configuration (`config/config.lua`)
| Setting | Default | Description |
| :--- | :--- | :--- |
| `Config.Lang` | `'en'` | Interface language (`'en'` or `'ar'`) |
| `Config.KeyTakePhoto` | `0x07CE1E09` | Capture key (`[ENTER]`) |
| `Config.KeyLeaveCam` | `0x156F7119` | Exit camera key (`[BACKSPACE]`) |
| `Config.ChangeBackground` | `{ prev = 0xD27782E3, next = 0x8FD015D8 }` | Backdrop navigation (`[S]` and `[W]`) |
| `Config.General.PhotoFlash.EnableBlur` | `true` | Enables `OJDominoBlur` screen defocus effect |
| `Config.General.PhotoFlash.DurationMs` | `450` | Flash bloom and blur duration in milliseconds |
| `Config.FixedCamera.ItemName` | `'fixedcamera'` | Database inventory item for the tripod camera |
| `Config.FixedCamera.RemoveItemOnPlace` | `true` | Consume item on placement and restore on pickup |
| `Config.Server.RequireStudioJob` | `false` | Set to `true` to restrict studio cameras to specific jobs |
---
## Commands
- `/fixedcam` - Place a tripod camera at your feet (requires `fixedcamera` item in inventory).
- `/camgallery` - Open the Rockstar Social Club photo gallery.
- `/camdiag` - Print diagnostic information to the F8 console.
---
## Dependencies

# jrs_chat 2.0.0
JRS Chat for RedM / `jrs_core`, rebuilt around the readable visual style and workflow ideas supplied in `JRS Chat` while keeping the JRS integrations open and e
## Requirements
- `jrs_core`
- `oxmysql`
- RedM / Cfx server
## Installation
1. Rename/use the resource folder as `jrs_chat`.
2. Disable the stock `chat` resource if it would create a second chat UI.
3. Start dependencies before this resource:
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_chat
'''
The manifest includes `provide 'chat'` for resources that depend on the standard chat resource.
## What was ported from the supplied JRS chat idea/theme
- Original readable JRS UI textures used by the chat (`bg_1`, `bg_2`, `bgorigin`, `box_bg`).
- JRS fonts used for tabs/header styling.
- Antique message-card visual style.
- Local / Global / Staff tabs.
- Me / Do / Try quick buttons.
- Emoji tab, categories and search.
- Message history and suggestions.
- Character-name chat header with optional badge and time.
- `/global`, `/say`, `/whisper`, `/reply`, `/togglechat`, `/toggleoverhead` compatibility aliases.
- `/staff` alias while the original JRS `/ac` command remains available.
- 3D-only `/me`, `/do`, `/try` by default with line-of-sight support.
- Optional chat console logging.
- Optional join/leave system messages.
- Photo, nickname and mute systems kept in JRS and styled with the same UI language.
No JRS encrypted Lua logic is required by this resource. The resulting JRS resource is independent.
## Music system
Music is command-first and then controlled through an in-game UI.
### Player music
`/music`
- Available to normal players when `Config.Music.allowPersonal = true`.
- Opens **Personal Music Player**.
- Accepts a YouTube URL or an 11-character YouTube video ID.
- Play / Pause / Stop / Volume controls.
- Audio stays completely local to that player; no server event broadcasts the personal track.
### Staff global music
`/musicall`
- Requests the **Global Music Control** UI.
- Permission is validated with `JRSChat.IsStaff()` on the server.

# jrs_church_bells
Church bell resource for RedM using RDR2's native church bell sound set.
## Included
- Valentine church bell sound: `CHURCH_BELL_SOUNDS / VAL_SINGLE_TOLL`
- Automatic in-game schedule:
  - 06:00 = 6 tolls
  - 12:00 = 12 tolls
  - 18:00 = 6 tolls
- Manual native prompt near the Valentine church.
- JRS Core job/admin permission checks.
- Admin groups enabled by default: `owner`, `admin`, `support`.
- Allowed church jobs enabled by default: `priest`, `preacher`, `church`.
- Server-side cooldown and permission validation.
- Optional ACE permission: `jrs.churchbells`.
- Admin/job command: `/churchbell [location] [tolls]`.
## Install
1. Copy `jrs_church_bells` into your resources folder.
2. Make sure `jrs_core` starts first.
3. Add:
'''cfg
ensure jrs_core
ensure jrs_church_bells
'''
## Valentine coordinates
The sound origin is already set at the Valentine church bell:
'''lua
vector3(-230.11424, 797.50195, 135.25150)
'''
The default manual interaction point is:
'''lua
vector3(-231.75000, 796.38000, 124.63000)
'''
If your custom Valentine church interior places the bell rope/control somewhere else, only change
`interactionCoords` in `config.lua`.
## Job permission
Edit:
'''lua
Config.Permissions.jobs = {
    priest = 0,
    preacher = 0,
    church = 0
}
'''
The number is the minimum allowed job grade.
## Admin permission

# jrs_city
Version 1.2.1
Native RedM location notifications for `jrs_core`.
## How it works
The client reads RedM native map-zone hashes and resolves the current location using this priority:
1. Town
2. Printed map location
3. Written map location
4. Water locations
5. District
6. State
The notification is a single transparent NUI element, so its background, title, district, state, time, temperature and wind always appear and disappear together
The bundled native zone metadata contains 320 mapped RedM zones.
## Install
'''cfg
ensure jrs_core
ensure jrs_city
'''
## Test
'''text
/jrscitytest
'''
With `Config.Debug = true`:
'''text
/jrscitydebug
'''
## Main settings
Edit `config.lua` to control notification size, position, duration, details and zone detection interval.
The default background is `html/assets/box_a_bg_1.png` and is rendered at 340px wide, smaller than its original 432px size.
## Exports
'''lua
local zone = exports.jrs_city:GetCurrentZone()
local city = exports.jrs_city:GetCurrentCity()
local inValentine = exports.jrs_city:IsInCity('Valentine')
'''
## Notification sound
The supplied MP3 is bundled as:
'''text
html/assets/zone_open.mp3
'''
Configure it in `config.lua`:
'''lua
Config.Notification.Sound = {
    Enabled = true,
    File = 'assets/zone_open.mp3',

# REDEMPIRE FreeCam for RedM
Standalone RedM free camera with jrs_core job access and Red Dead photo-mode filters.
## Installation
1. Rename the folder to `jrs_freecam` and place it in your resources directory.
2. Make sure `jrs_core` starts first.
3. Add:
'''cfg
ensure jrs_core
ensure jrs_freecam
'''
## Job access
Edit `Config.JobRequirement.Jobs` in `config.lua`:
'''lua
Config.JobRequirement = {
    Enabled = true,
    Jobs = {
        photographer = 0, -- job name = minimum grade
    },
}
'''
To allow more than one job:
'''lua
Jobs = {
    photographer = 0,
    reporter = 2,
}
'''
## Controls
- `/freecam` or `F6` when key mapping is supported: open/close freecam
- Arrow Up/Down: forward/backward
- Arrow Left/Right: move left/right
- Q/E: move up/down
- Left Shift: faster movement
- Mouse: camera rotation
- Mouse wheel: zoom
- A/D: camera roll
- Page Up/Page Down: previous/next filter
- B: reset roll and zoom
- `/freecamfilter`: next filter
- `/freecamprevfilter`: previous filter
- `/freecamhelpers`: show/hide controls
## Filters
The filter list and application method were copied from `jrs_camera`:
- PhotoMode_FilterGame01-18
- PhotoMode_FilterModern01-10

# REDEMPIRE Gramophone
A synchronized gramophone system built directly for `jrs_core`.
## Features
- Fixed gramophone stations with per-job access.
- YouTube link playback with synchronized play/pause and seek state.
- Distance-based volume attenuation.
- Volume up/down, rewind, forward, and timeline seek.
- Shared or per-character playlists.
- Song history in the UI.
- Optional portable gramophone item using `jrs_inventory`.
- Portable gramophones persist in the database and can be taken back by their owner.
- Optional play cost and Discord webhook logging.
- Automatic database table creation.
- No framework adapter file; the resource connects directly to `jrs_core`.
## Requirements
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_inventory
ensure jrs_gramophone
'''
`jrs_inventory` is only required when `Config.Portable.Enabled = true`.
## Portable item
If portable gramophones are enabled, add an item named `gramophone` to your REDEMPIRE items table and mark it usable.
Example:
'''sql
INSERT INTO `items`
(`item`, `label`, `limit`, `can_remove`, `type`, `usable`, `descriptions`, `metadata`, `category`)
VALUES
('gramophone', 'Gramophone', 2.00, 1, 'item_standard', 1, 'A portable gramophone', '0', 'tools')
ON DUPLICATE KEY UPDATE
`label` = VALUES(`label`),
`limit` = VALUES(`limit`),
`can_remove` = VALUES(`can_remove`),
`type` = VALUES(`type`),
`usable` = VALUES(`usable`),
`descriptions` = VALUES(`descriptions`),
`metadata` = VALUES(`metadata`),
`category` = VALUES(`category`);
'''
## Configuration
Edit `config.lua`.
Important sections:
- `Config.Stations` - fixed locations, allowed jobs, range and initial volume.
- `Config.Portable` - portable item and placement settings.

# jrs_killcam
Standalone client-side cinematic kill camera for RedM. It detects a confirmed
firearm hit, calculates a path from the shooter's hand/muzzle to the impact, and
plays a short local slow-motion camera. Damage, death and server ownership are
not replaced or delayed.
## Installation
1. Copy `jrs_killcam` into the server's resources directory.
2. Add `ensure jrs_killcam` to `server.cfg`.
3. Restart the resource or server.
No framework, inventory, database or server-side dependency is required.
## Default behaviour
- Activates for lethal firearm hits.
- Supports players and human NPCs.
- Runs only on the shooter's client.
- Does not freeze, revive, damage or make either player invincible.
- Restores the gameplay camera and time scale on completion, skip, player
  death, pause, error, resource stop or resource restart.
- Five-second cooldown prevents repeated cameras during rapid combat.
## Test
Aim at a player or human NPC and run:
'''text
/jrs_killcam_test
'''
This tests the camera without damaging the target. The test command can be
disabled in `config.lua` after setup.
For the real trigger, kill a supported target with a revolver, pistol, repeater,
rifle, sniper rifle or shotgun from at least the configured minimum distance.
## Important configuration
- `Config.Trigger.FatalHitsOnly`: use only lethal hits.
- `Config.Trigger.HeadshotsAlways`: allow non-lethal headshots too.
- `Config.Trigger.ChancePercent`: frequency from 0 to 100.
- `Config.Trigger.MinimumDistance`: prevents awkward point-blank cameras.
- `Config.SlowMotion.TimeScale`: local visual time scale.
- `Config.Camera`: travel time, FOV and offsets.
- `Config.Targets`: players, human NPCs and animals.
- `Config.BlockedWeapons`: weapon names that must never trigger the camera.
## Exports
'''lua
local started = exports.jrs_killcam:Play(targetPed, impactCoords)
local active = exports.jrs_killcam:IsActive()
'''
`impactCoords` may be omitted. `Play` intentionally bypasses the normal kill,
distance and cooldown checks so another trusted client resource can request a
cinematic directly.
## Technical note