Failed Code Alert

Failed Code Alert 1.2.1

Sign in to download
Warns players when someone tries to access their code lock with the wrong code
Documentation License Changelog (3) Version History Discussion
This plugin alerts players and their teammates when someone enters the wrong code on their code locks, keeping them informed about potential break-in attempts.







Recommended Plugins

Permissions

  • failedcodealert.use - Without this permission, players cannot enable or disable notifications for their own code locks.
  • failedcodealert.ignore - Players with this permission can enter any incorrect code without notifying the owner or team.

Commands

  • /codealert - Toggles code lock intrusion notifications on or off for the player. When enabled, the player will receive alerts when someone fails to enter the correct code on their locks.

Configuration

JSON: 
{
  "Version": "1.1.0",
  "Discord Webhook Url (Leave blank to disable)": ""
}
  • Discord Webhook Url - A url for sending failed code lock attempt alerts to Discord. If left blank, Discord alerts are disabled.

Stored Data

JSON: 
{
  "Intrusion Alerts": {
    "76561199104881804": true,
    "76561199963473143": false,
    "76561198813750329": true
  }
}

Localization

JSON: 
{
  "FailedAttempt": "Someone is trying to access your code lock at {1} but they failed! Intruder: {0}",
  "AlertsEnabled": "Code lock intrusion alerts enabled!",
  "AlertsDisabled": "Code lock intrusion alerts disabled!",
  "NoPermission": "You do not have permission to use this command.",
  "DiscordAlertMessage": "Intrusion alert: {0} ({1}) attempted to access code lock owned by {2} ({3}) at {4}"
}
Author
VisEntities
Downloads
25
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.2.1

    Fixed the missing registration for the ignore permission.

  2. 1.2.0

    Players now need the failedcodealert.use permission to toggle intrusion alerts. Failed code lock...

  3. 1.1.0

    Added /codealert command to toggle code lock intrusion notifications on or off.
Read more…
Back
Top
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Make sure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart

Cart

Total -