BaluDog Gaming

Hi, are you able to update the plugin so that the UI doesn't show while a player is sleeping please? Or add it as a config option?

What a beauty of a QoL plugin! No hassle, load it, equip the backpack and wonder how you played Rust for so long without this. Prompt and effective turnaround of fixes from the developer also. 5 stars!

Thanks for quickly fixing the initial compile issue, the plugin works! I have tested for a short while, and do have some suggestions for you. Console spam - the plugin logs every blocked SAM target. These fire repeatedly while in range which will become very noisy for owners, especially on large pop type servers and active SAMs. Recommend you move this behind a debug config option i.e. "Enable debug logging": false by default and only log when enabled, ideally with a cooldown. [Smart SAM Sites] [SAM] BaluDog on minicopter.entity blocked (vehicle permission). [Smart SAM Sites] [SAM] BaluDog on minicopter.entity blocked (vehicle permission). [Smart SAM Sites] [SAM] BaluDog on minicopter.entity blocked (vehicle permission). [Smart SAM Sites] [SAM] BaluDog on minicopter.entity blocked (vehicle permission). The in game chat message is partially cooled but it isn't configurable. Would suggest moving the cooldown into config for owners to choose a value. [SAM Sites] The SAM Site will not shoot you because you are authorized on the TC Suggest moving your player facing messages to a lang config, to separate gameplay config and localisation. Suggest adding various feedback options for the messages, chat is good, but also consider console, toasts etc. "Feedback": { "Chat enabled": true, "Toast enabled": false, "Console enabled": false, "Message cooldown seconds": 25.0 } The vehicle protection logic seems to protect the whole vehicle, even if the pilot or another passenger should not be protected. Maybe add a "Vehicle protection mode" and then "PilotOnly" (driver/pilot is TC- auth'd) and "AllMounted" (every mounted player must be TC - auth'd). Maybe rename the parachute permission, to make it clean that permission applies to player targets, not strictly parachuting? Have you tested the plugin with Raidable bases, custom monuments etc? Owners might get some unexpected results with the staticRespawn. Suggest you add some config options to tailor how these are handled. "Ignore static respawn SAM Sites": true, "Ignore monument/static SAM Sites": true, "Protect only player-deployed SAM Sites": true

Could you add permissions please? For example, a global config like you have and then permissions for each of these settings - workbencht.lvl1.all workbencht.lvl1.accelerated workbencht.lvl1.prototype etc