The Great Vibecoding Incident of January 2026

The Setup: A 5,454-line commit lands with the message lots of fucking about. Nobody reads it. Why would they? It’s working, right?

The Plot Twist: Buried deep in the diff, two critical bot functions were quietly replaced with this masterpiece:

async collectItems(itemType, quantity) {
    console.log(`[Collection] Collecting ${quantity}x ${itemType} (not implemented yet)`);
    await this.wait(1000);  // the code equivalent of “thoughts and prayers”
}

async depositItems(items, chestLocation) {
    console.log(`[Deposit] Depositing items (not implemented yet)`);
    await this.wait(1000);  // vibes only
}
The Result: A bot that would receive orders to gather 64 diamonds, announce its intentions to the void, take a power nap, and report back: “Mission complete, boss.”

Lessons Learned:

Maybe read the 5,000-line commit
(not implemented yet) in production is a cry for help
await this.wait(1000) is not a substitute for functionality
The commit message was accurate. It was, indeed, lots of fucking about.

___

DOH:(

DOH!

Nothing like spinning your wheels for *hours* trying to diagnose networking issues.

There is a lot of great community content on connecting Minecraft *locally* to local MCP servers, running node.js applications using the Mineflayer APIs.

The information gets a lot more cryptic when you try to connect to cloud based services and Minecraft server edition.

After spending hours trying to diagnose connection issues (and not even sure what I was trying to achieve was even technically possible), I really felt the wheels spin.

Why would it work one way and not another?

Even to the point I had to dig deep in the toolbox for old tools like Telnet!

It turns out, it was a minor case of finger dyslexia which was the cause of the problem.

IP address 24.5.6.7 is not the same as 20.5.6.7…

1 digit, 20, NOT 24… hours lost. tears shed. swears muttered.

Once that was resolved I was unstuck and back to making progress, only a few hours behind.

D’oh!

Who let the Vexes out?!? Who! Who! Who!

Yesterday, our developers got a bit carried away while base‑building in Minecraft. Mobs were generated. A lot of mobs… especially Vexes. There were simply so many that the server almost went down. The game lagged like crazy, and players reported long waiting times just to get back into the world.

Our beloved judge, Sara, also reported that her dogs in the village were being attacked by mobs!

We would like to offer our most humble apologies. We are truly sorry. We’ve spent a lot of time cleaning up, and everything is back in order now.

Goooooood morning!

Before the sun come up

Early bird cathes the worm!

Competition

We have a competition going

BUT DOH!

The comitee has run a script that mines the whole night. Thank you for giving us so much data 😀

Lets see what will happen.

Teamspirit

We have kept our team spirit througout the Hackaton! And will continue to spread good vibes with our team and table setup!

Two of us won the 5-kamp! So we put in some good effort!

Nasty hacker; import Power Pages when provision fails

With this blog post we aim for the badge “Nasty Hack”

Lots of teams have struggled provisioning new Power Pages sites in newly created environments. We have experienced the same problem.

Provisioning in older environments still work, so the idea was to provision a blank new power pages site in an old environment in another tenant, put it in a solution, export the solution and import it into the new environment.

Export the solution

Unmanaged, of course, to be able to edit the site in the destination environment.

Import

Success

Reactivate site

All good so far..

But then..

Provisioning still is in progress like the first one..

DOH!

Maybe this should qualify for the DOH! Badge instead..