For me this is no longer blocking damage even though it seems to be storing offline info correctly (and /ao seems to be returning the right statuses)

No blocking, no message, no errors in console

Please check your oxide/logs for errors and verify the plugin is loaded.

23:23 [Info] Unloaded plugin Anti Offline Raid v0.4.2 by Calytic
23:23 [Info] Loaded plugin Anti Offline Raid v0.4.2 by Calytic

Thanks for the tip ... but I just now reloaded to be sure, and retested. Nothing in that log after that point :| 

Since that didn't give errors, I tried unloading it, deleting the .cs file, and then dropping it in again to see if anything showed up in the compiler file:

[SERVER v1.0.20] Started as service
[SERVER v1.0.20] Running as service
[SERVER v1.0.20] Got Message: Ready
[SERVER v1.0.20] Got Message: Compile
[SERVER v1.0.20] Console: AntiOfflineRaid.cs(45,15): warning CS0414: The private field `Oxide.Plugins.AntiOfflineRaid.lastOnlineTimer' is assigned but its value is never used

You'd need to check your other oxide/logs file, not the compiler log. I'd also verify that you indeed have Oxide installed properly, as Rust will ignore chat commands natively as well. Checking the oxide.version console command would verify Oxide.

oxide.version
Oxide.Rust Version: 2.0.5532

I did check the other logs first, didn't see any errors (that's where that unloaded/loaded messages came from). But yeah only when I didn't see errors there did I bother to check the compiler one. 

That being said, again the /ao command does return things I'd expect, indicating that it's running. When people are online, it shows them online and green, when they go offline, it shows that too. It's only the blocking/alerting aspect that doesn't seem to be working.

Could you be more specific about what other files I might check?

Thanks

Wulf

You'd need to check your other oxide/logs file, not the compiler log. I'd also verify that you indeed have Oxide installed properly, as Rust will ignore chat commands natively as well. Checking the oxide.version console command would verify Oxide.

@Wulf do you know how I'd further address this, or if any other anti raid plugins are 100% for sure working right now? I am losing people on my server to raids because this plugin isn't working :( 

The oxide/logs/oxide logs would show details and any errors when using the commands.

Didn't want to lose the data, but figured since it wasn't working I'd give a full delete reinstall a try. Did the following:

• o.unload AntiOfflineRaid
• deleted AntiOfflineRaid.cs from plugins folder
• deleted AntiOfflineRaid.json from config folder
• deleted antiofflineraid.json from data folder
• added AntiOfflineRaid.cs to plugins folder

After doing this, things seemed to be working again. Anyone that logged off after I did this had raid protection after the delay timer expired.

However, I logged in later that day and started testing again. Found the following:

• ✅ Some people's bases were working as intended. I was getting the popup stating raid protection existed
• ❌ Other people's bases were NOT protected, including one of the people I tested with earlier in the day whose base was protected previously.
• ❗I started having people log out and waiting the the 10 minutes until they showed as "Offline" ... some of those users' bases were protected, some were not.