Deadlock's Stacking for Pyanodon Continued


Adds Deadlock stacking support for intermediate products from Pyanodon's mod suite. Community-maintained continuation for Factorio 2.1.

Content
a month ago
2.1
30
Logistics

b Deadlock's Stacking Beltboxes & Compact Loaders Continued, Py Coal Processing

11 days ago

Game Version: Factorio 2.1
Related Mods: Deadlock's Stacking Beltboxes & Compact Loaders Continued, Py Coal Processing

After updating the mod to the new version, boilers consume entire stacks of coal in one go. However, the Py Coal Processing mod only generates coal ash when individual coal items are destroyed. Consuming a full stack all at once skips the ash generation event entirely.

This issue did not exist in older versions of Deadlock's mod.
The only workaround for now is manually installing auto-unstack loaders at the front of all power plants to avoid this problem.

11 days ago

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.

11 days ago

@hunter_beij I think I’ve fixed it, but the fix is in the main mod rather than the Py compatibility mod.

It’s working correctly on my end now. Could you test it on your side and let me know if it works for you as well?

New response