About CoolDown....

Hello,

Previously (https://codefling.com/files/support/29787-regarding-the-buyraid-command/), I contacted you because Buyable Raidable Bases were not spawning.

Starting this wipe, I switched to letting RaidableBases handle the RP cost directly instead of using the Shop plugin. At first, I thought everything was working correctly, but I've now received reports that certain players can purchase a base and nothing happens.

My guess is that the issue is related to the cooldown system.

For example, one player was in a team of four. Two members were online and purchased a Raidable Base. The base spawned correctly, but they logged off before completing it.

Later, when the other two teammates logged in and tried to purchase another Raidable Base, nothing happened. There was no response from RaidableBases and no message was displayed.

On another day, two team members completed a Raidable Base successfully. Later, the two teammates who had been offline logged in. Sometimes the Buyable cooldown UI appeared for them, and sometimes it did not.

When the cooldown UI did not appear, it seemed that the cooldown was still active in the background. They were able to purchase a base, but after purchasing, nothing spawned and no message was shown.

I've experienced something similar myself while playing on my own server. Sometimes my friend who completed the raid with me sees the cooldown UI, while I don't. Other times, I see it as expected.

Because the cooldown UI appears inconsistently, I'm wondering if there might be a small issue with the cooldown logic itself.

Just in case, I've attached my .json configuration file as well.

I apologize for taking up your time, and I really appreciate your help. Thank you!

RaidableBases.json

heya. most of these issues I haven't heard of before and I'm not able to reproduce them by myself but it should be easy to fix. I can add any potential missing messages, and ensure that buyable cooldowns are always applied correctly  though there are no cooldowns configured for admin or those with raidablebases.allow permission. a bad copypaste file can easily cause issues with a purchase, but I need an error from the server console to help with that.

"They were able to purchase a base, but after purchasing, nothing spawned and no message was shown."

this is a bit confusing. it is possible to press buy and not receive any response, that has happened to me and I will look into it. but if payment was taken then there is always a message.

Thank you for your reply!

I do have administrator permissions. However, I still sometimes see the Buyable cooldown UI and sometimes I don't.

Just to confirm, even if the cooldown UI is displayed, players with administrator permissions (or the raidablebases.allow permission) should never actually be affected by the cooldown. Is that correct?

Also, I'd like to clarify something from my previous ticket (URL).

I'm still using the Shop plugin. However, the RP is effectively only deducted by Shop.

My Shop item executes the following command:

deposit %steamid% 20000 | buyraid 3 %steamid%

The flow is:

The player purchases the Expert raid from Shop for 20,000 RP.

Shop immediately refunds 20,000 RP using the deposit command.

The buyraid command is executed.

RaidableBases is configured to charge 20,000 RP.

So although Shop initially deducts 20,000 RP, it is immediately refunded, and the actual cost comes from RaidableBases. The player therefore pays 20,000 RP in total.

The issue is that the Shop purchase log always appears, but after that, RaidableBases produces no messages at all—not even the usual "paid" message—and nothing is written to the server console either.

I hope this explains the situation more clearly. Sorry for the confusion, and thank you again for looking into this!

[05:09:34] Loaded 210 items from RaidableBases/Difficulty_Loot/Easy
[05:09:34] Loaded 281 items from RaidableBases/Difficulty_Loot/Medium
[05:09:34] Loaded 303 items from RaidableBases/Difficulty_Loot/Expert
:[05:09:34] Loaded 314 items from RaidableBases/Difficulty_Loot/Nightmare
[05:09:34] Loaded 4 items from RaidableBases/Base_Loot/Easy Bases
[05:09:34] Loaded 9 items from RaidableBases/Base_Loot/Medium Bases
[05:09:34] Loaded 9 items from RaidableBases/Base_Loot/Expert Bases
[05:09:34] Loaded 11 items from RaidableBases/Base_Loot/Nightmare Bases
[05:09:51] [RaidableBases] 25% loaded (121 potential points)
[05:10:04] [RaidableBases] 50% loaded (281 potential points)
[05:10:17] [RaidableBases] 75% loaded (607 potential points)
[05:10:30] [RaidableBases] 100% loaded (1029 potential points)
[05:10:30] [RaidableBases] Grid initialization completed in 58 seconds and 355 milliseconds on a 4500 size map with 1029 potential points.

By the way, there don't seem to be any errors in the server logs.

hi, ok, I will look into it. you shouldn't see the cooldown ui

5 minutes ago, nivex said:

hi, ok, I will look into it. you shouldn't see the cooldown ui

Thank you very much! I really appreciate your help.

By the way, I have one more question.

As I mentioned earlier, suppose a team has a mix of online and offline players. If the online players complete a raid and the team cooldown becomes active, then one of the players who was offline logs in afterward.

In that situation, is it the expected behavior for the cooldown UI to appear for the player who has just logged in?

yes, they should see the cooldown ui even if they were offline previously.

Sorry, would you mind if I ask something that's not directly related?

It seems I completely misunderstood how this works.

Am I correct in understanding that:

Player Lockout = the amount of time before a player is allowed to enter another Raidable Base (the dome/event area).

Buyable Cooldown = the amount of time before a player can purchase another Raidable Base.

So, for example, if I set the Player Lockout to 90 minutes, does that mean that after completing a raid, the player must wait 90 minutes before they can enter another Raidable Base, whether it's an automatically spawned one or a buyable one?

Is that correct?

heya, that is mostly correct, but it is optional with Allow Ally With Lockouts To Enter

• if enabled, lockouts will not prevent a player from entering someone else's purchased event if they are in a team/clan/friend
• if disabled, the player will not be able to enter any event for the difficulty that they have a lockout for. 
• player lockouts will never prevent a player from purchasing their own event, and this is what Buyable Cooldowns are for.
• player lockouts are not applied to any event in a purchased state - if it becomes inactive and defaults back to the public then it is possible.

Issues with the cooldowns and messages have been fixed in the next update, if you do not receive a message then the command was not received by the plugin to begin with