Admin

# JRS Anti-Cheat — RedM Edition 2.1.1-jrs
## JRS changes (2026-10-02)
- Integrity challenges, resource-stop kicks and heartbeat audit start only after
  the client's first heartbeat (download finished) — first-time players are no
  longer kicked while downloading. `NeverLoadedKickMs` (15 min, counted from
  `playerJoining`) kicks an in-world client that never starts jrs_anticheat.
- Resource-stop reports are re-checked after 4 s; players who simply quit are not
  logged or kicked.
- `removeAllWeaponsEvent` is blocked only when the target is another player's
  ped (scripts may strip NPC/bot weapons).
- Invincibility telemetry off by default (`ReportInvincibility`) and skipped in
  safezones / while dead (state bags `inSafeZone`, `isDead`).
- `DiscordIgnoreCodes`: teleport and unknown-origin signals stay console-only.
- Unknown-entity auto-ban disabled; console spam off; MaxActive raised;
  restart grace 180 s. Original zip: `_jrs/_backups/jrs_anticheat_2.1.0_orig_2026-10-02`.
JRS Anti-Cheat is a framework-independent security resource for RedM. It can
run alongside `jrs_core`, `jrs_inventory`, and other resources without changing
their database or framework APIs.
## Installation
1. Remove or disable the old `Anti-Injection` resource.
2. Copy this folder to the server and keep its exact name: `jrs_anticheat`.
3. Add the following lines to `server.cfg` before `ensure jrs_anticheat`:
'''cfg
add_ace group.admin jrs_anticheat.bypass allow
add_ace group.admin jrs_anticheat.inspect allow
add_ace group.admin jrs_anticheat.manage allow
ensure jrs_anticheat
'''
The ACE permissions provide the following access:
- `jrs_anticheat.bypass`: exempts trusted administrators from applicable
  anti-cheat checks.
- `jrs_anticheat.inspect`: allows administrators to inspect entity-spawn logs.
- `jrs_anticheat.manage`: allows administrators to view and remove persistent
  entity-spawn bans.
The administrator identifiers must already inherit `group.admin`. Restart the
entire server after installing or updating the resource.
No SQL installation or `screenshot-basic` dependency is required.
## Main Protection Layers
The resource includes server-side protection against:
- Ped, animal, prop, and vehicle spawn flooding.
- Excessive active scripted entities per player.
- Entities created too far away from their network owner.
- Explicitly denied entity models.
- Particle, projectile, and explosion flooding.
- Amplified explosion damage and camera shake.

# REDEMPIRE Doorlocks 6.1.0
RedM door locking system for REDEMPIRE Core / REDEMPIRE Character / REDEMPIRE Inventory.
## Runtime
- Resource name: `jrs_doorlocks`
- Native RedM/RDR3 gameplay prompts only (`G` lock/unlock, `X` lockpick).
- Door registration is native prompts too (`E` select physical door, `X` cancel).
- Door prompt group title uses the original SQL door name.
- Server-authoritative REDEMPIRE job/grade/character/item access.
- REDEMPIRE Core and REDEMPIRE Character restart resynchronization without requiring the player to reconnect.
- 30-second forgotten-door auto close/re-lock remains server controlled.
- Successful lockpick robbery doors remain open until manually locked or the resource/server restarts.
- Resource/server start restores `locked_on_start`.
- Normalized SQL tables use the `jrs_doorlock*` names.
- If REDEMPIRE tables are empty, a compatible normalized legacy doorlock table family can be imported automatically before bundled seeding.
## Start order
'''cfg
ensure oxmysql
ensure jrs_core
ensure jrs_character
ensure jrs_inventory
ensure jrs_doorlocks
'''
The HTML/NUI is retained only for administration, the editor form, the inspector and notifications. Both nearby door interaction AND physical door selection dur
## Registering a door
1. `/createdoor` (or ADD DOOR in `/dooradmin`) opens the editor form.
2. Fill in name / access / auto-close and save. The form hides itself.
3. Aim at the physical door. The native prompt group shows `SELECT DOOR` (`E`) and `CANCEL` (`X`); the group title says whether the aimed object is a usable doo
4. Press `E` to confirm. A double door asks for the second leaf before it saves.
Every failure now returns a specific message (nothing selected, unreadable door, hash already registered, too far, no permission).

# jrs_hurricane
Ties world weather to txAdmin's scheduled-restart announcements. Every time
txAdmin broadcasts a restart warning (`txAdmin:events:scheduledRestart`,
default warnings at 30/15/10/5/4/3/2/1 minutes remaining -- configured in
txAdmin's own scheduler), the storm gets one stage worse:
1. `clouds` -- dark clouds gather
2. `overcastdark` -- sky turns grey, wind picks up
3. `rain` -- rain starts falling
4. `thunderstorm` -- thunder and lightning (native RDR2 weather effects, no
   extra scripting needed)
5. `hurricane` -- full storm, right around the final warning
Each stage change is broadcast to every player via weathersync's own server
API (`exports.weathersync:setWeather` / `:setWind`), so it stays in sync
exactly like the `/weather` command, and a bilingual (EN/AR) tip notification
goes out with it.
If an admin postpones/skips the restart (`txAdmin:events:scheduledRestartSkipped`),
the weather calms back down automatically.
## Requirements
- `weathersync` and `jrs_core` must be running (declared as `dependency` in
  `fxmanifest.lua`).
- This is a txAdmin server; if txAdmin's monitor is ever unavailable, no
  `scheduledRestart` events fire and the storm never starts -- that's by
  design, there's nothing to escalate towards.
## Config
See `config/config.lua`:
- `Config.Enabled` -- master on/off switch.
- `Config.TimeStageSeconds` / `Config.Stages` -- when each stage kicks in and
  what weather/wind it applies.
- `Config.RevertOnSkip` -- calm the weather back down if the restart is
  postponed.
- `Config.TestAce` / `Config.AdminScope` -- who can use the manual test
  commands.
## Manual testing
'''
/hurricanetest <secondsRemaining>   -- jump the storm to the stage that time would trigger
/hurricanestop                      -- clear the storm and restore calm weather
'''
Both commands require the `jrs.hurricane` ACE permission (`add_ace group.admin
jrs.hurricane allow`) or `jrs_admin` admin access; the server console can
always use them.

# 💻 Spooner
Documentation relating to the jrs_spooner.
## 1. Installation
jrs_spooner works Standalone.
To install jrs_spooner:
- Download the resource
  - On [Github](https://github.com/Spooni-Development/jrs_spooner)
- Ensure that all requirements are installed
  - [uiprompt](https://github.com/kibook/redm-uiprompt)
- Add the exec to the server.cfg
  '''
    exec @jrs_spooner/permissions.cfg
  '''
- Add the permissions
    '''
    add_ace builtin.everyone jrs_spooner.view allow
    add_ace builtin.everyone jrs_spooner.spawn allow
    add_ace builtin.everyone jrs_spooner.modify.own allow
    add_ace builtin.everyone jrs_spooner.delete.own allow
    add_ace builtin.everyone jrs_spooner.properties allow
    add_ace builtin.everyone jrs_spooner.noEntityLimit allow
    add_ace builtin.everyone jrs_spooner.modify.other allow
    add_ace builtin.everyone jrs_spooner.delete.other allow
    '''
- Drag and drop the resource into your resources folder
  - `jrs_spooner`
- Add this ensure in your server.cfg
  - `ensure jrs_spooner`
- At the end
  - Restart the server
If you have any problems, you can always open a ticket in the Spooni Discord.
## 2. Usage
## Cursor colours
| Colour | Meaning            |
|--------|--------------------|
| white  | No entity selected |
| green  | Entity highlighted |
| blue   | Entity attached    |
## Controls
| Control                   | Function                                                                         |
(line hidden)
| W/A/S/D                   | Move                                                                             |
| Spacebar/Shift            | Up/Down                                                                          |
| E                         | Spawn                                                                            |
| Left click                | Entity highlighted: Attach, Entity attached: Detach                              |

# FiveM/RedM weather and time sync
# Features
- Syncs time and weather for all players
- Configurable weather pattern
- Weather is queued so players can get a forecast of upcoming weather
- Different weather for different regions
- Adjustable timescale
- Players can temporarily disable sync and set local time/weather
# Examples
| Forecast and admin UI | Region-specific weather | Adjustable timescale |
|---|---|---|
| [![Forecast and admin UI](https://i.imgur.com/Scn0z0Em.jpg)](https://imgur.com/Scn0z0E) | [![Region-specific weather](https://i.imgur.com/Loif9SMm.jpg)](https
# Installation
1. Create a `weathersync` folder within your resources directory, for example, `resources/[local]/weathersync`.
2. Copy the files from this repository into the `weathersync` folder.
3. Add the following to your `server.cfg`:
'''
exec resources/[local]/weathersync/permissions.cfg
start weathersync
'''
# Commands
| Command        | Description                                               |
(line hidden)
| `/forecast`    | Displays a forecast of upcoming weather.                  |
| `/mytime`      | Set local time (if sync is off).                          |
| `/myweather`   | Set local weather (if sync is off).                       |
| `/syncdelay`   | Set how often the server syncs with clients.              |
| `/time`        | Set the server time.                                      |
| `/timescale`   | Set the ratio of in-game seconds to real-time seconds.    |
| `/weather`     | Set the server weather.                                   |
| `/weathersync` | Toggle time/weather sync on/off.                          |
| `/weatherui`   | Opens the admin UI for changing the time/weather/wind.    |
| `/wind`        | Set the wind direction and base speed.                    |
# Configuration
| Variable                         | Description                                                    | Example                                   |
(line hidden)
| `Config.time`                    | Default time when the resource starts.                         | `DHMSToTime(0, 6, 0, 0)` (Sun 06:00:00)   |
| `Config.timescale`               | Default timescale when the resource starts                     | `30` (30 in-game secs per real sec)       |
| `Config.realTimeOffset`          | Offset of the real server time in seconds.                     | `0`                                       |
| `Config.timeIsFrozen`            | Whether time is frozen when the resource starts.               | `false`                                   |
| `Config.weather`                 | Default weather when the resource starts.                      | `"sunny"`                                 |
| `Config.weatherInterval`         | How often the weather changes.                                 | `DHMSToTime(0, 1, 0, 0)` (1 in-game hour) |
| `Config.weatherIsFrozen`         | Whether weather is frozen when the resource starts.            | `false`                                   |
| `Config.permanentSnow`           | Whether to permanently add snow on the ground.                 | `false`                                   |
| `Config.dynamicSnow`             | Whether to dynamically add snow on the ground.                 | `true`                                    |