Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TrialSpawner API is very lacking #12023

Open
myToasterDied opened this issue Jan 27, 2025 · 0 comments · May be fixed by #12025
Open

TrialSpawner API is very lacking #12023

myToasterDied opened this issue Jan 27, 2025 · 0 comments · May be fixed by #12025
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added.

Comments

@myToasterDied
Copy link

myToasterDied commented Jan 27, 2025

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

Image

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!

@codebycam codebycam added status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added. and removed status: needs triage labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepted Disputed bug is accepted as valid or Feature accepted as desired to be added.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants