.png.9c4b6f2c79b42a5799d6d7bc91badfab.png)
StrongWolves
-
Posts
36 -
Joined
-
Last visited
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by StrongWolves
-
Ok, thanks.
-
@Mevent
-
I tested Dungeon event, animals, and players, and it still shows the same. And for deer, it doesn’t show anything at all.
-
The plugin seems broken to me. It shows the same damage for body and head, and it doesn't match the combat log. Can I request a refund if it isn't fixed?
-
-
Hi, I purchased the plugin and after uploading it and testing it for a while, my creative players immediately found a way to bypass the destruction using a drone and throwing C4. Could we add something to make this impossible? -
@Martian Please add hook Dungeon Complet.
-
@Martian Is it possible to use a 0.5% chance?
-
@Martian Hi, would it be possible to add a hook for successful event completion? I’d like to connect it to the leaderboard.
-
Yes, Nightmare is like that on purpose, since I don’t use it. I’ve currently contacted the RealPVE developer, and hopefully they’ll create an update for me. Thank you for your help — hopefully it will be resolved soon. -
Okay, maybe I’m the one not explaining it clearly When I disable RealPVE and complete a raid, I normally get the cooldown exactly as I have it configured. No purchase required — just dealing damage claims the raid, and after finishing it I receive the cooldown.
-
I think we still don’t understand each other. I’m using automatic events — the player just enters the raid, deals damage, the raid becomes theirs, they finish it, and they receive a cooldown. Everything works exactly like this. But only when RealPVE is disabled. I do not use /buyraid at all.
-
I’ve been dealing with this cooldown issue for weeks, and I finally figured out it’s caused by this. Because when RealPVE is disabled, everything works perfectly — but as soon as it’s enabled, it starts breaking things. I’ll try to contact the plugin author. Thank you. And please — can you accept my Discord?
-
I have everything set to false in RealPVE, and it still doesn’t work… If I disable RealPVE and enter a raid, deal damage, the raid becomes mine, and after I complete it I receive the cooldown properly. But when RealPVE is enabled, this does not work at all. At this point I really don’t know what else to try…
-
@nivex I have a problem with the RealPVE plugin… When it’s enabled and I enter a raid, it automatically purchases the raid (based on the RealPVE config), and after completing the raid I don’t receive any cooldown. When I disable RealPVE, everything works fine — I enter the raid, deal damage, claim the raid, finish it, and I get the cooldown properly. But when RealPVE is enabled, this doesn’t happen at all. Is there any way to add an ignore for this plugin somewhere? It seems like RealPVE is interfering with the whole system.
-
@IIIaKa Hi, RealPVE is causing problems with Raidable Bases… When I enter a raid while RealPVE is enabled, I don’t receive any cooldown after finishing the raid. But if I disable RealPVE and enter the raid normally, I do get the cooldown after completion. I’ve been dealing with this for about a week, and only now I figured out that RealPVE is the cause. Is it possible to add some kind of ignore for RealPVE? It’s really breaking the system I have set up. I’m sending the RealPVE + Raidable Bases config. { "Is RaidableBases enabled?": false, "RaidableBases Console command": "rbevent", "Is it worth enabling forced auto-buy for raidable bases where the final price is greater than 0?": true, "Settings for the RaidableBases. WARNING: The first value will be used as a template for new levels": [ { "Price": 0.0, "Language key for displaying the difficulty name": "MsgRaidableBasesEasy", "List of difficulty levels to which these settings apply": [ 0 ], "Time in seconds (1-15) given to respond for purchasing a Raidable Base. Note: This is shown to everyone who enters, and the first person to buy it will claim it": 5.0, "Is it worth using a progress bar for bars with a counter?": true, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP RaidableBase. 0 disables the delay": 10.0, "Settings id for the status bar": "raidable_bases_easy", "Settings id for the progress status bar": "raidable_bases_easy" }, { "Price": 0.0, "Language key for displaying the difficulty name": "MsgRaidableBasesMedium", "List of difficulty levels to which these settings apply": [ 1 ], "Time in seconds (1-15) given to respond for purchasing a Raidable Base. Note: This is shown to everyone who enters, and the first person to buy it will claim it": 5.0, "Is it worth using a progress bar for bars with a counter?": true, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP RaidableBase. 0 disables the delay": 10.0, "Settings id for the status bar": "raidable_bases_medium", "Settings id for the progress status bar": "raidable_bases_medium" }, { "Price": 0.0, "Language key for displaying the difficulty name": "MsgRaidableBasesHard", "List of difficulty levels to which these settings apply": [ 2 ], "Time in seconds (1-15) given to respond for purchasing a Raidable Base. Note: This is shown to everyone who enters, and the first person to buy it will claim it": 5.0, "Is it worth using a progress bar for bars with a counter?": true, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP RaidableBase. 0 disables the delay": 10.0, "Settings id for the status bar": "raidable_bases_hard", "Settings id for the progress status bar": "raidable_bases_hard" }, { "Price": 0.0, "Language key for displaying the difficulty name": "MsgRaidableBasesExpert", "List of difficulty levels to which these settings apply": [ 3 ], "Time in seconds (1-15) given to respond for purchasing a Raidable Base. Note: This is shown to everyone who enters, and the first person to buy it will claim it": 5.0, "Is it worth using a progress bar for bars with a counter?": true, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP RaidableBase. 0 disables the delay": 10.0, "Settings id for the status bar": "raidable_bases_expert", "Settings id for the progress status bar": "raidable_bases_expert" }, { "Price": 0.0, "Language key for displaying the difficulty name": "MsgRaidableBasesNightmare", "List of difficulty levels to which these settings apply": [ 4 ], "Time in seconds (1-15) given to respond for purchasing a Raidable Base. Note: This is shown to everyone who enters, and the first person to buy it will claim it": 5.0, "Is it worth using a progress bar for bars with a counter?": true, "PvP - Sets the delay in seconds that a player remains in PvP mode after leaving a PvP RaidableBase. 0 disables the delay": 10.0, "Settings id for the status bar": "raidable_bases_nightmare", "Settings id for the progress status bar": "raidable_bases_nightmare" } ], "Version": { "Major": 0, "Minor": 1, "Patch": 3 } } -
@nivex May I ask why my cooldown isn’t working? I have cooldowns set to one hour. When I finish a raid and the base despawns, I see the UI showing cooldowns for all bases, which is correct. However, if I try to enter a raid base during the cooldown using the purchase button, it still lets me in and the cooldown is ignored. I am entering the raid using the purchase button. I can also provide my config if needed — please help. RaidableBases.json
-
@nivex Hello, i have error with new update.
-
@IIIaKa Hello, I have been dealing with an issue with AbandonedBases for some time. When a player raids a base and finds a locked box, then destroys it, it turns into a grey stash that cannot be looted. I was wondering if this could be caused by a conflict with the RealPVE plugin. Do you know how you could help me with this?
-
So the fix has been released, I updated the plugin, but the problem still persists. If a player raids an abandoned base and destroys a chest that has a lock on it, it turns into a grey stash and cannot be looted. How can I fix this? Is it somewhere in the config? -
@nivex Hello, I’m constantly having an issue with a plugin – or possibly with the interaction between this plugin and RealPVE. When players raid a base that is already raid-allowed (for example an abandoned base), any locked storage containers that get destroyed turn into a small grey box. This box cannot be opened by anyone, even though the base should be fully raid-able. I’m not sure if this behavior is caused by a setting in the plugin, or if it’s a conflict with RealPVE (ownership / protection not being removed correctly). Is this controlled by some configuration option, or is it a known incompatibility with RealPVE?
-
Hello, So there is no way to set it up so that when a player completes an easy raid, they receive a notification that they have a 1-hour cooldown for starting another raid (of any difficulty), and at the same time see some kind of UI showing this cooldown? And during this cooldown, it would simply be impossible to purchase or start another raid? Ideally, the UI would remain visible the entire time and display the remaining cooldown.
-
@nivex Hello, I have an issue with cooldown settings. I have a cooldown set to 60 minutes. After finishing a raid, when I enter a raid base, I am not able to purchase it (the system requires purchasing the base from inside). However, once the previous raid base despawns, I am immediately able to purchase another raid. The purchase is done via UI, not via commands. What I want is: After finishing a raid, I should receive a 1-hour cooldown During this cooldown, I should not be able to enter or purchase another raid base Ideally, the system should display a message informing me that I am on cooldown How should this be configured to work correctly?
-
@nivex AbandonedBases is your plugin, right? And I have a problem — if a base is abandoned and a player raids it, they can’t take the loot from the crates. A grey loot bag appears and it can’t be looted.
-
@nivex Hi, I have a problem with the plugin — when a player is raiding or finishes a raid, they can’t loot. Is the plugin conflicting with RealPVE?
.thumb.png.0ec63e066e9a8dfb77f3861c7b273069.png)
