Different Cooldown Per Schematic

[ygtdmn]

Can we change cooldownRestart: 600 per island in island-schemes?.

[dutchy1001]

no, only in the main settings

[ygtdmn]

So, can you add that option?

[dutchy1001]

not per island

[rlf]

Questions: What do you mean with "per island"? Do you need to have different cooldowns for different schematics? Or do you need to have separate cooldowns for each (meaning, you can restart 1 of each immediately after the other?)

We already have cooldowns for the /is restart command - but it's currently shared across all schematics.

Or, are you referring to the "confirmation timeout"?

[ygtdmn]

I mean different cooldowns for different schematics.

[rlf]

So, why do you need this? And how do you imagine it working? I.e. let's say you have the following:

schematicA:
  cooldown: 45s
schematicB:
  cooldown: 30s
schematicC:
  cooldown: 5m

Would that mean, that a user can create an island with schematicC, then restart it right away with schematicB? Or does he have to wait 5m before chosing another schematic? Or, will a user that create an island with schematicA have to wait 5minutes before he can chose schematicC?

I don't really see this adding any value at all - unless you can actually tell me WHY you need that feature added. It just adds a lot of confusion (which is already quite high) reg. the cooldowns.

[ygtdmn]

Why i want this: I have special islands for VIP players. They are giving their islands another players for money. In 10 minutes they can create new island. For that reason i want VIP players can restart or create their islands per 7 days. If they dont want wait they can create a standart island in 10 minute.

How can you do that:

schematicA:
  cooldown: 45s
schematicB:
  cooldown: 30s
schematicC:
  cooldown: 5m

this will work. Imagine that player created a schematicC island. If he wants restart the island he need to wait 45s for schematicA, 30s for schematicB and 5m for schematicC.

[dutchy1001]

How can you do that: schematicA: cooldown: 45s schematicB: cooldown: 30s schematicC: cooldown: 5m

this will work. Imagine that player created a schematicC island. If he wants restart the island he need to wait 45s for schematicA, 30s for schematicB and 5m for schematicC

That will not work that way or very complicated to code. If their using schematicC with a waiting time of 5 minutes they have to wait 5 minutes then before they can use the restart command again otherwise that would defeat the object of the cooldown.

I don't get the 10 minutes and 7 days you mentioned (maybe lost in translation there).

An other way to do what you are trying to accomplice is to give your VIP players the cooldown exempt permissions:

• usb.exempt.cooldown.create
• usb.exempt.cooldown.restart

they will then be able to create or restart the island at any time (restart after 10 minutes is kinda useless too).

[ygtdmn]

If their using schematicC with a waiting time of 5 minutes they have to wait 5 minutes then before they can use the restart command again otherwise that would defeat the object of the cooldown.

Then can you make cooldown exempt per schematic?

Like: usb.exempt.cooldown.create.skySMP usb.exempt.cooldown.create.default

They will have 7 days cooldown for VIP islands but they can create default island anytime.

[dutchy1001]

That brings us back at the beginning again instead of in the config then per permission.

if I understand it correctly, you let VIP players create multiple islands, how? As this isn't implemented in the plugin.

[ygtdmn]

No, not multiple. I will tell like a story:

VIP player creating a vip island, invites another player, making him leader and then he quit. After 10 minutes(cooldown for restart) creating another VIP island. I wanna prevent this because all players have VIP islands with that way. I can prevent it with 7 days cooldown. But non-guilty players also need to wait 7 days. For that reason players can create a default island whenever they want. But creating VIP islands need to have 7 days cooldown.