-
Posts
2,449 -
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
-
In the next update, a feature will be added that allows specifying the word "wipe" when granting temporary permissions. These permissions will remain with players until the server wipe occurs. Unlike the current system, which removes all permissions during a wipe, this approach will only remove the specified permissions. The detection of a wipe occurs only through the wipe ID specified in the configuration file.
-
Error when empty parameter to.user group or others command
IIIaKa replied to dFxPhoeniX's Support Report in Support
If the issue persists, feel free to report it in this thread. -
Error when empty parameter to.user group or others command
IIIaKa replied to dFxPhoeniX's Support Report in Support
@dFxPhoeniX Hello! I apologize for the late response, I have been very busy and thank you for reporting the bug, it will be fixed in the next version. -
Error when empty parameter to.user group or others command
IIIaKa replied to dFxPhoeniX's Support Report in Support
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version -
Error when empty parameter to.user group or others command
IIIaKa replied to dFxPhoeniX's Support Report in Support
Changed Status from Pending to Work in Progress -
Changed Status from Pending to Work in Progress
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Not a Bug
-
Team members unable to loot monuments that someone on the team claimed
IIIaKa replied to NotAmbient's Support Report in Support
If the issue persists, feel free to report it in this thread. -
Team members unable to loot monuments that someone on the team claimed
IIIaKa replied to NotAmbient's Support Report in Support
Changed Status from Work in Progress to Not a Bug -
Team members unable to loot monuments that someone on the team claimed
IIIaKa replied to NotAmbient's Support Report in Support
@NotAmbient Hello, I tried various scenarios, and everything works perfectly. The only case where a friend couldn't loot was when player A was the owner and player B entered the monument, joined the queue, and then they became friends. Only in this scenario was player B unable to loot. A simple re-entry into the monument resolves the issue, but this will be fixed in the next update. Do friends always fail to loot the monument, or is this just a single case? -
@Markiii Hello, most likely you entered the command incorrectly. Which command are you entering? Currently, commands need to be entered exactly, for example, /adminpve loot, not /adminpve loo. This message is displayed if the player doesn't have the required permissions or if the command was entered incorrectly. A list of all available commands can be found on the plugin's page under the "Commands" section.
-
Changed Status from Pending to Work in Progress
-
@Koshara I checked the plugin's page and currently, I’m missing a couple of hooks to make it work. I’ve reached out to the plugin author and am awaiting their response.
-
Team members unable to loot monuments that someone on the team claimed
IIIaKa replied to NotAmbient's Support Report in Support
@NotAmbient Hello, thank you for reaching out. Did I understand correctly that in a claimed monument, friends cannot loot anything in the monument? And how did they become friends, through vanilla mechanics or via a plugin? -
Team members unable to loot monuments that someone on the team claimed
IIIaKa replied to NotAmbient's Support Report in Support
Changed Status from Pending to Work in Progress -
Yes, when the server or plugin is restarted, the data will be saved in a .json file. This will reduce save operations and the file is only needed during the plugin initialization/load to retrieve previously saved values. After that, the file is no longer required.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Closed Changed Fixed In to 0.1.3
-
Note, this will not change the values for existing players. To reset it for them, you need to: Install the plugin(new version) ; Unload the plugin(o.unload or c.unload) ; Change the default value for auto-modification in the config file to the one you want, most likely "false" in your case; Delete the data file(.../data/vDelivery.json) ; Load the plugin back(o.load or c.load) .
-
@Kobani Please re-download the plugin. The config file has been updated to allow setting a default value for auto-modification for new players.
-
As I understand, you want the config file to allow setting a default value for auto-modification for new players?
-
It seems I forgot to include it in the description. My apologies.
-
Wouldn't it be better to let authors decide for themselves? Add a tag(similar to Carbon and Oxide support) indicating that only the author is responsible for maintaining the plugin's functionality. If the author is unavailable, Codefling would not assume the right or obligation to provide support. And when attempting to purchase a product that does not grant Codefling the right to support this plugin, the buyer will receive a warning stating that if the author disappears, no one will refund the money or provide support for the plugin. After all, the right to intellectual property has not been abolished by anyone.
-
After entering the command, did you reload the plugin or the server? I made the save to a file only during unload plugin to avoid unnecessary operations.
