IIIaKa

Hello, thanks for reaching out. @ZEODE has already informed me about your issue. At the moment, I'm busy with other plugins, but I'll look into this problem as soon as I'm free. I'll try to get it done before the global wipe.

Changed Status from Pending to Work in Progress

At the moment, this isn't possible, as authorization on the tool cupboard is only allowed once players become friends. It's also important to note that checking for building privilege is significantly more performance-intensive compared to checking for friendship.

Hello. Damage to player-owned structures/entities can only be dealt by their owner, their friends(same team and only if friendly fire is enabled) and in PvP zones.

Changed Status from Pending to Work in Progress

Changed Status from Pending to Work in Progress

If you have anything to add, feel free to write in this thread.

Changed Status from Work in Progress to Not a Bug

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Not a Bug

Changed Status from Pending to Work in Progress

If I understood you correctly, you want to completely disable the claim system in monuments, but still keep the PvP monuments as PvP? To do this, you need to work with these two properties: 'List of tracked categories of monuments' and 'List of IGNORED monument names. Example: powerplant_1', in the file '*SERVER*\oxide\data\RealPVE\MonumentsConfig.json'. The 'List of tracked categories of monuments' property contains a list of tracked categories of monuments. Here, you can remove the categories of monuments that should not be tracked(no PvP and no claim system). The 'List of IGNORED monument names. Example: powerplant_1' property contains a list of monument IDs to ignore. Here, you can specify all the monuments you want to exclude. Most likely, it’s better to work only with this property to avoid confusion and leave the first one with its default settings. For example: "List of tracked categories of monuments": [ "RadTown" ], "List of IGNORED monument names. Example: powerplant_1": [ "ferry_terminal_1", "powerplant_1", "desert_military_base_c" ], With these settings, the plugin will track only monuments of the RadTown category, except those listed in the second list. You can find a list of monuments by category on the MonumentsWatcher plugin page, in the Developer API section.

Thank you for the suggestions. Could you please tell me the reason why you're suggesting to use Hurt method? IsValid is an extension method that checks for != null and block.net != null. The plugin already checks for != null and I believe that checking net is not necessary in this context.

Hello. I didn't quite understand this message. I set decay.scale to 3, made twigs blocks, let them decay to 100% and didn’t get any error. Could you explain in more detail when it occurs?

Changed Status from Pending to Work in Progress

If you have anything to add, feel free to write in this thread.

Changed Status from Pending to Fixed Changed Fixed In to Next Version

Changed Status from Pending to Fixed

If you have anything to add, feel free to write in this thread.

Changed Status from Work in Progress to Fixed Changed Fixed In to Next Version

@dustyhansen@Zand3rs@dbfreak In the meantime(as a temporary solution), you can find(line 840) : private void DeleteAllPluginBars(string pluginName) and add this line if (pluginName.Equals(Name, StringComparison.OrdinalIgnoreCase)) return; right before AdvancedBar bar;

@dustyhansen@Zand3rs@dbfreak Thank you for reaching out. I checked and indeed this issue does exist, but only on Carbon. This is because Carbon triggers the OnPluginUnloaded hook when AdvancedStatus itself is being unloaded, essentially, it's telling AdvancedStatus that the AdvancedStatus plugin has been unloaded This issue is solvable, but I believe it should be fixed on Carbon's side( @Raul-Sorin Sorban ), since I don’t see any reason to call OnPluginUnloaded for the plugin's own unloading.

Changed Status from Pending to Work in Progress