HostageTaking

__Project details__

Project: HostageTaking

Dev language: C# (uMod/Oxide for Rust)

Plugin language: EN + DE (localization included)

Author: @RustFlash

Description

Every server has them: players who sit in base all day. They do not want to roam, take risks, or “run into an event, kill everything, loot, repeat”.

HostageTaking was built exactly for those players.

Instead of a pure gunfight event, this is a brain-driven rescue scenario:

• a hostage is held with a ticking C4 device
• players must search the area to uncover the 4-digit defusal code
• only then can they attempt the defusal via an in-game UI keypad

This reliably pulls passive/base players out and gives them a meaningful server event without forcing a full PvE slaughter-fest.

Core Gameplay Loop

• Admin starts the event (chat or console command).
• A countdown begins (broadcast announcements at milestones).
• The hostage spawns at a monument location and is equipped like a prisoner, with C4 on the belt + beeping effect.
• Around the monument, the plugin selects 4 random code spots (from a predefined list).
• Players must roam and get close to code spots to discover digits (each digit reveals part of the code).
• Once players believe they have enough info, they interact with the hostage and open the Defusal UI (keypad).
• Limited attempts:
• wrong tries reduce attempts
• careless interaction (closing UI mid-attempt) can also reduce attempts
• Outcome:
• Success: bomb defused, hostage rescued, reward crate spawns
• Failure: hostage dies / attempts run out → C4 explodes and the event ends

Features

• Dynamic hostage rescue event with “C4 defusal” mechanics
• 4-digit code generated per event
• Code digits are discoverable via proximity-based “code spot” locations
• In-game UI
• warning dialog (encourages searching first)
• keypad defusal UI
• attempt counter and correct-digit feedback
• Max duration auto-stop (prevents never-ending events)
• Optional cooldown between events
• Admin visibility option (show the secret code to admins with permission)
• Debug mode can spawn flares at code spots (for testing)
• EN + DE messages included

Dependency / Requirements

This plugin requires the MonumentFinder plugin to locate the configured monument.
If MonumentFinder is not loaded, HostageTaking will not run.

Commands

Chat Commands (admin permission required)

• /flashhostagetaking - Start the event
• /stophostagetaking - Stop the event
• /statushostagetaking - Show current event status + code (admin-only)

Console Commands (admin permission required)

• flashhostagetaking - Start the event
• stophostagetaking - Stop the event
• statushostagetaking - Status output

Permissions

• hostagetaking.admin - Required to start/stop/status the event and (optionally) view the generated code.

Configuration

All config values are validated and clamped to safe ranges on load.

Default config options:

• Event Start Time (seconds): 300
• Max Event Duration (minutes): 60
• Event Cooldown (minutes): 0 (no cooldown)
• Max Code Attempts: 3
• Show Code To Admins: true (shows “Event code: ####” to admins)
• Debug Mode (Show Flares At Code Spots): false

Notes (important)

• Code spot offsets are hardcoded (not configurable via config).

Rewards

On successful defusal, a reward crate is spawned:

• Hackable Locked Crate (Chinook crate prefab)

Practical Server Use (Why this exists)

This event is designed to:

• create roaming incentives without pure PvE “wipe NPC camp” gameplay
• give “base players” a strong reason to leave safety
• encourage communication and exploration
• create PvP tension organically (players moving between code spots and the hostage)

In short: less “aim and loot”, more “think, search, risk, and decide”.

load, run, enjoy 💝