Activities

# jrs_beekeeping
`jrs_beekeeping` is a complete RedM beekeeping/farm resource converted to the REDEMPIRE stack. It uses `jrs_core` for character and currency handling, `jrs_inve
## Requirements
- `jrs_core`
- `jrs_inventory`
- `oxmysql`
No legacy framework adapter or framework.lua is used.
## Main features
- Persistent player-owned beehives.
- Small, medium and large hive kits as usable `jrs_inventory` items.
- Placement preview and server-side placement validation.
- Hive ownership by REDEMPIRE `identifier` + `charIdentifier`.
- Complete colony management: queen, food, water, cleaning, smoker, medicine, repair, queen replacement and upgrades.
- Health, hunger, water, cleanliness, stress, queen health, swarm strength and forage quality simulation.
- Diseases, offline lifecycle progression and seasonal production modifiers.
- Honey, beeswax, propolis and royal-jelly harvesting.
- Hive XP/level progression and character profile progression.
- Bulk farm actions.
- Bee Market for buying supplies/hive kits and selling products.
- Cash and Gold support through `jrs_core` currency APIs.
- Persistent streamed hive props.
- NUI shop/farm interface, notifications and sounds.
- Optional Discord webhook logs.
- Rate limits, distance checks, transaction locks and rollback paths around inventory/currency operations.
## 1.1.0 deep-fix notes
This build is aligned against the supplied/current REDEMPIRE APIs rather than a generic framework adapter.
- Shared per-player mutation lock serializes Bee Market, hive placement and farm inventory/economy mutations.
- Owner-level lifecycle lock prevents the global hive tick and live player actions from overwriting each other after an awaited MySQL call.
- `jrs_inventory` split-stack removals use exact `itemId` entries and roll back earlier stacks with their metadata if a later stack fails.
- Hive placement, upgrade and dismantle use direct delta synchronization instead of forcing every client to re-query the database.
- Menu/HUD synchronization is read-only; lifecycle state is persisted only by authoritative mutation/tick paths.
- Character-ready gating prevents hive refresh requests during character selection/loading.
- NUI open retries stop as soon as the UI is ready, and character unload/resource stop release only state owned by this resource.
- Server distance checks, transaction idempotency, finite-number checks and action rate limits remain authoritative.
- Normal success/compatibility console noise is hidden while `Config.Main.Debug = false`; critical rollback/startup errors remain visible.
## Installation
1. Copy the folder as:
'''text
resources/[jrs]/jrs_beekeeping
'''
2. Import:
'''text
sql/jrs_beekeeping.sql
'''
3. Copy the item images from:

# jrs_canon v1.1.0
REDEMPIRE cannon / Gatling deployment system for RedM.
## v1.0.7 changes
- Placements are **persisted in database** (`jrs_canon_placements` table) across server and resource restarts.
- Inventory operations are **verified with callbacks** on both placement (`jrsCore:subItem`) and recovery (`jrsCore:addItem`), preventing item loss or duplicati
- Enforced `Config.AllowAnyPlayerRecover`: when set to `false`, only the original owner character can recover deployed artillery.
- Client re-sync net event handlers properly registered for `jrs_character:isPlayerReady`, `jrs_core:client:characterReady`, and `jrs_canon:client:requestSync`.
- Completed Arabic localization in `locales/ar.lua` (translated English strings: placement title, cancel, recover, and added not_owner).
- Clean entity teardown on resource stop without wiping persistent database records.
## Dependencies
- `jrs_core`
- `jrs_inventory`
- `oxmysql`
## SQL Setup
Import the SQL schemas if not already applied:
1. `sql/jrs_canon_items.sql` (registers cannon and gatling inventory items)
2. `sql/jrs_canon_placements.sql` (table schema for persisted deployments; automatically initialized on boot)
## Controls
- Use the item from the inventory: the inventory closes and placement starts
  (same NUI panel and keys as jrs_housing furniture placement)
- Crosshair: move the gun
- Arrow Left / Right (or mouse wheel): rotate - Q / E: turn 45 degrees
- Arrow Down / Up: lower / raise (-0.5 .. +3.0 m) - F: back onto the ground
- L: lock position - X: speed (Precise / Normal / Fast) - R: reset
- G: place (only inside Config.MaxPlacementFromPlayer) - DELETE: cancel
- At a deployed gun: E use, R remove and get the item back
- Seated on the gun: centre reticle is shown, gold while firing

# jrs_cinema v1.1.9
YouTube cinema changes:
- YouTube image is grayscale by default (`Config.YouTube.BlackAndWhite = true`).
- Video and YouTube audio are only exposed while the player is in the same RedM interior room as the projection screen (`Config.YouTube.SameRoomOnly = true`).
- The room check follows PMMS' proven RedM method: `GetInteriorFromEntity` + `GetRoomKeyFromEntity`.
- An invisible local RDR2 projection target is created only as the room-reference entity; it has no collision and no DUI.
## v1.1.7 - PMMS-style RedM YouTube projection
YouTube display now follows the proven RedM method used by PMMS: a single fixed
world coordinate is projected every frame with `GetScreenCoordFromWorldCoord`,
and the NUI video size is calculated from camera FOV and camera distance. This
removes the old 4-corner homography entirely and still avoids `CreateDui`.
Screen tuning is intentionally simple: edit only `coords` and `videoSize` under
`Config.YouTube.FixedScreens`. `coords` is the centre of the video in the world.
# jrs_cinema
Standalone JRS cinema/theatre system for RedM using the RDR2 built-in theatre animscenes and magic-lantern movie assets.
## Requirements
- jrs_core
- OneSync/server entity coordinates for server-side ticket-seller distance validation.
## Install
1. Put `jrs_cinema` in your resources folder.
2. Ensure `jrs_core` starts first.
3. Add `ensure jrs_cinema` to server.cfg.
## Flow
Seller NPC -> hold G -> choose show/movie -> server validates distance and balance -> server removes Money/Gold -> synchronized countdown -> players inside `Con
## Main config
- `Config.ShowStartTime = 60`
- `Config.PriceType = 0` (Money) or `1` (Gold)
- `Config.DistanceStart = 150.0`
- `Config.ShowLockSeconds = 900`
- Ticket locations, NPCs, prices and show lists are all editable in `config.lua`.
## jrs_core integration
Uses `exports.jrs_core:getCoreApi()`, `getCharacter`, `removeMoney` and `NotifyRightTip`.
## Notes
The underlying show/movie asset identifiers are Rockstar RDR2 game assets. Theatre engine behavior was implemented with reference to the MIT-licensed `xK3LY/red
## v1.1.3 - Managed YouTube playback
Movie cinemas can now render a synchronized YouTube embed on the in-world projection screen using Cfx DUI/runtime textures.
Management is server-authoritative. A player can submit/control YouTube when one of these is true:
- `exports.jrs_core:IsAdmin(source)` returns true. This automatically follows `Config.AdminGroups` inside jrs_core.
- Their job from jrs_core exists in `Config.YouTube.AllowedJobs` and meets the configured minimum grade.
- Optional ACE permission `jrs.cinema.manage` is allowed when `UseAcePermission = true`.
Core administration is enabled with:
'''lua
UseCoreAdmin = true
'''
Default allowed job:

# jrs_crafting 6.0.0-jrs
Crafting system converted to use **jrs_core** and **jrs_inventory** directly.
## Verified against supplied builds
This package was reviewed against the supplied `jrs_core` build from 2026-08-12 and `jrs_inventory` v1.5.4. It uses the current account-group API, Character Rea
## Requirements
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_inventory
ensure jrs_crafting
'''
No external progress-bar resource is required. The resource uses its internal craft timer and the supplied NUI.
## Main integration
Server integration is in:
'''text
server/services/jrs.lua
'''
It uses:
- `exports.jrs_core:getCoreApi()` for characters, money/gold and notifications.
- `exports.jrs_core:GetXP()` / `AddXP()` for crafting level and XP.
- `exports.jrs_core:IsCharacterReady()` / `GetCharacterState()` for character state.
- `exports.jrs_inventory:jrs_inventoryApi()` for item counts, capacity, add/remove, weapons and usable items.
Client code waits for `jrs_core` character readiness before enabling crafting prompts.
## Item installation
Import:
'''text
sql/jrs_items.sql
'''
The installer uses the current REDEMPIRE item columns:
'''text
item, label, limit, can_remove, type, usable, descriptions, metadata, category
'''
`limit` is the per-item weight used by `jrs_inventory`. Existing rows are not overwritten because the installer uses `INSERT IGNORE`.
Copy any missing item PNGs into:
'''text
jrs_inventory/html/images/items/
'''
## Configuration
Important files:
'''text
config/jrs.lua          # jrs_core / jrs_inventory resource names and compatibility timeouts
config/settings.lua     # timings, keys, distances and notifications
config/integrations.lua # REDEMPIRE XP, crafting price and webhook logging
config/security.lua     # server-authoritative anti-abuse validation
config/admin.lua        # recipe administration and audit options

## In-game destination builder (1.1.3)
Administrators can open the Fast Travel admin menu and use the **DESTINATIONS** tab to create persistent travel locations without editing Lua files. The builder
Locations created from the admin menu are saved in the `jrs_fasttravel_destinations` SQL table, restored after resource/server restarts, and synchronized live t
# REDEMPIRE Fast Travel
`jrs_fasttravel` is the REDEMPIRE-native rewrite of the stagecoach fast travel resource for RedM.
The resource now integrates directly with `jrs_core`. The old multi-core bridge and its framework selection files are not part of this build.
## Resource
- Name: `jrs_fasttravel`
- Version: `1.1.2`
- Game: RedM / RDR3
- Core: `jrs_core`
- Author: `jrs`
## Main features
- Stagecoach fast travel between configured towns.
- Server-authoritative destination validation and payment.
- Cash or gold payment through `jrs_core`.
- Distance-based dynamic fares.
- Time-of-day fare multipliers.
- Server-issued one-use travel quotes.
- Per-city service enable/disable state.
- Global service enable/disable state.
- Job and grade restrictions per destination.
- Destination population display.
- Spawned coach/driver/horse cleanup.
- Travel failure refunds.
- Security rate limits and travel tokens.
- Built-in NUI notifications with REDEMPIRE notification fallback.
- Administrator menu using `jrs_core` staff groups.
- Optional database and Discord audit logging.
## Requirements
Required:
'''text
jrs_core
'''
Recommended / required by the normal REDEMPIRE stack:
'''text
oxmysql
'''
`oxmysql` is a required dependency in this build because administrator-created Fast Travel destinations are stored in SQL. The destination table is created auto
No inventory resource is required by Fast Travel.
## Installation
1. Extract the folder as exactly:
'''text
jrs_fasttravel
'''