Skip to content

dig-now - properly handle UNDIGGABLE tiles #5523

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

Merged
ab9rf merged 1 commit into from
Jul 27, 2025
Merged

dig-now - properly handle UNDIGGABLE tiles #5523

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/changelog.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,7 @@ Template for new versions:

## Fixes
- several fixes related to changes in file system handling in DF 52.01
- `dig-now`: don't allow UNDIGGABLE stones to be excavated

## Misc Improvements
- `autoclothing`: added a ``clear`` option to unset previously set orders
Expand Down
10 changes: 4 additions & 6 deletions plugins/dig-now.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -450,12 +450,10 @@ static bool is_diggable(MapExtras::MapCache &map, const DFCoord &pos,
break;
}

if (mat == df::tiletype_material::FEATURE) {
// adamantine is the only is diggable feature
t_feature feature;
return map.BlockAtTile(pos)->GetLocalFeature(&feature)
&& feature.type == feature_type::deep_special_tube;
}
MaterialInfo mi;
mi.decode(map.baseMaterialAt(pos));
if (mi.material != nullptr && mi.material->flags.is_set(df::material_flags::UNDIGGABLE))
return false;

return true;
}
Expand Down