Ark-Plugin-TribeSlotCooldown
Features:
Planned Features:
A: No. And every server needs a own database.
Q: Is there a problem when increase or decrease the tribe limit?
A: Increasing is no problem. When decreasing the limit it is recommended to wipe the plugin database.
Q: What should I do when i reset my servers?
A: Wipe the plugin database too.
Known issues:
none so far. I used the plugin two months at my servers without any trouble.
Source code is open:
github
Features:
- When a player leaves or gets kicked from a tribe the used tribe slot is set to cooldown.
- Tribe slots with cooldown are not longer usable for tribe invitations.
- For tribe merges the new tribe must have enough tribe slots (without cooldown) for all player and all active slots with cooldown of the old tribe.
- When tribes merge all slots with cooldown of the old tribe will be inherited to the new tribe.
- Server Admins (authenticated with the enablecheats command) are ignored of the implementation. They don´t set tribe slots to cooldown when leaving the tribe.
- Customizable config
- No save game modivication.
- /SlotsCooldown - Shows all tribe slots with cooldown. Can get changed in configuration.
- GetTribeIdOfPlayer <SteamId64> returns the tribe id of a given player. Only works when player is online.
- ListPlayerTribeCooldownSlots <SteamId64> returns a list of tribe slots with cooldown of a given player. Only works when player is online.
- ListTribeCooldownSlots <TribeId> returns a list of tribe slots with cooldown of a given tribe.
- ResetSlotOfTribe <TribeId> <SlotNr> resetets a tribe slot cooldown of a given tribe. Do ListTribeCooldownSlots to determine <SlotNr>
{
"General":{
"General":{
"DbPathOverride":"", // Path to database. If empty, default path is used
"SlotCooldown": 24, // Slot cooldown in hours
"MessageTextSize": 1.4, // Text size for player notifications
"MessageDisplayDelay": 10, // Notification time in secounds
"AutoWipeDatabase": true // if set to true automatically resets the database when a new world is started
},
"Messages":{
//Notification when tribe join is suppressed
"SuppressPlayerJoinTribeMessage":"The Tribe you like to join does not have a free player spot",
//Notification when tribe merge is suppressed
"SuppressMergeTribeMessage":"The Tribe you like to merge with does not have enough free player spots", //Notification when chat command /SlotsCooldown is used
"CommandDisplaySlotsMessage":"Currently there are {} slots on cooldown and not usable for tribe invitations",
//Lists all slots with cooldown when chat command /SlotsCooldown is used
"CommandDisplaySlotsMessageSlotCooldown":"Slot {} again usable in {} hours, {} minutes, {} secounds"
},
"Commands":{
"CommandPrefix":"/", // Prefix for chat command
"CommandDisplaySlots":"SlotsCooldown" // Chat command for player to check current tribe slots with cooldown
}
}Planned Features:
- MySQL database support
A: No. And every server needs a own database.
Q: Is there a problem when increase or decrease the tribe limit?
A: Increasing is no problem. When decreasing the limit it is recommended to wipe the plugin database.
Q: What should I do when i reset my servers?
A: Wipe the plugin database too.
Known issues:
none so far. I used the plugin two months at my servers without any trouble.
Source code is open:
github
