-
Posts
2,500 -
Joined
-
Last visited
-
Days Won
10
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by IIIaKa
-
Changed Status from Pending to Work in Progress
-
Hello, thanks for the suggestion, I’ll try to include it in the next update.- 19 comments
-
- 1
-
-
- #rust
- #banditcamp
- (and 23 more)
-
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.
-
Hello. The 'Command' property controls whether the status bar is clickable, if a 'Command' is set, the bar becomes clickable, but the UI layer of all bars must be 'Overall'(this causes overlapping when the map is opened). There are also other properties, 'PlayerCommands' and 'ConsoleCommands', which are triggered when the bar is removed. You can see more details in the 'UpdateTimedBars' method. -
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
-
Hello, please check this key in all language files located at *SERVER*\oxide\lang\**\PermissionsStatus.json
-
Hello. PvE mode is always enabled and PvP mode only applies in designated PvP zones. Therefore, there's no need to constantly display the PvE status bar. I didn't quite understand what you're asking. Do you want the monuments to be vanilla and shared by everyone? Or do you want the monument claiming feature to work, but make it free? Please check if this will work with deleted MonumentsWatcher plugin. Also, what plugins are installed on your server? For reference, most of the settings can be found in *SERVER*\oxide\data\RealPVE\
-
@BroShelbi Hello, I checked with your settings and everything works fine on my end(Economics and ServerRewards). Please send your config file from *SERVER*\oxide\config\ActivityRewards.json and let me know which economy plugin you have installed?
-
Hello, this is most likely referring to the RealPVE functionality. If you want to disable monument tracking by the RealPVE plugin, you can do it in the monument settings file *SERVER*\oxide\data\RealPVE\MonumentsConfig.json There are two ways to do this: Disable tracking by type - Simply remove the monitored type(in this case, Custom) from the "List of tracked categories of monuments" property. This will stop RealPVE from tracking all monuments of that type. Disable tracking by monumentID - Add the monumentID(which you can find in the same file) to the "List of IGNORED monument names. Example: powerplant_1" property. This will prevent RealPVE from tracking that specific monument.