Khan

Changed Status from Pending to Not a Bug

The config is working as designed. A value of 10 means the raid block triggers when 10% of an entity’s total HP is damaged. A value of 1 effectively means that almost any meaningful damage will trigger a raid block, since 1% of most building entities is an extremely small amount of HP. A value of 0 disables the percentage check entirely and always triggers on any qualifying damage. There is no post-damage health check. The comparison is made at the time the damage hook fires. If the damage does not meet the configured percentage threshold at that moment, no raid block occurs — even if the entity is later destroyed. If your goal is to avoid false positives from small or incidental damage, you should **increase the value to 10% or higher**. Values this low (e.g., 1%) defeat that purpose and will not behave the way you expect. This is expected behavior, not a bug.

In order for everything to work properly any time a plugin has a config option to allow or block backpack drops & active-item drops you need to make sure they are all set the same ( False ) Otherwise death-modifier cannot do its job to restore all the items lost on death. Calling hook OnBackpackDrop resulted in a conflict between the following plugins: DeathModifier - False (Boolean), TruePVE (True (Boolean)) Calling hook OnBackpackDrop resulted in a conflict between the following plugins: DeathModifier - False (Boolean), RaidableBases (True (Boolean)) This report is saying stack-modifier is trying to block dropping the players backpack using False and the other plugins are saying no-allow them to drop/lose there backpack on death / wounded. It'll be the same case with Active item hook conflicts > CanDropActiveItem

Can you post the console errors? Also, death modifier doesn't allow looting of the corpse until after the dead player respawns. Otherwise they have no way to get there items back if they choose a death-modifier respawn option.

Changed Status from Pending to Not a Bug

Yes, a dedicated Death Modifier option will appear to use it with, that is separate from the standard green one on the right that's vanilla spawn.

Death Modifier does not cause that behavior. That issue is coming from another plugin on your server. I’ve tested this thoroughly — applying skins using the repair bench, dying, and respawning — and all skins remain exactly as they were before death. Death Modifier does not modify, remove, or reset player skins at any point. You’ll want to check for another plugin that handles inventory, stripping, reskinning, or loadouts.

Changed Status from Pending to Closed Changed Fixed In to 1.4.7

Added new configuration option setting for cooldowns Example: this would be 2min cool-down between being able to use it. "Sets Respawn with death modifier cooldown in seconds, 0 = disabled": 120 ( for testing i had it set to 30 and it works )

Changed Status from Pending to Not a Bug

That's something that you have done. The website does not do that.

Changed Status from Pending to Not a Bug

I’m not really sure why a support ticket was opened for this, as the single line you posted provides no useful information. You didn’t include any context, plugin list, what tool generated that output, or even what you believe the issue actually is. With zero details, there’s nothing for me to diagnose or assist with. For context: hook time by itself is not an indicator of a problem with this plugin. High hook times are often caused by other plugins abusing or spamming Oxide hooks—especially plugins that repeatedly call things like CanStack, including item sorters, auto-organizers, and similar systems. If you’re genuinely experiencing an issue, please provide context, your full plugin list, and a clear explanation of what you think is wrong. Without that, there’s nothing meaningful for me to investigate.

Some plugins will not work with no-escape for example vanish if you are in vanish mode you will be ignored. Additionally some admin related plugins can make no-escape simply not work for you. ( Such as being in vanish ) Please let me know if you find out the cause of the plugin compatibility issue.

I can assure you the plugin works flawlessly. Have you tried unloading all other plugins and testing with only NoEscape loaded? This is the quickest way to confirm whether another plugin is interfering. Also, please double-check that the plugin is actually uploaded, compiled, and loaded correctly. Does anything appear in the server console when it loads or when raid/combat should activate? If you can, attach your server logs or share any console errors—otherwise we’re blind troubleshooting. Once you provide that, I can point you in the right direction quickly. Additionally if you'd like I can hop into a discord call @khan8615

Are you sure it's not due to another plugin causing compatibility issues? have you simply tried testing on a test server with just mine loaded to see if it works?

Changed Status from Pending to Closed

I see. This plugin has actually been disabled for sale for quite a while. I haven’t been updating it because Facepunch made game changes that effectively discontinued support for the way this product originally functioned. That said, I’ll review the latest game updates and see if there’s anything I can do to bring it back sometime this month or next.

Changed Status from Pending to Closed

Just update the link before map wipes in the config file.

That functionality isn't supported. RustMaps.com does not provide any way todo that through there API system. You will have to manually set it. https://api.rustmaps.com/docs/index.html?url=/swagger/v4-public/swagger.json

As stated in the update notes just add or remove your own additions. You are not creating the json file properly is what it looks like. Should look like this. "Map Link": { "Enabled": true, "Description": "https://rustmaps.com/map/afb0d08923d64dbfab6e5a7d0d1cf11d", "Inline": false },

@dustyhansen If you think bullying developers into adding features outside the advertised scope of their products through 1-star or negative reviews is acceptable, that says more about you than about any developer’s “customer service.” My stance has always been clear — and so has Codefling’s: I’m not responsible for compatibility with other developers’ plugins. That’s outside the intended scope and functionality of the product. You’re always welcome to request custom compatibility work as paid development, but that would fall under a custom commission, not normal support. It’s also worth noting that threatening or manipulating reviews in exchange for changes is considered review manipulation and isn’t acceptable under marketplace rules. Unfortunately, if Codefling chooses to allow those kinds of reviews to stand, it effectively sets a precedent that encourages this behavior — punishing developers for maintaining quality standards. I’m always happy to help within reason, but only within the supported scope of the plugin. Thanks for understanding.

I want to clarify that the issues you’ve listed involve third-party plugins (Vehicle Buy, Abandoned Bases, etc) that my plugin does not officially support. I’m not responsible for compatibility with other developers’ plugins — that’s outside the intended scope and functionality of this product. You’re of course welcome to request custom compatibility work as paid development, but that would fall under a custom commission, not normal support. Also, please note that threatening negative reviews or ratings in exchange for changes is considered review manipulation and isn’t acceptable under marketplace rules. I’m happy to help within reason, but only within the supported scope of this plugin. Thanks for your understanding.

Changed Status from Pending to Not a Bug