NODERAntiraid and lockpick protection

NODERAntiraid alerts an authorized player when the system detects suspicious activity at their base, storage, or vehicle. This could be a lockpick attempt, vehicle damage, or an explosive base attack. Notification can come in-game, via email or via Discord depending on server settings and player preferences.

The goal is not to automatically punish the attacker or guarantee that every raid will stop. The module gives the defender quick information and the administrator a searchable log. The attacker's identity is intentionally not sent to the player.

NODERAntiraid is not NODERaid

They can work on the server at the same time, but their settings and logs should not be confused.

Where to find it

• NODERAntiraid → Overview - protection status and latest summaries.
• NODERAntiraid → Logs - captured incidents and delivery.
• NODERAntiraid → Discord – content and status of Discord output.
• NODERAntiraid → Settings - event types, channels and messages.
• Lockpick Watchdog → Active Watchdogs - players for whom events are currently watchable.

Who can receive a notification

The global server setting is only an upper limit. A specific player must be authorized according to the set service or role, have a linked Steam identity and meet the requirements of the selected channel:

• In game: the player must be online and the server must have player-targeted messages available.
• Discord: player needs a linked Discord account and messages enabled.
• Email: player needs a valid email address and email notifications enabled.

The player can turn off the channel. An administrator does not have the option to bypass it just because the channel is globally enabled. At the squad base, authorized squad members can also receive a notification if this option is enabled.

How to set the module

1. Choose a server and turn on NODERAntiraid.
2. Choose incident types: base lockpick, chest or vehicle, vehicle damage and base explosive attack.
3. Decide whether authorized squad members should also be notified.
4. Enable the required channels. For Discord and email, also check the common delivery configuration.
5. Edit player message. Use only the offered variables and do not put the attacker's name in it, which the player output does not intentionally reveal.
6. Check active watchdog records. If the player does not have a properly linked identity or authorization, the global switch alone is not sufficient.
7. Perform a safe test and compare the incident with the results of individual channels in Logs.

What delivery statuses mean

• Sent: the specific channel received the message.
• Pending: the message is still waiting to be processed.
• Skipped: the player did not have the channel available, turned it off, was not online, or the rule against repeated spam was applied.
• Failed: delivery failed and a specific error needs to be checked.

"Skipped" therefore does not necessarily mean a malfunction. The log should be read together with the reason and preferences of the recipient.

Example from the Main server

Status of the database as of 1 September 2026.

The numbers represent recorded history and should not be used as the number of confirmed cheaters or successful raids.

Most common problems

• The incident is in the log, but the player has not received anything: open the delivery lines and check the authorization, Steam binding, preferences, online status and channel availability.
• Too many messages coming in: check cooldown/rate limit, range of squad recipients and repeating events from the same object.
• Player requests name of attacker: explain that player protection does not intentionally send identity. Admin audit and moderation are a separate process.
• Watchdog is not active: most often the service authorization, linked identity or supported event source on the selected server is missing.