Thanks for the detailed report. I understand the issue: stacked coal is now being consumed by boilers as one fuel item, while Py Coal Processing appears to generate coal ash based on individual coal consumption. That means burning one stacked-coal item can bypass the ash-generation behavior.
I’ll investigate whether the stacked coal prototype is missing or incorrectly handling Py’s ash result, or whether this behavior comes from the current Deadlock stacking implementation itself.
Could you also confirm:
- the exact version of Deadlock’s Stacking Beltboxes & Compact Loaders Continued;
- the exact version of Py Coal Processing;
- which boiler or power-plant entity you tested;
- how much coal ash should normally be produced from one full coal stack?
The auto-unstacking workaround makes sense for now, but ideally stacked fuel should preserve both the total fuel value and the correct ash output.