A roleplay hold: step in behind someone, put a blade to their throat, and take control of the scene.

He does not hear you. The saloon is loud, his back is to the door, and your knife is already out.

Three steps and your left arm is across his chest, the blade under his jaw. He stops walking because he cannot walk. His friends turn around and find themselves negotiating.

You hold him there for as long as the scene needs. Then you let him go — or you do not.

That is the whole product. One clean, believable hostage hold, built so the drama lives in what the players say to each other, not in a health bar.

• Knife-from-behind paired animation. The captor and the victim play a matched grapple sequence, so the hold reads correctly to everyone watching.
• The animation family follows the weapon in hand. A small blade plays the blade family; a sidearm plays the pistol family. You do not pick an animation from a menu — you pick a weapon.
• A free hand is required. Dual wielding is refused. You cannot hold a man at knifepoint with both fists full.
• A small NUI panel on the captor's screen: G to release, K to execute. Execute must be held for 1.2 seconds before it commits, so nobody ends a scene by fumbling a key.
• Execution. The paired throat-cut plays; the victim dies 900ms later, on the beat, not before the animation lands.
• Animation watchdog. The victim cannot emote, dance, or animation-cancel their way out of the hold.
• Only the captor can release. Config.StruggleAfter = 0 — there is no struggle-free timer to farm. The hostage ends when the captor ends it, when the execution comes, when the hold times out, or when the two of you drift apart.
• Framework bridge for RSG, VORP, RedEM:RP, and standalone.
• English and Georgian locales included, English by default.
• Every hold and every execution is logged with both players' identifiers, so your staff can read the scene back afterwards.

This is not a human shield.

There is no damage redirect. Bullets meant for the captor do not land on the hostage. Holding someone gives you no combat advantage of any kind — no armour, no cover, no mitigation, no aim bonus. If a rifle opens up on you mid-hold, you are exactly as vulnerable as you were before you grabbed him.

That is deliberate. A hostage system that wins gunfights becomes a gunfight mechanic within a week. This one stays a roleplay tool: leverage in a conversation, not leverage in a fight.

A static radial menu entry fires the client event:

lxr-hostage:client:radial

Wiring instructions are in docs/RADIALMENU.md. If you would rather not touch your radial, /hostage is the fallback command and works out of the box.

Two exports, for anyone building around it:

-- is this player currently held?
exports['lxr-hostage']:IsHostage(src)   --> boolean

-- who is holding them?
exports['lxr-hostage']:GetCaptor(src)   --> captor server id, or nil

Use them to block shop access, refuse a teleport, deny a job action, or gate anything else while a player is at knifepoint.

lxr-* resources are built to stand alone. There is no hard dependency between them, and nothing here needs to be edited into another resource. Integration happens through the documented exports and events above — that is the whole surface.

Siblings that pair naturally with a hostage scene: lxr-blindfold (restraints and abduction), lxr-lasso (restraint states), lxr-robbery, lxr-banking, lxr-playerstore. If one of them is not installed, that feature simply does not appear. Nothing breaks.

Escrowed release, with the parts you actually need left in plaintext:

The framework bridge is open, so if you run something custom you can point it at your own core without waiting on us. The NUI in html/ ships plaintext, as CFX escrow always does — no secrets live there.

Discord — https://discord.gg/CrKcWdfd3A Store — https://theluxempire.tebex.io Site — lxrcore.com · wolves.land

Built by iBoss21 · The Lux Empire.