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.

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

Arcane workbench not working in modpack #652

Closed
GenWarfield opened this issue Apr 27, 2021 · 2 comments
Closed

Arcane workbench not working in modpack #652

GenWarfield opened this issue Apr 27, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@GenWarfield
Copy link

GenWarfield commented Apr 27, 2021

Please read the guide for contributing before posting.

Minecraft version: 1.12.2
Wizardry version: 4.3.4
Environment: Server

Issue details:
I'am currently using the R.A.D pack (lite) modpack (server edition) and it seems that upgrading the wizard armor sets doesn't work properly. The animation plays but neither the upgrade material nor does the wizard armor get upgraded (such as using resplendent thread, etc), they also do not get consumed.

I suspect it may be caused by quality tools mod but am not sure. Would appreciate some help in tracing the issue as I'm not sure how to blacklist the armor or isolate the issue.

Further testing has shown that electrobob wizardry armor don't provide any mana reduction effects whatsoever either.


Issue is not present in single player, the arcane workbench functions normally and wizard armor is upgraded normally as well as upgrade material being consumed.

Other mods involved: R.A.D (lite) modpack, potentially caused by Quality tools or an error with the server world file..

Link to crash report (if applicable): no crash, just absence of functionality.

@MagmaBro123
Copy link

MagmaBro123 commented Apr 27, 2021

I'd recommend asking the R.A.D developers. If they use CompatSkills,
then disable its compat. with Wizardry. Read #609 for more info.

@Electroblob77
Copy link
Owner

Electroblob77 commented Jun 14, 2021

Sounds a lot like that issue to me. Please reopen this issue if it turns out not to be.

@Electroblob77 Electroblob77 added the duplicate This issue or pull request already exists label Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants