-
Notifications
You must be signed in to change notification settings - Fork 16
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
[BUG] & [Feature] Warmups don't work on folia #123
Comments
For the bug we could use a little bit more information on it such as the version of Folia and the plugin you're using. Also is your config.yml set properly and are there any errors printed when the warm up is supposed to get cancelled? As for the feature request - I'll gladly put it into the list for future versions! |
I have no errors in the console [14:59:47 INFO]: This server is running Folia version git-Folia-"372d479" (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 372d479) 15:00:50 INFO: - Developed by Niestrat99 and Thatsmusic99 |
use-warps: true Warm-up timer for /tpa.tpa: default Warm-up timer for /tpaheretpahere: default Warm-up timer for /tpr, or /rtp.tpr: default Warm-up timer for /warpwarp: default Warm-up timer for /spawnspawn: default Warm-up timer for /homehome: default Warm-up timer for /backback: default |
Alright, thanks for the information, we'll work on a fix for it as soon as we got time! |
Unable to reproduce the issue on the latest version of Folia, warm-ups do cancel for me. Try bumping Folia's version but I'm very doubtful that would do anything, could it be an OP thing? (Also for the sake of issue tracking, please keep feature requests and bugs in separate issues in the future, thank you!) |
So, I happened to run into it whilst testing another bug you mentioned, never mind |
Should be fixed in the latest Folia build |
Warmups don't work on folia, it doesn't cancel the teleportation even if player moved.
Feature Request: Can you add only take-damage warmup option? (I want to give players moving possibility)
The text was updated successfully, but these errors were encountered: