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
Cannot delete teams.yml cache, I've deleted the whole file, reinstalled the whole plugin, deleted the teams individually, but for some reason they come back everytime.
Expected Behaviour
Have the teams delete and allow them to be recreated.
How to Reproduce
Have people create teams (ex. RiOT)
Attempt to clear the created teams through the teams.yml file
Restart server
Try to create a team name (ex. RiOT)
Error "Team already exists"
All the cache comes back even though it was deleted.
Error message
No response
Output of /teama version
theres nothing the teama command can do within this situation, teama disband doesn't work.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Why are you trying to delete teams in the file rather than using the /teama disband command. In almost all cases modifying the files directly is not supported.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stalebot
added
the
inactive
The issue has had no activity for 20 days, it will be closed in 10 days time
label
Jun 1, 2024
This issue is being closed for inactivity. If you are still having problems feel free to open a new issue linking this one, make sure you answer any questions asked in the new issue.
What is the bug?
Cannot delete teams.yml cache, I've deleted the whole file, reinstalled the whole plugin, deleted the teams individually, but for some reason they come back everytime.
Expected Behaviour
Have the teams delete and allow them to be recreated.
How to Reproduce
Error message
No response
Output of /teama version
theres nothing the teama command can do within this situation, teama disband doesn't work.
Additional Information
No response
The text was updated successfully, but these errors were encountered: