-
Notifications
You must be signed in to change notification settings - Fork 755
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
Hammer/Excavator single block bug (1.7.0d3/1.7.0d4) #1072
Comments
emperor06
changed the title
Hammer/Excavator single block bug (1.7.0d3)
Hammer/Excavator single block bug (1.7.0d3/1.7.0d4)
Oct 9, 2014
Same issue with 1.7.0d4. Mantle is the latest available (0.3.2), same with ExtraTIC. Minecraft is 1.7.10. I roll back to TC 1.6.x until this is fixed. |
I've noticed this using the creative-item IfniMiner (love it), but it only happens in survival mode. You beat me to opening this. 😄 |
bonii-xx
added a commit
that referenced
this issue
Oct 14, 2014
…reak in AOE correctly. Changed behaviour to emulate the correct behaviour, but don't call the recursive block breaks. Furthermore, send packets causing updates for each AOE block broken. This should prevent clientside ghost blocks because the client is breaking blocks that it can't break yet on the server. #1072
Thanks for the InfiMiner hint, that made testing much easier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I've updated from TC 1.6.x to 1.7.0d3 and got an annoying bug. I thought it was because of the update but I made some new tools directly with 1.7.0d3 and get the same issue. No clue if it's an incompatibility with another mod but for sure, it was perfectly fine before I move to 1.7.0.
The issue:
When a hammer or an excavator reaches a very high speed value, it stops digging 3x3 blocks and only dig single blocks instead.
How to reproduce:
I'm gonna try 1.7.0d4 to see if it fixes it but so far, I couldn't find any post about this bug so it's probably still unknown.
The text was updated successfully, but these errors were encountered: