-
Posts
1,842 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by IIIaKa
-
If the issue persists, feel free to report it in this thread.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
In the next update, the RealPVE plugin will subscribe to universal hooks that will allow any other plugins to add/remove players/entities from PvP. I also informed the author of the ArenaTournament plugin about this and everything should work once the updates for both RealPVE and the ArenaTournament plugins are released.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Pending to Not a Bug
-
Hello, unfortunately, what you’re asking for isn’t possible. However, you can: 1) Allow players to claim a monument but make it free by setting the Price parameter to 0.0 in the monument configuration file (*SERVER*\oxide\data\RealPVE\MonumentsConfig.json) ; 2) Remove the MonumentsWatcher plugin entirely, which will disable tracking for all monuments and revert them to vanilla behavior, though this may cause issues with other plugins that depend on MonumentsWatcher; 3) In the monument settings(*SERVER*\oxide\data\RealPVE\MonumentsConfig.json), leave the "List of tracked types of monuments" parameter empty(this will disable tracking for all monument types) ; "List of tracked types of monuments": [] 4) In the monument settings, use the "List of IGNORED monument names. Example: powerplant_1" parameter. For example, add monument IDs like "powerplant_1" to exclude specific monuments from tracking by their IDs. "List of IGNORED monument names. Example: powerplant_1": [ "powerplant_1", "CargoShip", "satellite_dish" ] -
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
Unfortunately, there's currently no way to disable aggression from the new wolves and the developers haven't finished working on them yet. Damage to the new wolves will be enabled from any player until there's an option to control the aggression of the new NPCs.
-
@keera Hello, it seems you tried to kill a wolf in someone else's monument. Regular animals shouldn't attack players in foreign monuments, so they can only take damage from those who have access to the monument. However, for some reason, this doesn't work with the new wolves, they attack all players, but can only be killed by those with access.
-
Changed Status from Pending to Work in Progress
-
By @keera
-
There are several methods to disable monument claiming: 1. Remove the MonumentsWatcher plugin. 2. In the monument settings(*SERVER*\oxide\data\RealPVE\MonumentsConfig.json), leave the "List of tracked types of monuments" parameter empty(this will disable tracking for all monument types). "List of tracked types of monuments": [] 3. In the monument settings, use the "List of IGNORED monument names. Example: powerplant_1" parameter. For example, add monument IDs like "powerplant_1" to exclude specific monuments from tracking by their IDs. "List of IGNORED monument names. Example: powerplant_1": [ "powerplant_1", "CargoShip", "satellite_dish" ]
-
Hello. This parameter controls item pickup from the ground. For example, when a player breaks a barrel, items drop to the ground and if you enable this parameter, no one except the owner or their friends will be able to pick up items from the ground inside monuments.
-
Understood, the ActivityRewards plugin works with the BankSystem, ServerRewards and Economics plugins. Any one of these plugins is required for it to function, having all of them is not necessary. -
Hello, I didn’t quite understand the question.
-
What if an FAQ section is added to the plugin page? It would only be displayed if the author adds at least some content. Sure, the Description section can be used, but many plugins already have a lot of information there, and the FAQ might get lost. Implementing a dedicated FAQ section would be convenient for quick answers.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
@Wodan Hello, thank you for reaching out. The issue will be fixed in the next update.
-
Changed Status from Pending to Work in Progress
-
I suggest adding a notification for plugin authors to inform them when *SOMEPLUGIN* includes their plugin in the compatibility list. This way, plugin authors can discover plugins that work with theirs and reciprocally add them to their own compatibility lists.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Pending to Not a Bug
