-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Crazyenchantments #335
Comments
What exactly is the issue you are experiencing? I can't magically make something work if I don't know what's broken. |
when is silkspawners on the server crazyenchatments does not start, they told me it is because of the silkspawners and when removing it if it worked, could they add compatibility? |
If it does not start, please show the corresponding error message |
Do you happen to have two SilkSpawners files in your plugins folder? |
No, there is only one, but they told me that there were more people who had this problem having those two plugins. |
how can i solve it? |
Hello? |
I've had no time to investigate this further. As you are on a dev build, have you tried upgrading CrazyEnchantments? |
Hi, would like to add to this further. Error message below. I believe it's could be due to CE using an older version of SilkSpawners class which leads to a breaking change when SilkSpawners class got an update from your end. I'm trying to download previous version of SilkSpawners to see which works. Anyway this issue is happening to me while on MC 1.16.5 and CE v1.8 Dev build-10. Unable to enable both CE and Silk Spawners. Corresponding ticket on CE Repository: Crazy-Crew/CrazyEnchantments#639 |
Can silkspawner add support for crazyenchantments? with silkspawner it doesn't load that plugin
I think it makes the plugin load after, i use 1.17.1 and the versions are:
CrazyEnchantments version 1.8-Dev-Build-v10-Build#174
SilkSpawners version 7.1.0
This server is running Purpur version git-Purpur-1377 (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT) (Git: b6d1b6a on ver/1.17.1)
The text was updated successfully, but these errors were encountered: