In our case, that system was Dynamics 365 Production Orders.

What production orders normally do

In a standard ERP setup, releasing a production order typically triggers:

• Warehouse picking
• Manufacturing execution systems
• Shop floor machines
• Industrial control software

In short: very serious, very real-world manufacturing.

What our production order does

When a production order is released in our solution, it triggers:

• A Minecraft bot

The production order is treated as valid, approved, and executed. exactly as intended by the traditional ERP.

The difference is only in what executes it.

The semantic hack

We deliberately reinterpreted the meaning of manufacturing:

• Minecraft acts as the manufacturing execution system
• Blocks are treated as inventory
• Mining and crafting are treated as production steps
• Gameplay becomes the production process

From Dynamics 365’s perspective:

• A production order was created
• Materials were consumed
• Output was produced
• Status was reported back

All of this is technically correct.

Why this qualifies as a Nasty Hack

• No custom manufacturing logic was added to Dynamics
• No simulation layer was introduced
• No special exceptions were built

We reused standard ERP production flows and simply pointed the execution at something they were never designed for.

The ERP believes it is running manufacturing.
In reality, a bot is mining blocks….Kinda absurd if I say so myself

Conclusion

This is not how production orders are meant to be used.
But it works.

Which makes it a proper Nasty Hacker solution.