It was a long time since we were in this room,,, Few hours ago actually!
It feels great to be back and we are fully charged for the day (its an affirmation!)
We have a morning newspaper and coffee ready!
Morning Glory
Category Archives: Logiqraft
Client Side Salsa
Category: Code Connoisseur
Description of solution:
Crafting equipment in Minecraft lets you turn basic resources into useful tools, weapons, and armor. Better equipment helps you gather materials faster, survive dangerous mobs, and explore harder areas more safely and efficiently.
To allow customer to order the appropriate equipment that should be printed, we created a PCF control that allow to choose an item from hundreds of different.
Let’s see how it works:
We have a Recipe table where the customer can create a request to build the item.
If we go to the form, we have two fields Name and Description. For the Name field we activated the PCF control, so the form looks like at the picture:
Click on the search button and the modal dialog will be open with a more than thousand items to choose. Here we have possibility to choose the type of item and search by the name or description.
And when customer choose the item, the name, description and small image are set to the fields on the Recipe Model-driven app form.
Using external API:
PCF control receives all Minecraft items thorough public Vercel api:
Let’s look at the code structure:
index.ts – main file with our control
components/MinecraftItemPicker.tsx – React UI component
services/MineCraftItems.service.ts – logic and data
styles/MinecraftItemPicker.styles.ts – styles for component
types/Minecraft.types.ts – data models/interfaces
Performance
- The control cache external data in a dedicated service and reuse it across renders and dialog openings.
- Images are lazy loaded reducing initial load time and avoiding UI blocking.
Maintainability
- The project follows a separation of responsibilities: PCF lifecycle (index.ts), UI components, services, styles, and domain types are isolated in dedicated folders.
- External API access and business logic are encapsulated in a service layer, that allows to make future changes easier or replacements with a low risk.
- The structure closely aligns with Microsoft PCF sample conventions, making the codebase easy to understand for new developers.
Lost Ancient Recipe Recovery Tool
In our concept, the 3D printer becomes a modern crafting table. (ref post Crafting, Crafting, Crafting…. Category: Pro Code | Arctic Cloud Developer Challenge Submissions)
Just like villagers in a game world, our Customers can rely on recipes to craft almost anything they want. But what happens when a recipe is lost, discontinued, or no longer available on the market – and all you have left is a broken spare part?
That’s where Model Builder comes in.
The Problem
Spare parts often disappear long before the products that rely on them. When something breaks, users are left with:
- No original CAD files
- No replacement parts
- No way to reverse-engineer the object without expert tools
The Idea
Model Builder is a recovery tool for lost recipes.
By using just one photo, the app helps users reconstruct a printable 3D model of a broken or unavailable object.
How It Works
- Upload a Single Photo
The user takes a picture of the broken item or spare part using their phone or camera.
- Detail Enhancement
The app enhances edges, surfaces, and geometry, filling in missing or damaged details to make the object readable for modeling.
- Model Generation Assistance
Based on the enhanced image, the tool assists in generating a clean, printable 3D model – ready to be refined or sent directly to the 3D printer.
- Craft Again
The recovered “recipe” allows the user to recreate, repair, or improve the original object.
The Vision
Model Builder turns visual memory into manufacturable knowledge.
Even when designs are lost to time or market changes, users regain the power to repair, recreate, and continue crafting – bringing true self-sufficiency to 3D printing.
We are using the coolest technologies: Bun for the backend app, Gemini Nano Banana Api for Projection generation and Meshy.ai to generate the model from the projections.
Badge: Hipster
Minecraft Dataflow – Recipe Import
This document describes the dataflow used to import external Minecraft items into the application and map them to the Recipe table, enhancing the value of existing data that we have in the model driven app. The recipes are then used by our customer/user.
1. Dataflow Creation
A new dataflow is created using a blank query. The query connects to a public Minecraft API to retrieve item data in JSON format.
2. Minecraft API Query
The blank query is named “Get Items” and contains logic that calls the Minecraft API, converts the response into a table, and selects the required item columns.
3. Dataflow Connection
The connection is configured to allow the dataflow to access the Minecraft Items API.
4. Execute the query
Once the connection is established, the query is executed automatically to retrieve data from the Minecraft API.
5. Table Mapping
The output of the query is mapped to the desired Dataverse table (la_recipe). Each column from the API response is mapped to its corresponding column in the Recipe table.
6. Dataflow Publish
After mapping, the dataflow is published so it can be used for importing data.
7. Running the Dataflow
The dataflow can be scheduled or run manually. The first execution occurs automatically if it is set up as manual. The progress and status can be monitored.
8. Check Results
After the dataflow has run, the imported data can be verified in the model-driven app to confirm that Minecraft items are available in the Recipe table.
Crafting, Crafting, Crafting…. Category: Pro Code
Crafting equipment in Minecraft lets you turn basic resources into useful tools, weapons, and armor. Better equipment helps you gather materials faster, survive dangerous mobs, and explore harder areas more safely and efficiently.
With our 3D printer we print all things the Customer would like to order and using our custom local web server we manage our printer device.
Web portal:
Backend: The backend is written in TypeScript and runs on Bun, using WebSockets and HTTP endpoints to communicate with a Bambu printer via the bambu-link library, handling printer connection, status updates, commands, file uploads, camera snapshots, and cloud API proxying.
Frontend: The frontend is a React + TypeScript single-page app, rendered via index.html, and it connects to the backend using WebSockets and fetch, providing a UI for printer control, status monitoring, file uploads, and cloud interactions.
Let’s watch how it works for example if we want to turn on or/and turn off the Led light during the printing.
This is our web interface.
And demonstration how it works.
Show and tell – CraftPortal Evolved: From Minecraft to Supply Chain
in our first post, we talked about the problem. Supply chains are slow. Parts ship across the world. Weeks pass. Carbon burns. Sometimes the manufacturer doesn’t even exist anymore.
We asked: what if supply chain worked like Minecraft?
Now let’s show you what we mean. (no, its not the same picture)
Think about how Steve plays Minecraft.
Steve needs a diamond sword. He doesn’t call a supplier in another country. He doesn’t wait for a ship. He finds the recipe, gathers materials, walks to his crafting table, and makes it. If he needs something far away, he uses a portal – instant.
Now think about CraftPortal.
A customer needs a part. Instead of ordering and waiting for shipping, they log into the Portal and post a request: “I need this part, these specs.”
IP Owners see the request. We call them Wandering Traders. They don’t ship physical parts – they sell recipes. Digital blueprints. They bid on the request.
Customer picks a recipe. Downloads it through the portal. Instant – like Steve stepping through a Nether portal.
Now the customer has two options:
Option 1: They have their own 3D printer – their Crafting Table. They print the part locally. Done in hours.
Option 2: They can’t print it themselves. They order from a Manufacturer – a Villager with better equipment. The Villager crafts it for them from a local facility.
Either way: recipe travels through the portal, part gets made locally.
No ships. No planes. No weeks. No carbon.
The Tech Behind It
The Portal is Power Pages – the marketplace. Recipes live in Dataverse. Copilot and AI Builder handle automation and intelligence. Azure IoT connects the Crafting Tables. Model Driven App runs the back office. Teams keeps everyone talking.
And LogiQraft? We’re the Redstone Engineers. We build the wiring that makes it all work.
Minecraft Procurement & Crafting Process
This document explains the end-to-end process from the perspective of a player (Steve) using the Model-Driven App within the Minecraft-themed procurement and crafting system.
1. Player Login (Steve)
Steve is a player (user) who logs into the Model-Driven App. From here, Steve can manage Projects, Recipes, Crafting requests, and track all activities.
2. Creating a Project
Steve creates a new Project. A Project represents a request for a specific item or component that needs to be sourced or crafted.
Within the Project, Steve specifies:
- Deadline (when bids should close)
- Budget (in Emeralds 🟩 / EM)
- Recipe or Component required
3. Publishing the Project
Once all Project details are complete, Steve publishes the Project, changing its status from Draft to Open. Publishing makes the Project visible to Vendors via the Power Page (Power Page will not be covered here).
4. Vendors: Villagers & Wandering Traders
Vendors are external parties who interact with the system via the Power Page. There are two types of Vendors:
- Villagers: Crafters and shippers who can manufacture (print) and deliver items.
- Wandering Traders: Providers of Recipes or Components, offering 3D-printable designs.
5. Bids (Handled via Power Page)
Wandering Traders can view published Projects on the Power Page and place Bids. A Bid includes the price for providing the requested Recipe or Component.
Although Bids are created through the Power Page, all Bid records and statuses are visible to Steve in the Model-Driven App.
6. Selecting a Winning Bid
Once the deadline has passed, or earlier if Steve is satisfied, Steve selects a winning Bid.
The selected Bid determines which Wandering Trader will provide the Recipe or Component.
7. Contract Creation & Signing
After a Bid is selected, a Contract is automatically created and sent to the winning Wandering Trader for signing.
The Contract formalizes the agreement, including price, delivery expectations, and terms.
8. Receiving the Recipe / Component
Once the Contract is completed, Steve receives the Recipe or Component. At this point, Steve has two options:
- Print / craft the item themselves.
- Request a Villager to craft and ship the item.
9. Creating a Crafting Record
If Steve cannot or does not want to craft the item personally, they create a Crafting record.
In the Crafting record, Steve specifies:
- The Recipe to be crafted
- The selected Villager
- Shipping details (not yet implemented)
Villagers will charge an additional fee for crafting and shipping, which is tracked within the system.
10. Visibility & Tracking
Although Villagers and Wandering Traders primarily use the Power Page, all records, logs, and statuses are also visible to Steve in the Model-Driven App for full transparency.
11. Recipes Management
Recipes can be created in multiple ways:
- Automatically by selecting an item from the Minecraft API.
- Manually created by a player to define a custom Recipe.
Recipes can be reused across Projects and Crafting requests.
The Name column is implemented as a PCF control using Fluent UI React v9. When the magnifying glass is clicked, a modal window appears that calls the Minecraft API, allowing players to select a recipe and return its name, description, and icon.
12. Summary
This process creates a complete Minecraft-themed procurement and crafting flow. From Project creation, bidding, contracting, recipe sourcing, to final crafting and delivery.
#low-code + pro code #category
Early Delivery, Show and Tell: CraftPortal: Bringing Minecraft to Supply Chain
The Problem
A part breaks. You need a replacement. The manufacturer is on the other side of the world. Traditional supply chain kicks in: order placed, part produced or pulled from stock, shipped across continents, customs cleared, finally delivered. Sometimes – the wrong part. Start over.
Weeks pass. Operations suffer. Carbon burns.
Or worse – the manufacturer went out of business ten years ago. No stock. No supplier. No solution. The machine stays broken.
This is modern supply chain. Global, fragile, slow.
The Inspiration
In Minecraft, Steve doesn’t wait for delivery. He finds what he needs, crafts locally, moves on. Instant. Simple.
What if real-world supply chain could learn something from this?
The Vision: CraftPortal
A portal. Vendors. Manufacturers. Customers. A Crafting Table.
Connected in a way that might just change how we think about getting parts from A to B.
The Tech
Built on Microsoft cloud: Power Platform, Azure, Copilot Agents, IoT, AI.
Happy Camper: R U ready for the healthy snack?
It feels too quiet over there, in the judges’ corner and we cannot wait to start talking to you guys, but we have little to nothing to show yet )) The team spirit is high, and same is optimism or maybe we are high on sugar? Anyways, just come over and grab some snacks from Spain, Scotland, Croatia, Macedonia, Ukraine!
Sharing is Caring: Minecraft Heads
What a great way to start the day 1 of ACDC 2026, Minecraft edition!
Kuddos to @advaniaEnderdogs (not Underdogs!) and @Bratwurst and Biscuits (everybody loves them!) for sharing their Minecraft Heads (and something else…stay tuned) with our team!
