Raid Time Protection

Give your community clear raid hours. Choose when raids are allowed each day, protect the start of a wipe and let players check the current rule with /raid_date.

Choose when raids are allowed

• One allowed raid window per day, including windows that cross midnight.
• A fixed UTC offset for the schedule.
• Post-wipe protection that takes priority over the weekly schedule.
• Optional prefab and Zone Manager exceptions.
• Chat notices when protection changes, plus the public /raid_date command.

For example, a window starting at 18:00 and lasting 300 minutes allows raids until 23:00. Outside the allowed windows, eligible targets stay protected while Global Protection is enabled.

The UTC offset does not change automatically for daylight saving.

Build your schedule on PimpMyRust

Choose raid hours, wipe protection and exceptions in the browser. Import your current file or export a new configuration for your server.

Open the Raid Time Protection configurator →

Install the policy

1. Back up the existing configuration and install RaidTimeProtection.cs.
2. Load it once, then install your exported oxide/config/RaidTimeProtection.json or Carbon's corresponding config file.
3. Reload and check /raid_date.
4. Test allowed and protected damage on a private server before changing live rules.

Readable older configurations can migrate to version 2. Keep the generated .v1.bak until you have checked the result.

Know what is protected

Protection covers player-attributed damage to eligible owned buildings with a tool cupboard. TC-authorized players may damage their own protected target; configured exceptions can also allow damage.

This is not protection for every damage source. Decay, electricity, NPC players, Bradley APC and CH47 damage are excluded. Indirect damage without an attributed player is not claimed as covered.

Runs on Oxide or Carbon. Zone Manager is optional; Notify is not required for chat notices.

Schedule, exceptions and protection guide →