-
Notifications
You must be signed in to change notification settings - Fork 1
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
Windup & Cooldown configurability #1
Comments
Sorry for the late reply, I have been busy for a while with alot of life stuff. I aim to port TPA++ to Fabric during the weekend, I will also include this feature in the next release. So correct me if I am wrong, you want a feature that if the player ran /TPA, they would have to wait 10 seconds (configurable) before actually sending the request. Thank you for suggesting this feature! |
Windup's as well as some bug fixes, stability improvements and performance enhancements are out in the latest release (Check Modrinth if it's not yet out on CurseForge). |
…t of code asynchronous. The windups requested in issue #1 have been fixed. Additionally, the code now supports 1.20.1 - 1.20.4, (although on quilt it only works on 1.20.1 for some unknown reason).
…me missing config options. Build is currently not stable
Cooldowns will be implemented on the next release, Scheduled for Sunday 14/4/2024. |
Removed features I don't plan on doing, I want to get TPA++ to a stable state that makes it easy for others to pick up this project, and update it if they wish to. I will just fulfill the feature requested in #1.
Cooldowns have been finally implemented as of release 1.6 |
I'd like to request the implementation of an optional togglable windup that makes it so when a player runs a command there is a timer until the command executes (e.g 10 seconds by default) and if the player is damaged/moved in that timeframe the command is cancelled.
I'd also like to request cooldown configurability so that the cooldown between command usage can be reduced/increased based on personal preference.
The text was updated successfully, but these errors were encountered: