You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The trial spawner tilestate lacks features - the most important one for me being getting and setting the cooldown_ends_at value.
Providing access to this value would be highly beneficial, as it would allow users to get the remaining time before the trial spawner becomes available again, as well as modify or remove the cooldown as needed.
Describe the solution you'd like.
I propose these 2 functions:
getCooldownEndTime() returns a long that is the gametime at which the cooldown ends (this is what the game stores as the value), if there is no value it would return 0 or null.
setCooldownEndTime(Long) sets this value for the tilestate.
Describe alternatives you've considered.
.
Other
Implementing this feature shouldn't be too complex, considering there is already a function in setting and getting the target_cooldown_length value. Of course, that's just my perspective. It's not me acutally doing the coding!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
The trial spawner tilestate lacks features - the most important one for me being getting and setting the
cooldown_ends_at
value.Providing access to this value would be highly beneficial, as it would allow users to get the remaining time before the trial spawner becomes available again, as well as modify or remove the cooldown as needed.
Describe the solution you'd like.
I propose these 2 functions:
getCooldownEndTime()
returns a long that is the gametime at which the cooldown ends (this is what the game stores as the value), if there is no value it would return 0 or null.setCooldownEndTime(Long)
sets this value for the tilestate.Describe alternatives you've considered.
.
Other
Implementing this feature shouldn't be too complex, considering there is already a function in setting and getting the
target_cooldown_length
value. Of course, that's just my perspective. It's not me acutally doing the coding!The text was updated successfully, but these errors were encountered: