Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Arcane Wizardry sorcery install spell book error #722

Closed
ghost opened this issue Oct 2, 2021 · 2 comments
Closed

Arcane Wizardry sorcery install spell book error #722

ghost opened this issue Oct 2, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists external bug This issue was caused by another mod, but I might still be able to prevent it workaround exists There is a known workaround that avoids this issue

Comments

@ghost
Copy link

ghost commented Oct 2, 2021

Minecraft version: 1.12.2
Wizardry version: 4.3.4
Environment: Server

Issue details: I was at the arcane workbench trying to install the spell book for my staff, but when I clicked "Install" there was an error in the background and the staff failed to install the spell

Link to crash report (if applicable): https://paste.ubuntu.com/p/HpqJM3SN9q/
@ghost ghost added the bug Anything that isn't working how it's supposed to label Oct 2, 2021
@WinDanesz
Copy link
Collaborator

Looks like the "Compatskills" mod causes it, not wizardry

@WinDanesz WinDanesz added duplicate This issue or pull request already exists external bug This issue was caused by another mod, but I might still be able to prevent it workaround exists There is a known workaround that avoids this issue and removed bug Anything that isn't working how it's supposed to labels Feb 3, 2022
@WinDanesz
Copy link
Collaborator

duplicate of #609

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists external bug This issue was caused by another mod, but I might still be able to prevent it workaround exists There is a known workaround that avoids this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@WinDanesz