-
Posts
76 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by CrypticRedHat
-
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
It doesn’t allow you to set an overall limit per week or server wide. I could implement this if there was enough flak for it, although to be honest - I’d be surprised, I can’t see why this would be a good idea although I’m open to discussion, I think any players would be in uproar though. I can see a single team using the entire limit for the whole server every wipe or week
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
That's correct, or if the defenders/attackers are different, or if it is outside the radius
-
Changed Status from Pending to Not a Bug
-
Let me know if this resolved the issue or if you need further help
-
Yes there is a criteria, For example, if the attackers and defenders are the same, and within 140 meters of the original raid, and within the time constraint, its classed as the same raid, this is to avoid counting multiple raids for external TCs and compound bases. You can decrease the distance or time, although I would advise against this as it could create false positives. The default config is pretty well optimised. The time constraint is not from when the raid begun, its from when the last item was destroyed, for example a raid could last 6 hours if someone boomed 1 wall every 60 minutes. However if there is a gap in booming of more than x minutes (default 90) the raid we be considered over.
-
Is the second offline base you are raiding, owned by the same people as the first, and within 140 meters, and being raided within 90 minutes of the first base by any chance?
-
Hello! when you raid the second offline base, is the counter going up, or does it stay the same EG first base it goes 0->1. Does it go from 1->2?
-
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
If someone starts a raid as an online, and the defenders log off once the raid has begun, it is not considered an offline, therefore is not counted. If they log off before anything's been destroyed, it is counted as an offline. There is no grace period. This is to avoid people tracking player with BM and waiting for them to log off and raiding immediately after to circumvent the plugins logic.
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
Its important to note, also taking your other comment into account, this is not an offline raid protection tool This tool limits the quantity a player or team can offline raid, it does not strictly protect a players base. However it does stop someone from offline raiding more than x bases per day. The plugin you may be comparing with, I'm my opinion offers a different use case for functionality. In theory your base may be protected against someone with more than for example say, 1 offline raid, but may be raided offline by another player who has not yet reached that limit. This tool is great to stop players mass offlining the whole server, while not taking the originality out of rust by blanket blocking offline raids, other plugins may and will perform differently
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
- 19 comments
-
- #raid
- #protection
- (and 12 more)
-
Version 1.1.0
28 downloads
BaseGuardian ensures that sudden server restarts, forced crashes, or network drops won’t leave players’ bases vulnerable, by closes all doors. It also automatically boosts Tool Cupboard upkeep to a safe threshold, preventing unexpected decay. Designed for simplicity, fairness, and seamless integration with Rust’s native upkeep rules, BaseGuardian takes server management to the next level—now with added options for automated protection. Key Benefits Automated Crash & Network Handling BaseGuardian can automatically close all doors and top up Tool Cupboards whenever it detects a crash or network outage. No manual intervention needed—players stay protected even if you’re offline. Instant Door Security With a single command, any open door, gate, shutter, or ladder hatch across the map is snapped shut—especially helpful right after a server crash or restart. Accurate Upkeep Top-Ups BaseGuardian brings each qualifying Tool Cupboard’s coverage up to a pre-set number of hours (default: 12 hours). Because it taps into Rust’s own upkeep balance, each base pays only for the exact time and resources it needs. Fair for All Base Sizes Larger or higher-tier bases require more resources to stay protected; simpler bases need less. No one’s overpaying, and no hidden shortcuts are involved. Permission-Based Commands Two separate permissions let you decide who can close doors and who can top up TCs. This prevents misuse and keeps server management firmly in your control. No Leftover Resources Once upkeep is topped up, materials are seamlessly consumed to provide the extended coverage. Players don’t find unexpected piles of items in their cupboard—just the additional time they need. Minimal Disruption Although the plugin checks multiple entities, it’s designed as an on-demand tool for admins. Run it when needed (e.g., after a restart) with negligible impact on your server’s performance. Commands & What They Do Close All Doors Command: bg.doors Effect: Closes every door, gate, shutter, and ladder hatch on the server if they’re open. Use Case: Ideal after forced restarts or when an admin wants to ensure no player base is left open during downtime. Top Up Tool Cupboards Command: bg.tc Effect: Scans all non-abandoned TCs, and brings each one’s upkeep coverage to a default threshold (12 hours). The plugin accounts for each base’s size/tier, creating and using only the necessary resources. Use Case: Perfect for preventing mass decay after downtime or ensuring players have a fair buffer when forced offline. Frequently Asked Questions “Why don’t I see extra resources in the Cupboard afterwards?” BaseGuardian immediately converts spawned materials into extra coverage. You won’t see leftover items because they’re fully used to boost the TC’s timer. “How is the upkeep cost determined?” The plugin uses Rust’s own upkeep system to decide what’s required for the final hours. Larger or more complex buildings need proportionally more resources, while simpler bases pay less. “Can I change 12 hours to a different amount?” Yes. The plugin defaults to 12 hours, but you can adjust it to match your server’s rules—such as 8, 10, or 24 hours—ensuring any forced downtime doesn’t unfairly penalize players. “What if a TC has fully decayed already?” By default, BaseGuardian skips TCs with zero coverage. If you prefer to ‘rescue’ those TCs, you can modify the plugin’s settings to do so. “Does this run automatically?” Now it can! Besides manual commands, the new version detects crashes or network issues and handles door closures/TC top-ups automatically—keeping your server protected even when you’re not there. Permissions BaseGuardian’s two core features—closing doors and topping up TCs—are independently permissioned. This means you can give some staff the ability to secure doors, while only a few select admins can top up everyone’s upkeep, or vice versa. Check your server’s mod framework documentation for how to manage these permissions. Door Closure Permission: Allows the use of the door-closing command. TC Top-Up Permission: Allows the use of the upkeep top-up command. Why BaseGuardian? Defends Offline Players: Protects your community from uncontrollable downtime and forced restarts. No Game-Breaking Workarounds: Aligns with Rust’s native decay and upkeep standards without creating artificial advantages. Unobtrusive: Kicks in only when you command it, so normal gameplay is never disrupted. Transparent & Fair: Ensures players’ bases remain intact if they can’t reconnect promptly, boosting server reputation and trust. With BaseGuardian, your Rust server stays secure and fair—no matter how abruptly it reboots or how large the bases get. It’s a small but invaluable addition for any admin who wants peace of mind and a satisfied player community. A special thanks to EU Game Host for generously providing free server hosting to support the development and testing of BaseGuardian. Your assistance has been instrumental in helping this project flourish and ensuring the Rust community enjoys a smooth, reliable experience. UK Game Server Hosting - EUGAMEHOSTFree -
Changed Status from Closed to Fixed Changed Fixed In from 1.5.20 to 1.5.22
-
Thanks I have patched this in v.1.5.22
-
In my tests it has been SimpleStatus natively.
-
Sam reach out if needed, it was all fine until last wipe, maybe a difference in priority setting. Looks like simplestatus isn't reacting to the priority or its being ignored.
-
It counts cardtableseat As a vehicle seat so people using the trains for poker are punished
-
I have examples of it logging associations of joint looting, when one of the warned players are offline and not even looting
-
Can you post a copy of your config please, be sure to remove any webhooks
-
Hello, that’s very odd as another person who uses trainable bases has reported this resolved the issues for them. can you please include the version number in your message you sent to ensure you are running the latest version?
-
Customer reloaded in order and cleared data files, is now working if you like the plugin please remember to leave a review, it really helps
-
Changed Status from Pending to Not a Bug
-
Okay so based on that I am sure the issue is with simple status, I will reply to your PM and try to help with this anyway, on discord