Badged Claimed: Power User Lovers

EcoCraft is intentionally built at the intersection of low-code orchestration and pro-code execution.

We use Dataverse as the low-code backbone. At the core of the solution, we rely on Dataverse to manage business state like events and registrations, game sessions and progress, mission completion and lifecycle flags. Low-code handles what should happen and when.

Minecraft world changes require things low code is not designed for:

• persistent server connections
• precise command execution
• queueing and error handling

For this, we use Azure Functions written in C# for world manipulation. The function receives a Dataverse-triggered request and authenticates against the Minecraft server. Then it executes a defined set of world commands and returns structured execution results.

This keeps infrastructure logic, server access, and execution control firmly in pro code where it belongs.

Then we use RCON with C# to have a console for development and testing before automating anything.

Why this combination works? Both sides stay simple because they do only what they’re good at. Low code gives us speed, structure, and safety for business logic. Pro code gives us control, performance, and testability where needed. Clear separation of concerns keeps the system maintainable

So low code or pro code? We don’t choose sides: #ProCodeLowCodeUnite