Khan

Changed Status from Pending to Fixed Changed Fixed In to 2.8.8

Action Hooks * Use these to forcefully interrupt or stop plugin behavior when a player becomes Combat or Raid blocked (e.g., using bgrade, skinbox, etc.): private void OnCombatBlock(BasePlayer player) private void OnRaidBlock(BasePlayer player) Check Hooks * Use these to check a player's current block status before allowing an action (e.g., using a command, teleporting, etc.): private bool IsCombatBlocked(BasePlayer player) | IsCombatBlocked(string player) | IsCombatBlocked(ulong player) private bool IsRaidBlocked(BasePlayer player) | IsRaidBlocked(string player) | IsRaidBlocked(ulong player) private bool IsEscapeBlocked(BasePlayer player) | IsEscapeBlocked(string player) | IsEscapeBlocked(ulong player)

Welcome to the FAQ and Support Guide for the Death Modifier plugin. This document is here to help you troubleshoot common issues, understand proper setup practices, and get support or suggest new features. Common Issues & Troubleshooting Permissions Bug - If a player is granted more than one permission, the plugin will not work correctly for them. Fix: - Only grant one permission per player. This ensures the plugin functions as intended. - Granting multiple permissions will cause conflicts and unexpected behavior. Example: oxide.grant user player1 deathmodifier.vip # Do NOT also grant: oxide.grant user player1 deathmodifier.vip2 We are aware of this bug and are working on a solution for a future release. Getting Support If you are experiencing issues with the plugin or have a question not covered in this guide: - Navigate to the Support section of the plugin page. - Open a support ticket. - Please include the following in your ticket: - A clear description of the issue - Any errors shown in the console - Plugin version - Steps to reproduce (if possible) This will help us assist you faster and more effectively. Feature Requests & Discussions If you have an idea for a new feature, improvement, or change you'd like to see: - Use the Discussion section of the plugin page. - Be descriptive in your suggestion, including the use-case or motivation. We welcome your ideas and will review them for possible inclusion in future updates! Best Practices Summary - Only assign one permission per player. - Use the Support tab for help with issues. - Use the Discussion tab for feature requests and general feedback. Thank you for using Death Modifier! Your feedback helps make this plugin even better. — Khan

Changed Status from Not a Bug to Work in Progress Changed Fixed In to Next Version

I'll be updating the plugin to simply grab the directory straight from the DLL source its loaded from Interface.Oxide.ConfigDirectory This will prevent any future problems ( same with carbon ). Since that will pull the directory for that specific instance running. ( Should prevent future issues ) For now you can just change "oxide" to Interface.Oxide.ConfigDirectory ( without the string quotes " " )

Christ all you had todo was state your running a multi-server instance under the same root directory or show this > "root/server/<identity>/oxide/config". As I had asked for after your first post. Easy enough fix. You made it sound like you had moved the oxide folder out of the root directory. As long as it's still in the main directory and simply split between instances that should be fix-able.

I don't understand why it wouldn't be. You've provided no context or reason for it to not be where it's provided by default. All you have done is report a problem that to me simply isn't an issue. Moving forward all future plugin updates of mine will be using the same config get/save methods. You haven't even explained why yours isn't in the default location or bothered to show where you've moved it to either. I have well over 500 users and frankly you are the only one to have an issue with this.

Changed Status from Pending to Not a Bug

I'm sorry but your going to have to show me how you have your file directories setup.

Why wouldn't the oxide folder be in the rust folder directory? That would break more then just mine if you moved it outside of the rust folder.

Changed Status from Pending to Not a Bug

What are you using to track / show that? Oxide, carbon, DLL addon? etc Also would help if you showed the top of all that so i knew what order everything is being displayed in/as. Honestly these images are very vague, it doesn't state if that is current ram usage in the displayed images or if those are simply TOTAL ram usage since running the plugin. 2 Very different things to track. Regardless, that ram usage is typically when loading / unloading the plugin and not actual real-time-usage which means those stats are not-valid.

Changed Status from Not a Bug to Fixed

Carbon support has been restored.

Spoke to carbon / raul. Fix is coming next production update. https://discord.com/channels/1013291619765723196/1361083692277301338 Fix is delayed, follow thread for updates.

If you are running carbon, it's been confirmed this problem is only related to those running carbon. Its not a problem on oxide.

Ah, well tell him to add the umod kit's API ! So that plugins like mine already support it! Here is what umod's kit's API does.

I forgot to mention, it is possible that you have more then 1 plugin affecting it, so do be careful of that /

Changed Status from Work in Progress to Fixed

@dfgas Hey so looks like the developer got around to adding an API. Does death modifier work now with Real PVE?

Changed Status from Pending to Not a Bug

No-Drop only prevents your body from drooping active items/backpacks from the corpse when you die, it is not designed to restore / give back your items. But Death Modifier is designed to keep your previous inventory.

Changed Status from Pending to Not a Bug

Please let me know if you find the plugin causing it! I may be able to fix support for it / Best way to find the plugin is to load 1 at a time on your test machine until it breaks it.