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
Unable to acquire most blocks using Chisel chisels on 1.12.2 server #12
Comments
I am commenting to show interest in this issue; I am able to replicate it with a similar configuration (Immersive Engineering 0.12-74, Forge #2517, UCW 0.15). The mod is essentially nonfunctional on 1.12 servers. |
This is actually a bug in Chisel, as their getSubBlocks() is client-side-only, whereas in the latest 1.12.x versions getSubBlocks/getSubItems should no longer be marked as such. Paging @tterrag1098 - could you please fix it in your 1.12 branch and push a new version? |
This has been fixed, it will be included in the next release. |
Worked around locally so you don't have to wait! |
Using a Chisel chisel, unable to chisel blocks to most UCW variants on Multiplayer servers. All available variants show as normal when inserted/selected with chisel. Some of them allow the first, two, or four variants to be pulled/chiseled, but none beyond that. "iChisel" will deceptively chisel the block item, but server will revert it. Blocks can be pulled from creative-esque menus and placed just fine. Everything works 100% fine in Single Player.
Client Minecraft version 1.12.2 using:
MultiMC 0.6.0-develop-1082
Forge 14.23.0.2491
LWJGL 2.9.1
Server running Forge 14.23.0.2491 using installer jar.
Mods files running on both using default config files:
Chisel-MC1.12-0.0.14.18
CTM-MC1.12-0.2.3.9
UnlimitedChiselWorks-0.1.5
Tested with blocks from each of these mods one-by-one with fresh configs and worlds:
ImmersiveEngineering-0.12-72
Traverse-1.12.1-1.3.1
AbyssalCraft-1.12-1.9.4-pre-4
Initially ran into this issue on a private modpack being hosted on a friend's server. Hosted a server locally in attempt to narrow down issues. I apologize in advance if there was some sort of formatting that I should be using for this issue report.
The text was updated successfully, but these errors were encountered: