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

Dig spells delete Thermal Expansion machines #1217

Closed
whitepyros opened this issue Aug 21, 2015 · 3 comments
Closed

Dig spells delete Thermal Expansion machines #1217

whitepyros opened this issue Aug 21, 2015 · 3 comments

Comments

@whitepyros
Copy link

Whenever a player uses a dig spell on a thermal expansion machine i doesnt drop as its supposed to it instead just deletes the machine, havent tested with other machines such as ender io yet

AM2 version: 1.4.0.008
Thermal expansion version: 4.0.3B1-218

@LemADEC
Copy link
Contributor

LemADEC commented Aug 27, 2015

There's a configurable blacklist in the configuration file:
# Comma-separated list of block IDs that dig cannot break. If a block is flagged as unbreackable in code, Dig will already be unable to break it. There is no need to set it here (eg, bedrock, etc.). Dig also makes use of Forge block harvest checks. This is mainly for fine-tuning.
S:dig_blacklist=

DoomFruit added a commit to DoomFruit/ArsMagica2 that referenced this issue Sep 13, 2015
@Mithion Mithion added this to the Next AM2 Update (1.4.0.009) milestone Sep 19, 2015
Mithion pushed a commit that referenced this issue Sep 19, 2015
Fix for issue #1217 (dig spell evaporating TE machines)
@jjtParadox
Copy link
Contributor

I believe this issue has been fixed, unless there was a different reason @Mithion added this to the milestone.

@Mithion
Copy link
Owner

Mithion commented Sep 21, 2015

Quite possibly - when creating the milestone I just added any still open issues that need to be fixed before a release candidate could be generated.

This one was fixed by #1239.

@Mithion Mithion closed this as completed Sep 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants