-
Notifications
You must be signed in to change notification settings - Fork 35
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
Could not pass event PluginIntegrationEnableEvent to CustomCrafting v4.16.10 #378
Comments
So far I didn't have much time and was unable to reproduce the issue. |
If you need any help in testing or want to experiment yourself, I can give you access to my server panel. You can contact me via discord .orphey (member of your ds community) |
Indeed, I also encountered this situation. I used customcrafting-spigot-4.16.11, wolfyutils-spigot-4.17-beta.6,ItemsAdder_3.6.4-release-2. [15:27:50 ERROR]: Could not pass event PluginIntegrationEnableEvent to CustomCrafting v4.16.11 Plugin List: |
I have the same problem here with the paid version... I did 1 customcraft with a custom Itemadder item and everything is fine, but not for the second one. When i restart the server i got this error! Paper-1.21.1-74
|
What happened?
I discovered that after updating to CustomCrafting v4.16.10 and setting sync: true in main config - ItemsAdder recipes are missing after server load.
If I reload plugin itself via /cc reload command - all recipes are loaded then.
Only error I found is this:
[11:40:25 INFO]: [WolfyUtilities] Enabled plugin integration for ItemsAdder
[11:40:25 ERROR]: Could not pass event PluginIntegrationEnableEvent to CustomCrafting v4.16.10
(Full log attached)
How can the bug be reproduced?
Just install all mentioned plugins, create any recipe with ItemsAdder item and reload server.
Expected Behaviour?
All recipes succesfully load on server start.
Plugin version
CustomCrafting v4.16.10, WolfyUtils 4.17-beta4, ItemsAdder_3.6.4-release-3
Server software
Paper 1.20.4
Relevant log output
Submit issue
The text was updated successfully, but these errors were encountered: