Totem Colldown

[InvalidTeslaa]

Description of Issue

The change to CMis totem handling make it now not useable anymore, always on die it say im on cooldown

Version Information

https://cdn.letsgrief.net/2024/07/23/82b1625d-f3e8-418d-8cbb-e196dfe15e37.png

Errors

None

Relevant Config Sections

Totem:
  # When this set to true, on players death totem will be used even if he is not holding it in hand
  RemoveFromInventory: true
  Cooldown:
    # When this set to true player can use totem only every X second's
    Use: true
    Time: 20
  Warmup:
    # When this set to true player can use totem to have X amount of second's, during which he can die and be resurected
    # Totem will be consumed durring activation and wont be returned even if resurection is not used during warmup time
    Use: false
    Time: 10
  # If player falls into void while having totem, he will be teleported to respawn location and totem gets consumed
  ProtectFromVoid: false
  Effects:
    # Time in seconds effect needs to be applied to the player. Set it to 0 if you want to disable it
    Regeneration: 45
    FireResistance: 40
    Absorbtion: 5

Relevant Plugins

AngelChest v13.1.1

Agreements

• My server is supported by CMI.
• My version of CMI at the time of this report is up to date.
• I have searched the github and asked around before making this report.

[mercurialmusic]

Confirming, my players have been complaining about this as well. Totems no longer work at all, even in the main hand, but now only show that they are on cooldown.

CMI plugin version: 9.7.4.7 Velocity CMIB SqLite
CMILib: 1.5.0.9
Server: Paper(497) 1.20.4-R0.1-SNAPSHOT-
CMI economy: Enabled Vault: 1.7.3-CMI CMI Chat: Disabled
Modules -> 64 enabled 2 disabled: ranks, skin

Editing to note that it seems somewhat inconsistent. Most of the complaints I was getting was last night after we first updated to 9.7.4.7. After a restart I haven't been able to reproduce it again, so it might have resolved itself somehow.

[Zrips]

Looks to be an issue which was somewhat inconsistent. Will be resolved with next update